Unable to extend temp segment by 128 in tablespace PSAPTEMP
Hi everybody!
While processing a UNICODE coversion with SAPINST on my SAP NW2004s system (AIX 5,2 - Oracle 10.2 - BW 7.0) into my.SAPDFACT_1.log file the following errors occured:
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "HBQ20080503070541 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "si088ss1 "
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "si088ss1"
(GSI) INFO: release = "2"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "0031832B4C00"
(DB) INFO: /BIC/FZHPY_LIM created #20080503200234
(IMP) INFO: import of /BIC/FZHPY_LIM completed (133182692 rows) #20080503212420
DbSl Trace: Error 1652 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1652 occurred when executing SQL stmt (parse error offset=42)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "/BIC/FZHPY_LIM~0" ON "/BIC/FZHPY_LIM" ( "KEY_ZHPY_LIMP", "KEY_ZHPY_LIMT", "KEY_ZHPY_LIMU", "KEY_ZHPY_LIM2", "KEY_ZHPY_LIM3", "KEY_ZHPY_LIM4", "KEY_ZH
PY_LIM5", "KEY_ZHPY_LIM6", "KEY_ZHPY_LIM7" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(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
Anybody can help me?
Thanks a lot!
Hi Stefan!
desc SAPSR3."/BIC/FZHPY_LIM";
Name Null? Type
KEY_ZHPY_LIMP NOT NULL NUMBER(10)
KEY_ZHPY_LIMT NOT NULL NUMBER(10)
KEY_ZHPY_LIMU NOT NULL NUMBER(10)
KEY_ZHPY_LIM2 NOT NULL NUMBER(10)
KEY_ZHPY_LIM3 NOT NULL NUMBER(10)
KEY_ZHPY_LIM4 NOT NULL NUMBER(10)
KEY_ZHPY_LIM5 NOT NULL NUMBER(10)
KEY_ZHPY_LIM6 NOT NULL NUMBER(10)
KEY_ZHPY_LIM7 NOT NULL NUMBER(10)
/BIC/ZHCONTING NOT NULL NUMBER(17,2)
/BIC/ZHD_IMP NOT NULL NUMBER(17,2)
/BIC/ZHPERC2 NOT NULL NUMBER(10)
SELECT AVG_ROW_LEN FROM ALL_TABLES WHERE TABLE_NAME = '/BIC/FZHPY_LIM';
AVG_ROW_LEN
SELECT BYTES, BLOCKS FROM DBA_SEGMENTS WHERE SEGMENT_NAME = '/BIC/FZHPY_LIM';
BYTES BLOCKS
7180648448 876544
SELECT FILE_NAME, TABLESPACE_NAME, BYTES, BLOCKS, AUTOEXTENSIBLE, MAXBYTES, MAXBLOCKS FROM DBA_TEMP_FILES;
FILE_NAME
TABLESPACE_NAME BYTES BLOCKS AUT MAXBYTES MAXBLOCKS
/oracle/HBQ/sapdata1/temp_1/temp.data1
PSAPTEMP 1048576000 128000 YES 1.0486E+10 1280000
/oracle/HBQ/sapdata1/temp_1/temp2.data1
PSAPTEMP 298844160 36480 YES 3.4359E+10 4194176
Thanks.
Similar Messages
-
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
Hi Everybody;
My coleague who is an bw consultant facing given below problem in BW production server.
Error reading the data of InfoProvider ZN_IVLTD
Error when generating the sql statement.
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
I checked table space PSAPTEMP as well but its showing o% used.
Kindly help how can i resolve this problem.
Regards
SantoshHi Santosh,
There is also this thread going on, check if anything will be useful for you.
Two SAP Instances (DEV & QAS) on singe windows host.
One problem that I have noticed on UNIX systems for PSAPTEMP, refer to the this note if your OS is UNIX.
548221 - Temporary Files are created as sparse files
Regards,
Nilesh -
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,
balaramHI,
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-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
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
IshuHi,
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.
-RI 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 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-------------0Unless 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 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)
Tks843277 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 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
Jaganwhat 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 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 regardsHi,
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. -
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 -
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 selectedHello,
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 -
Unable to extend temp segment by 128
Hello
In our Company an erp is running very well.
All reports were running very fine. and forms lov also.
an error is comming when seen from sql
unable to extend temp segment by 128 in tablespace MAKESS_TEMP
for e.g
1 select e.vc_group_desc,f.vc_sub_group_desc,
2 to_number(substr(d.vc_invoice_no,3)) inv_no1,d.dt_invoice_date inv_date,
3 b.vc_item_group,b.vc_item_sub_group,
4 d.vc_item_code,d.vc_item_desc,d.vc_unit,d.vc_invoice_no,d.dt_invoice_date,
5 d.nu_item_disc,
6 d.vc_invoice_no inv_no,
7 d.vc_cust_name cf_cust_name,d.nu_tot_sale_val,
8 d.nu_tot_charge charge,d.nu_tot_disc disc,
9 d.nu_tot_freight freight,d.nu_product_quantity,d.nu_product_rate,
10 d.nu_item_val ,d.vc_voucher_no voucher_no,
11 d.nu_tot_cycle_val,d.nu_tot_parts_val
12 from dt_sale_invent d,
13 makess.mst_item b,
14 mst_group e,mst_sub_group f
15 where
16 f.vc_comp_code='01'
17 and f.vc_sub_group_code=b.vc_item_sub_group
18 and e.vc_comp_code='01'
19 and e.vc_group_code=b.vc_item_group
20 and b.vc_comp_code='01'
21 and b.vc_item_code =d.vc_item_code
22 and d.vc_comp_code='01'
23 and d.dt_invoice_date between '01-APR-03' AND '31-MAR-04'
24 and e.vc_group_code='66'
25 and d.vc_item_group='66'
26* order by 2,4,3
SQL> /
from dt_sale_invent d,
ERROR at line 12:
ORA-01652: unable to extend temp segment by 128 in tablespace MAKESS_TEMP
here makess_temp is temporary tablespace
i have seen makess_temp.ora file size has gone to 16 GB
This tablespace was generated by this query
CREATE TEMPORARY TABLESPACE makess_temp TEMPFILE 'D:\ORACLE9I\avondata\avon\maketemp.ora' SIZE 200M AUTOEXTEND ON NEXT 20M DEFAULT STORAGE ( INITIAL 100K NEXT 100K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 1 );
pls recommend me what to do,how to increase its sizeAs Jeroen suggests, you could add a datafile to your temp tablespace, but, I'm not sure that that is your problem.
Unless your tables are really huge (and I mean several tens of Gb each), and that query actually returns a substantial percentage of the rows in the tables, I don't see why it would use 16Gb of temp.
I would re-create the temp tablespace with:
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M
for starters. Minimally, I would set pctincrease to 0.
I would also look at the the Explain Plan for the query to see if there are a lot of sort joins going on. Make sure that the tables and indexes are analyzed properly so the statistics are up to date.
HTH
John
Maybe you are looking for
-
SMI error on Web UI of SNC 5.1
Dear experts, I'm working on SMI (Supplier Managed Inventory) implementation with SAP SNC 5.1. I'm trying to do a demo on SNC. At moment I have: 1) Created our set of master data. 2) Configured the CIF communication to send from ECC to SNC the maser
-
If I want to remove CS2 from my HD are there any other files to look for than these: Applications/Photoshop CS2 User/Library/Application Support/Adobe/Bridge User/Library/Preferences/Any CS2, ACR3 and Bridge Library/Application Support/Adobe/Plug-Ins
-
Ipod Classic 6th Gen 160 GB wont Restore (Error 1439)
So I just purchased an iPod today knowing it was having problems. I had looked online before hand to find fixes, and thought it would be easy enough to fix. But I guess not. I called support, bad idea. They were absolutely useless (they couldn't help
-
PDF missing some text from FM 9 using Acrobat 9.2
When I generate a PDF frome FM 9, it's missing some of the text (non-bold) and one of the chapters is missing the chapter number in the TOC. It worked fine with Acrobat 6.0, but now I'm using Acrobat 9.2 and some text is missing. Any suggestions? Th
-
Can you run MRP against a sales order , if so which tcode can i use to accomplish this. Thank you