<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technology on Chenism</title><link>https://chenism.net/categories/technology/</link><description>Recent content in Technology on Chenism</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 19 Apr 2019 01:14:50 -0400</lastBuildDate><atom:link href="https://chenism.net/categories/technology/index.xml" rel="self" type="application/rss+xml"/><item><title>Oracle unable to extend temp segment in tablespace</title><link>https://chenism.net/posts/2019-04-19-oracle-unable-to-extend-temp-segment/</link><pubDate>Fri, 19 Apr 2019 01:14:50 -0400</pubDate><guid>https://chenism.net/posts/2019-04-19-oracle-unable-to-extend-temp-segment/</guid><description>&lt;p&gt;In order to test a data conversion tool which my team had been developing for weeks, we wanted to import the latest database dump from production to our develop environment so we can run the tool against the latest data and assess the conversion result.&lt;/p&gt;
&lt;p&gt;The database in our environment was Oracle 11g Release 2, and the DMP file to be imported was about 34 GB. I let the import process ran overnight, only to realize next morning that it failed. I checked the alert log which in our case is under &lt;code&gt;/ora01/app/oracle/diag/rdbms/orcl/orcldv/alert/log.xml&lt;/code&gt; and realized there was an error in the log: &lt;code&gt;ORA-1652: unable to extend temp segment by 1024 in tablespace&lt;/code&gt;. At first this seemed weird to me but after talking to our DBA I realized this actually meant the datafile of the tablespace I was using, instead of system temp, reached its size limit.&lt;/p&gt;</description></item></channel></rss>