Unable to extend TEMP segment even after adding fresh temp files

Hi All,
I have a huge table with rows nearly 2 million. When this table is moved to another tablespace, the command failed giving the following error:
ORA-01652: unable to extend temp segment by 128 in tablespace XYZ
To overcome this error, an additional temp file was added with huge size. Unfortunately, the same error appeared again when the table was tried to move to another tablespace. I wonder if the new temp file was not recognized by database, so tried to see how many files belong to temporary tablespace, but the query listed the newly added temp file also.
What could be the possible reason for this error? Suggestions or clues are most welcome.
Thanks,
...

The temp segment is for the table that is being moved.
Oracle creates a temporary segment when doing a move. If the target tablespace has enough space, the move succeeds and the temp segment gets converted to a Table segment. Else, if the move fails because of lack of space (the temp segment itself unable to grow), then the temp segment is dropped on failure.
Thus, in a
alter table ABC move tablespace MY_TBS;or
the target tablespace MY_TBS should have enough space for ABC. While Oracle is building the copy of ABC in MY_TBS, it is being built as a temporary segment. If the copy succeeds, the temporary segment is renamed as a Table segment 'ABC' and the original table segment 'ABC' is dropped.
This behaviour also happens when you do an ALTER TABLE .. MOVE ; into the same tablespace that it is existing in. The new copy of the table is a temporary sgement till the copy succeeds.

Similar Messages

The Sky is Falling! ORA-01652: unable to extend temp segment by 128

So we currently have a production problem and I'm not so in the know as a lowly java developer and not an Oracle expert.
We keep getting this error(below) when a certain heavy query hits the DB.
Our DBA claims that the tablespace for 'TABLE_SPACE_NAME_HERE' is 20GB of space and that the problem is the query.
The query has been running fine for many many months but all of a sudden is presenting a problem and we have to do something quick.
We tried bouncing the application server but the error came right back when the big select query gets hit.
Any thoughts? Help! : )
java.sql.SQLException: ORA-01652: unable to extend temp segment by 128 in tablespace TABLE_SPACE_NAME_HERE
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:113)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:754)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:972)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1074)
     at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:854)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1156)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3415)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3460)
     at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)

LosLobo wrote:
So, the next question... what is our lesson learned in this case?It depends on the root cause.
Our DBA thinks 30GB is an unreasonable size for the tablespace and is fingering the select query that was causing the error to occur. Their solution is move to the query to a view and then reduce the tablespace back to 20GB.
My thoughts are shouldn't the DB be able to handle a query that has been running fine for the last couple years? Also, if we do what is suggested what would prevent another query from coming along and causing the same issue all over again?Has the DBA identified the source of the issue? Did the query plan change? It's possible that something with statistics (or with some configuration change) causes Oracle to believe that two different query plans are roughly equally efficient. One plan might take substantially more TEMP space than another. It's possible that Oracle had been choosing the plan that involved less TEMP space being used and recently changed to preferring the plan that takes more TEMP space. If that's the issue, you may want to force Oracle to use the plan that involves less TEMP usage.
Regardless of your TEMP tablespace size, another query may come along that causes TEMP to run out of space. Or data growth may cause TEMP to run out of space. Or an increase in the number of users may cause TEMP to run out of space. Ideally, the DBAs would be identifying how much TEMP space is used over the course of the day so that if things are growing steadily additional space can be added as necessary. If TEMP space increases dramatically because a query plan changes, however, even the best monitoring is unlikely to be able to predict that level of growth.
Whether 30 GB is unreasonable (or whether 20 GB is unreasonable) will depend heavily on your application. We don't know enough to be able to comment. A TB-sized OLTP database serving millions of customers will have very different TEMP requirements than a multi-TB data warehouse which will have very different TEMP requirements than a small department-level application.
My surmising is we must have just crossed a watermark threshold and the simplest most reasonable solution is to just leave the larger tablespace size.Why do you believe this is the case? It is entirely possible that you need more TEMP because your TEMP usage has been growing slowly over time. It is entirely possible that the query in question has always been using more TEMP space than it really should and that you finally have enough usage to cause the problem to bubble to the surface. It is entirely possible that the query used a reasonable amount of TEMP for the past couple years and suddenly started using far more because of a query plan change. Once you identify the source of the problem, we can figure out the appropriate solution. Without knowing the source of the problem, we're all just guessing.
Justin

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

Unable to extend temp segment

Hi All,
I received the following error;
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
Then I added the datafile in temp2 tablespace.
But still it giving the same error;
Syntax of Create tablespace is
Create temporary tablespace temp2
Datafile \temp_01.dbf size 500m;
Table contains 100000 records;
Please help me.
Thanks and regards,
Prathamesh.

Please check the allocation and deallocation of space in a temporary tablespace sort segment using the V$SORT_SEGMENT view. The V$TEMPSEG_USAGE view identifies the current sort users in those segments.
Also, check settings of TEMP tablespace. May be it's trying to create a huge extent as NEXT (larger than available space), which is not required. In that case reduce NEXT EXTENT for this.

Add Unique Constraint - Unable to extend temp segment

I'm getting the error "ORA-01652: unable to extend temp segment by 1024 in tablespace ...". I'm a developer, and our DBA is on vacation. I'm trying to understand what's happening, so I monitor V$SORT_SEGMENT while the constraint is being created. Here is what that view looks like immediately before and after the exception is thrown:
10:43:07 < ... > select * from v$sort_segment;
TABLESPACE_NAME                 SEGMENT_FILE SEGMENT_BLOCK EXTENT_SIZE CURRENT_USERS TOTAL_EXTENTS TOTAL_BLOCKS USED_EXTENTS USED_BLOCKS FREE_EXTENTS FREE_BLOCKS ADDED_EXTENTS EXTENT_HITS FREED_EXTENTS
FREE_REQUESTS   MAX_SIZE MAX_BLOCKS MAX_USED_SIZE MAX_USED_BLOCKS MAX_SORT_SIZE MAX_SORT_BLOCKS RELATIVE_FNO
TEMP                                       0             0         128             1           460     58880     460       58880            0           0           460         505          2809
            1       2809     359552           460           58880           460           58880            0
Elapsed: 00:00:00.04
10:43:13 < ... > select * from v$sort_segment;
TABLESPACE_NAME                 SEGMENT_FILE SEGMENT_BLOCK EXTENT_SIZE CURRENT_USERS TOTAL_EXTENTS TOTAL_BLOCKS USED_EXTENTS USED_BLOCKS FREE_EXTENTS FREE_BLOCKS ADDED_EXTENTS EXTENT_HITS FREED_EXTENTS
FREE_REQUESTS   MAX_SIZE MAX_BLOCKS MAX_USED_SIZE MAX_USED_BLOCKS MAX_SORT_SIZE MAX_SORT_BLOCKS RELATIVE_FNO
TEMP                                       0             0         128             0           460     58880       0           0          460       58880           460         505          2809
            1       2809     359552           460           58880           460           58880            0
Elapsed: 00:00:00.02My DBA had previously instructed me to issue this command to try to avoid this error:
alter database tempfile '...' resize 12g;I do that, but I still only show 460 free segments. Can someone point me to some documentation on how to make the Free Extents be larger than 460?
Here's my client info:
SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 6 10:40:39 2012
Copyright (c) 1982, 2011, Oracle. All rights reserved.Here's my server info:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Given that you appear to be able to add/increase temp files, you are also likely to be able to see the dba_* views. As a first shot, try:
select sum(bytes) from dba_free_space
where tablespace_name = <name from the error message>If there appears to be sufficient space (no idea what that would be since I do not know how big your objects are) then try something like:
select file_id, block_id, bytes from dba_free_space
where tablespace_name = <name from the error message>
order by bytes descIf you have large amounts of contiginous free space (i.e. the first few rows have a large value for the bytes column) then ther may be something else going on.
If both queries show relativel small values for the amount of free space, you will need to add another datafile to the tablespace, or increase the size of one of the existing datafile.
To see the datafiles in the tablespace use:
select file_name, bytes from dba_data_files
where tablespace_name = <name from the error message>You can increase the size of a datafile using something similar to the alter database command you have for the tempfiles like:
alter database datafile <a quoted full name from dba_data_files> resize some bigger numberJust make sure that the file system has enough free space for the new size.
John

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

ORA-01652: unable to extend temp segment by 8192 in tablespace CDR_TAB

Dear All,
While create index command
"create index idx_CALLED_NO on dbs(CALLED_NO) nologging"
an error occure
ORA-01652: unable to extend temp segment by 8192 in tablespace CDR_TAB
how to retify it.what is the command to add datafile or tablespace......
Using oracle 9i...
Thanks in advance

create tablespace or add index, that you can find out at http://tahiti.oracle.com
You should check space on CDR_TAB.
I think you can create new tablespace
http://download.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_74a.htm#SQLRF01403
Create tablespace CDR_IND datafile 'xxx' ...After that create index
create index idx_CALLED_NO on dbs(CALLED_NO) nologging tablespace CDR_IND ;Good Luck;)

System copy export - error message unable to extend temp segment PSAPTEMP

I am performing an export of ECC ABAP+java instance and during the export of the source system I get the following error during the ABAP export:
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
ORA-27072: File I/O error
What do I need to do with this error? I have extended the tablespace via brtools but still getting the error.
Is this because I did not select the shutdown instance during the export? or do I need to do something more via brtools to the PSAPTEMP tablesapce?
I am running on Oracle 10.2.0.2. unix
Thanks
Mikie

Hello Mike,
>> My PSAPTEMP is 8GB.
I would bet the table you try to export is bigger (if you export sorted.. you will need temp space)
>> You have said you increased it to 800GB, that is almost a terabyte. Is this correct?
>> If so, how did you arrive at this figure.
As i already said .. this was the temp space that i needed in a sorted exported with many parallel exports (splitted packages and splitted tables). The system that i have migrated was round about 3 TB and we need to do it very fast.. so i needed the temporary space for the many parallel actions... but this should not be the "normal" case if you have no specific values.
>> And if you could define how you extended PSAPTEMP. Did you use brtools?
I have extended it manually (over sqlplus) .. i have monitored it in my test cases with the view V$TEMPSEG_USAGE and increased it if necessary.
>> did you recreate PSAPTEMP via SQLPLUS size 800GB and then dropped it and recreated to normal size?
No, in my case i have exported and imported it at the same time (distribution monitor) so there was no need to drop it after the export, because i have build up a new target database. But under normal conditions you would only drop the tempfiles after your work has been done. This is possible with Oracle 10g (with some restrictions).
=> http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3002.htm#i2093894
Restrictions on Dropping Files To drop a datafile or tempfile, the datafile or tempfile:
- Must be empty.
- Cannot be the first file that was created in the tablespace. In such cases, drop the tablespace instead.
- Cannot be in a read-only tablespace.
Regards
Stefan

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

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

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

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

Unable to extend temp segment in permanent tablespace

Dear all,
I have a tablespace where I have set all the datafiles to autoextend on.. I have enough storage on the file system.. but even then, am getting error :
ORA-1652: unable to extend temp segment by 128 in tablespace EMPTBS
Moreover, this is a permanent tablespace , why it is giving me the error : temp segment ?
Any idea ?
KAI

Kai,
Pl see if the explanation in ML Doc 19047.1 (OERR: ORA 1652 unable to extend temp segment by %s in tablespace %s) helps
HTH
Srini

Unable to extend TEMP segment even after adding fresh temp files

Similar Messages

Maybe you are looking for