ORA-1652

Hi,
We are running SAP on ECC 5.0 , Oracle 10.2 and windows 2003 x-64 bit. We have tried to export the production system and getting failed several times. The log is as follows.
DbSl Trace: ORA-1652 occurred when executing SQL statement (parse error offset=754)
(EXP) ERROR: DbSlExeRead failed
rc = 99, table "COEP"
(SQL error 1652)
error message returned by DbSl:
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
(DB) INFO: disconnected from DB
We had run the DB verify and corrected the corrupted datablocks through re-org. The re-org went sucess fully. Again we had run the export and got failed at the same place. This happend several times. We have turned the auto extend on for the tablespace 'PSAPTEMP'. Still no use. Appreciate your help on this.
Thanks,
Krishna.

Hi Krishna,
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
We have turned the auto extend on for the tablespace 'PSAPTEMP'. Still no use.
Even if you put the auto extend ON, it has a max size value.. the export still requires more PSAPTEMP, if you've more space at OS level, you should increase the max size of PSAPTEMP so that it can grow more.
Regards,
Debasis.

Similar Messages

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 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 error

hi,
today in one of the database alert log i found this error.
Thu Apr 29 05:46:22 2010
ORA-1652: unable to extend temp segment by 1504 in tablespace TEMP
I checked the space availabily of TEMP tablespace,but it is having 1GB free space in it.
I m not sure of this error.could anybody help me on this.

Now may be there free space,but if you use long runnig queries with order by clause or create index statement on big tables then there is not enough free space .
And this time you can check free space as
select sum(free_blocks) from v$sort_segment where tablespace_name='TEMP';
Edited by: admin on Apr 29, 2010 11:40 PM

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 --

ORA-00604,ORA-00600,ORA-1652,ORA-1653,ORA-00257 errors

Hi All,
I am getting the below alerts in my Oracle 9i database.
ORA-00604: error occurred at recursive SQL level 3
ORA-00600: internal error code, arguments: [kghpih:ds], [
ORA-1652: unable to extend temp segment by 128 in tablespace           TS_PHDB_5
ORA-1653: unable to extend table T49XPWM.TMP_PD_VALUES by 128 in           tablespace TS_PHDB_5
ORA-1652: unable to extend temp segment by 128 in tablespace           TS_PHDB_16
ORA-00257: archiver error. Connect internal only, until freed.
ORA-604 signalled during: ALTER DATABASE CLOSE NORMAL...
Saswat

This error does not necessarily indicate whether or not you have enough space
in the tablespace, it merely indicates that Oracle could not find a large enough area of free
contiguous space in which to fit the next extent.
add datafile to your table space.
Edited by: Asad99 on Apr 1, 2013 3:59 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

ORA-1652: unable to extend

Hi ,
on 11g R2 I have repeatedly the following error in alertlog :
2012-08-10 12:16:45.061000 +02:00
ORA-1652: unable to extend temp segment by 16 in tablespace PSTEMP How can I find the user or query that causes this ?
Thank you.

How can I find the user or query that causes this ? check v$tempseg_usage to find out any running session with high temp usage.
also check
ORA-1652: unable to extend temp segment by 128 in tablespace

ORA-1652: unable to extend temp segment by 187502

Hi ,
OS=AIX 5.2
DB= Oracle8i , 8.1.7.4.0.
I've seen few ORA-1652 in alert log file, and the TS that it shows with error is permanant and dictionary managed Tablespace as there is no temporary tablespace in the database, its autoextend is off.
This Tablespace is of total 13 GB , with 2 datafiles (9G + 4 G). one datafile is almost 30 % Free the other is 80 % free. that shows that there is enough free space in the tablespace and on the filesystem there is also enough freespace.
initital extent and next extent are 1 Mb with pct increase 10.
If somebody can help to solve out this issue, and why this error occured.
Thanks in advance!

Are you sure the user runing the large sort is using the right temp-tablespace?
If not then he uses the system tablespace for temp, and that might be something you should not want.
And if i am correct Oracle does not clean out the temp-tablespace in ways of showing the free space it actualy has. At least in Oracle 9 this is the case, the temp tablespace will show a used percentage of what it ever was used and not how much actualy is being used. It can be free actualy, but showing a 100% used in the tablespace-list (in the oracle enterprise manager).
This makes me feel that if you say the temp-tablespace still has unused space, the query does not use the right temp-tablespace.

ORA-1652: Index creation error

At the time of table re-organisation, Index creation got aborted for the secondary index creation. then we have continued our activity leaving the index creation due to short of System downtime.
Again we have run the sql statment when the sap system is up, then it has thrown an error:
ORA-1652 unable to extend temp segment by 128 in tablespace PSAPTEMP.
In the current system, we are not ready to increase the size of datafile or resizing.where it leads to the increase the size of database.
Here we have option to create a new temp tablespace, will delete after index creation, but while doing this how do we point the new tablespace which is created for this activity.
SAP 4.6c oracle 9 sun solaris.
Kindly advise what can be done. reply ASAP

Martin,
We have discussed with the team like,
1. Create new temporary tablespace with desired Size which should be minimum 25GB
            CREATE temporary tablespace PSAPTEMP1......
    2. If the original tablespace is a default temporary tablespace, set the new tablespace as default temporary tablespace in the database.
             SQL> alter database default temporary tablespace PSAPTEMP1;
    3. Perform the index creation
    4. Make the old tablespace PSAPTEMP as the default temporary tablespace.
             SQL> alter database default temporary tablespace PSAPTEMP
   5. Drop the new tablespace.
             SQL> drop tablespace temp including contents.
Here I have a question, while switching the default temporary tablespace from PSAPTEMP to the much bigger new PSAPTEMP1Tablespace whether this will affect the running transaction.
Any impact on switching the tablespace online..?
We are performing this activity in the online system(running sap system)
Thanks,

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 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

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

Similar Messages

Maybe you are looking for