ORA-1652: unable to extend temp segment by 128 in tablespace TEMP

Hi All,
Today in we have faced the below issue in our production database
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP
when we checked we are having 99% of free space in temp tablespace,we are not able to understand why we got this error.
earlier also we got the same issue adding datafile to the tablespace solved the issue. wanted to know if free space exsists why we getting this error.
Thanks....

Hi,
Please check Oracle support id : TROUBLESHOOTING GUIDE (TSG) : ORA-1652: unable to extend temp segment (Doc ID 1267351.1)
and OTN Form :
https://forums.oracle.com/thread/457771?start=0&tstart=0
https://forums.oracle.com/thread/703095?start=0&tstart=0
Thank you

Similar Messages

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

Hi,
I am getting the following error while executing an insert query.
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP.
I have tried increasing the TEMP tbsp size it got resolved temporarily but occurred again after few days.
When the problem occured, following query shows all insert queries in TEMP tablespace and one of them consumes about 5GB and others are about 24MB.
SELECT S.sid || ',' || S.serial# sid_serial, S.username,
T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
T.sqladdr address, Q.hash_value, Q.sql_text
FROM v$sort_usage T, v$session S, v$sqlarea Q, dba_tablespaces TBS
WHERE T.session_addr = S.saddr
AND T.sqladdr = Q.address (+)
AND T.tablespace = TBS.tablespace_name
ORDER BY S.sid;
The insert query is :
INSERT INTO SEOSDATA (ENTRYID,DOMAINNAME,USERNAME,EVENTTYPE,LOGNAME,TIMSTAMP,SOURCE,COMPUTERNAME,EVENTID,EVENTCATEGORY,SEARCHSTRINGS,MSGTEXT) VALUES (ENTRYID_SEQ.NEXTVAL,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)
It is not expected that an insert query consumes such a huge memory.
Can someone help me in figuring out what the problem is.
What might have gone wrong? Seems like sorting is used, why an insert query uses sorting?
Regards
Ishu

Hi,
Insert statement should not use TEMP tablespace. Please check with following query which user and session id is using TEMP tablespace.
SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
a.username, a.osuser, a.status
FROM v$session a,v$sort_usage b
WHERE a.saddr = b.session_addr
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
Dilipkumar Patel.

Need help on "unable to extend temp segment by 128 in tablespace TEMP..

Dear All,
I recently ported my code from Vs 2003 running on Windows 2003 Server to VS 2010 running on Windows 2008 Server 64bit.
The DB query that we trigger from the code has not been changed but forming the query is changed.Like in very high level initally I was getting data at execution level so I use sprintf to form the query along with required params and then use SQLExecute. The application runs fine for few hrs after that I get the below error.
6/23 15:40:11 (4396 0214): ExecuteDirectly::Failed Query is [insert into Test (bbid, keyOrder, keyLength, keyValue) values (?, ?, ?, ?)]
06/23 15:40:11 (4396 0214): Encountered ODBC error -1: S1000, 1652, [Oracle][ODBC][Ora]ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
I am using Oracle 11g client on Windows 2008 Server R2. Surprisingly when we get this temp space issue in the DB, that time when I run the same query through application from a 32bit it is able to execute successfully same doesn't happen with 64bit machine.
Any suggestion to resolve the above error ?Am I doing a memory leak of something which is causing the above issue.
Thanks in advance.
-R

I was trying to monitor as which inserting is causing this issue.It looks to be the insertion of blob data is causing the issue.When I disable all the insertions of Blob data the temp space issue doesn't come.
I am seeing some trailing characters in the coloumn when we are inserting Blob. I am doing SQLBindParameter with SQL_C_BINARY and SQL_LONGVARBINARY as InputOutputType and ValueType respectively.Do you see any problem in this.
Thanks,
-R

Unable to extend temp segment by 128 in tablespace TEMP

Hi all,
I am using apps 11.5.10.2 and i think this is a database issue
ERROR at line 1:
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
Do i have to increase the tablespace, if so how to do it. I don't even know the EM Pass
Regards
Jagan

what is the size of your temp tablespace?
Have another try, if the problem persists, increase the temp datafile size.
alter database tempfile <temp file name> resize <integer> M;
You can also add a new datafile.
ALTER TABLESPACE name ADD TEMPFILE 'filename.dbf' SIZE 10M;
You can always investigate and try to avoid too much sort by checking the SQL.
Jaffar

ORA-1652: unable to extend temp segment by 128 in tablespace

HI,
i am getting an error in alert log file.....
Thread 1 advanced to log sequence 1758
Current log# 2 seq# 1758 mem# 0: /dev/vx/rdsk/racdg/orcl_raw_log12
Mon Sep 8 12:34:16 2008
ARC1: Evaluating archive   log 1 thread 1 sequence 1757
ARC1: Beginning to archive log 1 thread 1 sequence 1757
Creating archive destination LOG_ARCHIVE_DEST_1: '/arch/log/1_1757.dbf'
ARC1: Completed archiving log 1 thread 1 sequence 1757
Mon Sep 8 13:04:26 2008
Completed checkpoint up to RBA [0x6de.2.10], SCN: 0x0000.6c1f757f
Mon Sep 8 13:49:16 2008
ORA-1652: unable to extend temp segment by 128 in tablespace                 TEMPI don';t want to add datafile
SQL> select bytes,maxbytes,increment_by from dba_temp_files;
     BYTES   MAXBYTES INCREMENT_BY
6134169600          0            0
SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
TABLESPACE_NAME                BYTES_USED BYTES_FREE
TEMP                           6037700608   96468992i have also referred metalink note: 19047.1
Is there any way to avoid this problem without adding any datafile........

how to find out which session is using temp tablespace
SQL> select * from v$sort_usage;
USERNAME                       USER                           SESSION_ADDR
SESSION_NUM SQLADDR             SQLHASH TABLESPACE
CONTENTS SEGTYPE     SEGFILE#    SEGBLK#    EXTENTS     BLOCKS   SEGRFNO#
DATA3                        DATA3                        000000044D84F558
      25860 00                        0 TEMP
TEMPORARY DATA             201     183561          1        128          1pls correct me if the above query is worng to find out the no. of session s using temp tablespace
i think we have already allocated good amt of space to pga_aggregate_target
SQL> show parameter pga
NAME                                 TYPE        VALUE
pga_aggregate_target                 big integer 524288000
SQL>Edited by: user00726 on Sep 8, 2008 2:29 AM

ORA-1652: unable to extend temp

Hi,
We faced a problem with one of r billing process which normally takes 25-30 min was running for over 5 hrs and in the end gave a rollback error....when the process was re-started it got completed in 35 min....
Tue Jan 1 22:48:33 2008
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP
Tue Jan 1 22:48:37 2008
GATHER_STATS_JOB encountered errors. Check the trace file.
Tue Jan 1 22:48:37 2008
Errors in file /oracle/databases/bluedart/bdump/bluedart_j001_19817.trc:
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

Hi,
Which version ?
R u using LMTS or DMTS ?
How much space u have allocated for your Temp Tbsp?
Generate the statspack report or V$ tables which query or process involved in that report?
Regards,
Suresh

Oracle Alert - ORA-1652 Unable to extend the Temp Segment

Hi Team,
During our DB Reorg we have received the Oracle Alert - ORA-1652 Unable to extend the Temp Segment by 15485 in tablespace :PSAPBTABI.
Our DBReorg got cancelled..
We would like to know how we can resolve the above error so that we can reschedule the DB Reorg activity..
Regds,
Satyanarayana N

Hi,
If you are using UNIX OS, the temp files are created as sparse file due to the OS functionality.
Altough you have assigned 49 GB the actual size will be very very less.
You can check the actula file size with du or df command. To remove these sparse condition you will need to perform certain steps.
Read this note and execute the steps given and then see the file size difference.
548221 - Temporary Files are created as sparse files
Do update the message if the OS is different.
Regards,
Nilesh

ORA-1652: unable to extend temp segment

Hi,
I am new here and i am not sure if my question is for that section but will be happy to get some answers.
I found ORA-1652: unable to extend temp segment by 128 in tablespace PSAPTEMP in alert log and checked the space in PSAPTEMP.
TABLESPACE_NAME MB_FREE FRAGMENTS BIGGEST_BIT
PSAPTEMP 0.00 1 0.00
Could you advice me what to do?
Thanks in advance
Miki

Miki, you probably need to add space via adding another data file as the posted error message information says or you might first look to see what is using the space to make sure someone did not do something 'stupid'. In this case stupid would be assigning the wrong usernames the affected tablespace as their default temporary tablespace when the users should be assigned a different one or some other misconfiguration.
Most likely you just need a larger tablespace, but it never hurts to know why or how much larger before taking action.
HTH -- Mark D Powell --

How to find which query ORA-1652: unable to extend temp segment by 128 in

How can i find which query caused the below error,the query is not running currently
ORACLE ERRORS IN ALERTS LOG dnb2stg3 - lnx300 on Thu Jun 17 12:10:01 EDT 2010
1 ORA-1652: unable to extend temp segment by 128 in tablespace TEMP_SCHED
SQL> select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks from gv$sort_segment;
INST_ID TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
1 TEMP 638336 0 638336
4 TEMP 565760 0 565760
4 TEMP_SCHED 16776704 0 16776704
3 TEMP 484864 0 484864
3 TEMP_SCHED 0 0 0
2 TEMP 455808 0 455808
6 rows selected.
SQL> SQL> SELECT S.sid || ',' || S.serial# sid_serial, S.username,
2 T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
3 T.sqladdr address, Q.hash_value, Q.sql_text
FROM v$sort_usage T, gv$session S, gv$sqlarea Q, dba_tablespaces TBS
4 5 WHERE T.session_addr = S.saddr
6 AND T.sqladdr = Q.address (+)
7 AND T.tablespace = TBS.tablespace_name
8 ORDER BY S.sid;
no rows selected

Hello,
You may try to catch the SQL with a Servererror Trigger.
This link will give you an interesting example:
http://oratips-ddf.blogspot.com/2008/09/to-err-is-human.html
Hope this help.
Best regards,
Jean-Valentin

Query to find which past ses caused ORA-1652: unable to extend temp segment

Hi,
I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
I have generated the AWR report but not able to figure it out which sessions caused this error.
Thanks in advance

913410 wrote:
Hi,
I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
I have generated the AWR report but not able to figure it out which sessions caused this error.
Thanks in advance
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.

ORA-1652: unable to extend temp segment by 699912 in tablespace ##PSAPTEMP

Dear Expert
I found this error ORA-1652: unable to extend temp segment by 699912 in tablespace ##PSAPTEMP. How can I fix this problem. Anyone help me...pls
best regards

Hi,
We had the same error in our Production system.
That basically occured when there were a lot of Background jobs that were running.
As more than 5 jobs were running which were utisiling PSAPTEMP to the fullest invariably the jobs got cancelled with a dump and the error u have mentioned
Though we tried adding 3 datafiles the error kept repeating..
We finally added almost 20 GB to PSAPTEMP for those jobs to get completed.

ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1/TEMP2

db version: 11.1.0.7
I detect the error log on dbTier's alertlog as below, BUT I think the temp tbs is enough because of the SQL output(you can see as below too)
so I want to know why and how can I fix it. thanks
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP2
SQL> select TABLESPACE_NAME,TOTAL_BLOCKS,USED_BLOCKS,FREE_BLOCKS from v$sort_segment;
TABLESPACE_NAME-------TOTAL_BLOCKS-----------USED_BLOCKS--------------FREE_BLOCKS
TEMP1 -------------1048448------------9472--------1038976
TEMP2---------------1048448 -----------5248---------1043200
TEMP--------0--------0-------------0

Unless you are running the query against v$sort_segment at the point in time that you are getting the errors, I would strongly suspect that something tried to use more than 16 GB of TEMP space, the query died, and when you subsequently looked, nothing was attempting to use much TEMP space. That doesn't mean that some process wasn't eating up all your TEMP space earlier.
My guess (no evidence, just a hunch) is that you have a query that is doing a Cartesian join, that query rapidly consumed all the space in the TEMP1 and TEMP2 tablespaces, encountered this error before exiting and freeing all the TEMP1 and TEMP2 space it had acquired before you ran your query.
Justin

ORA-1652: unable to extend temp segment by 128 in tablespace PSAPTEMP

Hi Gurus,
We are getting this alert continuosly , anybody please suggest me.
OS: AIX
DB:ORACLE 10g
We disabled STAT file also,, but still we are getting this alert
please check table spaces,,,
PSAPTEMP                          10.485.760     10.481.664          0          0          0    Off                  0    ONLINE
PSAPUNDO                           8.514.344      2.062.912         75         31        951    Off                 75    ONLINE     NOT ACTand file system also fine
please find below error details..
02/05/10 10:45:12 Europe/Middle (open.related - System Open Related):
External Update
05/02/2010 08:27:41 by CA
Attached new CA message: 1535095
.Last matching line that caused this alert: ORA-1652: unable to extend temp segment by 128 in tablespace PSAPTEMP
BR0301E SQL error -1652 in thread 4 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPP01"', TABNAME => '"GLPCA"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SI
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
ORA-06512: at "SYS.DBMS_STATS", line 13437
ORA-06512: at "SYS.DBMS_STATS", line 13457
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPP01.GLPCA
Regards,
balaram

HI,
ORA-01652: This error is caused by a tablespace overflow. As a rule of thumb, PSAPTEMP should be at least twice as large as the largest index. If an overflow occurs despite this size, this is     frequently due to external reasons such as incorrect Oracle parameter settings, large-scale parallel processing or    unfavorable access paths. See also Note 3155.
Check - 659946 for details.
Best Regards
Niraj

ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1

Hi,
I am using 10g RAC Database. Its an 3 node RAC infact 2 nodes are active. Today i found some temp segment related error in my alert logfile.
ORA-1652: unable to extend temp segment by 128 in tablespace
After some time the error disappeared. When i checked the space availbility in that temp1 tablespace its showing enough space (almost 13 gb is free from out of 15 gb).
Could pls tell me why this error occured?
For node 1 alert
==========
Wed May 25 11:17:25 2011
Beginning log switch checkpoint up to RBA [0x5de0.2.10], SCN: 12187394662259
Wed May 25 11:17:25 2011
Thread 1 advanced to log sequence 24032 (LGWR switch)
Current log# 4 seq# 24032 mem# 0: +DGAPPROD01/approd01/onlinelog/group_4.368.675197639
Wed May 25 11:19:31 2011
Incremental checkpoint up to RBA [0x5ddf.44a31.0], current log tail at RBA [0x5de0.119e.0]
Wed May 25 11:22:34 2011
Completed checkpoint up to RBA [0x5de0.2.10], SCN: 12187394662259
Wed May 25 11:36:30 2011
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
Wed May 25 11:36:34 2011
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
Wed May 25 11:36:40 2011
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
Wed May 25 11:36:44 2011
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
Wed May 25 11:50:09 2011
Incremental checkpoint up to RBA [0x5de0.e7fb.0], current log tail at RBA [0x5de0.12c99.0]
Wed May 25 12:11:59 2011
Starting control autobackup
Control autobackup written to DISK device
handle '/home/apacops/disk2/db_backup/approd01/db_hot/approd01_25_05_2011_120502/CONTROLFILE_c-3463087906-20110525-00'
Wed May 25 12:12:08 2011
ALTER SYSTEM ARCHIVE LOG
Wed May 25 12:12:08 2011
Thread 2 advanced to log sequence 13302 (alter system archive log)
Wed May 25 12:12:08 2011
Beginning log switch checkpoint up to RBA [0x5de1.2.10], SCN: 12187452224920
Wed May 25 12:12:08 2011
Thread 1 advanced to log sequence 24033 (LGWR switch)
Current log# 8 seq# 24033 mem# 0: +DGAPPROD01/approd01/onlinelog/group_8.372.675197727
Wed May 25 12:12:38 2011
ALTER SYSTEM ARCHIVE LOG
Wed May 25 12:12:38 2011
Thread 2 advanced to log sequence 13303 (alter system archive log)
Wed May 25 12:12:42 2011
Beginning log switch checkpoint up to RBA [0x5de2.2.10], SCN: 12187452225436
For node 2 alert
============
Wed May 25 09:58:50 2011
Completed checkpoint up to RBA [0x5143.2.10], SCN: 12187336726369
Wed May 25 10:00:05 2011
Incremental checkpoint up to RBA [0x5143.344.0], current log tail at RBA [0x5143.3b3e.0]
Wed May 25 10:30:49 2011
Incremental checkpoint up to RBA [0x5143.afab.0], current log tail at RBA [0x5143.ba27.0]
Wed May 25 11:01:30 2011
Incremental checkpoint up to RBA [0x5143.182db.0], current log tail at RBA [0x5143.1c1a6.0]
Wed May 25 11:32:08 2011
Incremental checkpoint up to RBA [0x5143.22413.0], current log tail at RBA [0x5143.233c9.0]
Wed May 25 11:36:14 2011
ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
Wed May 25 12:02:46 2011
Incremental checkpoint up to RBA [0x5143.2fbf4.0], current log tail at RBA [0x5143.34e2c.0]
Wed May 25 12:11:51 2011
Beginning log switch checkpoint up to RBA [0x5144.2.10], SCN: 12187452224934
Wed May 25 12:11:51 2011
Thread 3 advanced to log sequence 20804 (LGWR switch)
Current log# 2 seq# 20804 mem# 0: +DGAPPROD01/approd01/onlinelog/group_2.387.678151487
Wed May 25 12:12:23 2011
Beginning log switch checkpoint up to RBA [0x5145.2.10], SCN: 12187452225434
Wed May 25 12:12:23 2011
Thread 3 advanced to log sequence 20805 (LGWR switch)
Tks

843277 wrote:
Hi kamran,
In SQL Statistics Link, i can see some fields like..
SQL Statistics
* SQL ordered by Elapsed Time
* SQL ordered by CPU Time
* SQL ordered by Gets
* SQL ordered by Reads
* SQL ordered by Executions
* SQL ordered by Parse Calls
* SQL ordered by Sharable Memory
* SQL ordered by Version Count
* SQL ordered by Cluster Wait Time
* Complete List of SQL Text
From here how can i figure out more details?
Pls guide me.
RgdsCheck the statistic of all sql's which consumes more memory

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2

Dear all,
received this error when generate a report.
check the TEMP1 and TEMP2 they all have lot of spaces.
check the env $APPLLCSP return empty.
Please advise how to correct this error.
Regards,
Payables: Version : 12.0.0
APXSSIMP module: Supplier Sites Open Interface Import
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
Enter Password:
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-300: MSG-00001: After SRWINIT
MSG-00002: After Get_Company_Name
MSG-00003: After Get_NLS_Strings
MSG-00004: After Importing Suppliers
MSG-00005: After Get_Header_Information
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
==> SELECT assi.org_id C_Rejected_Org_Id,
MSG-00020: After SRWEXIT
Report Builder: Release 10.1.2.0.2 - Production on Mon May 11 09:55:36 2009

>
check the TEMP1 and TEMP2 they all have lot of spaces.
>
How much is "lot" ? :-) How did you determine this "lot" ?
Pl see MOS Doc 1025288.6 (How to Diagnose and Resolve UNABLE TO EXTEND Errors)
HTH
Srini

ORA-1652: unable to extend temp segment by 128 in tablespace TEMP

Similar Messages

Maybe you are looking for