Temp segments full

Hi,
There is a report based on a select which includes several tables, views and an inner select. In the last several years, any date will give no more than a couple of hundred records except for one day in 2006 when there are almost 3,000 records, and November 8th of this year when there are over 7,000 records.
The report is fine except when it includes those two days. However, running the select in plsql is no problem at all (results within a couple of seconds). It is only in Discoverer where a message will come up that the temp segments are full.
Can anyone give me a suggestion as to what to look for in order that I can change the sql?
Thanks.
Leah

Hi Srini,
Thanks for responding. In the meantime I received a response from Metalink. Apparently the sql that is being formed by discoverer is different than the custom sql folder. I am supposed to run the sql that was executed in Discoverer in sql*plus. I am waiting for sql*plus to be installed in my computer at work.
Thanks. I will be happy to update this thread with the results.
Leah

Similar Messages

Error: ORA-01652: Unable to extend temp segment by 128

Hello.
The error occured when I tried to execute a complex query. I saw that my temp file is 30GB and it's hard to believe that it's getting full by this query!!!
There is an analytic function used in the query and probably it is causing the huge need of space. Here is the execution plan of the query:
SELECT STATEMENT, GOAL = CHOOSE               Cost=3455606     Cardinality=3615949     Bytes=636407024          IO cost=3455606     Optimizer=CHOOSE          Timestamp=19.3.2007 ã. 11:00:08
WINDOW SORT               Cost=3455606     Cardinality=3615949     Bytes=636407024          IO cost=3455606               Timestamp=19.3.2007 ã. 11:00:08
FILTER                                                  Timestamp=19.3.2007 ã. 11:00:08
HASH JOIN OUTER                                                  Timestamp=19.3.2007 ã. 11:00:08
HASH JOIN OUTER               Cost=6610     Cardinality=20963     Bytes=2683264          IO cost=6610               Timestamp=19.3.2007 ã. 11:00:08
HASH JOIN               Cost=6572     Cardinality=20963     Bytes=2096300          IO cost=6572               Timestamp=19.3.2007 ã. 11:00:08
PARTITION RANGE SINGLE                                                  Timestamp=19.3.2007 ã. 11:00:08
TABLE ACCESS FULL     Object owner=RS     Object name=LOANS     Cost=369     Cardinality=24551     Bytes=1104795          IO cost=369     Optimizer=ANALYZED          Timestamp=19.3.2007 ã. 11:00:08
TABLE ACCESS FULL     Object owner=RS     Object name=LOAN_PLANS     Cost=5629     Cardinality=826902     Bytes=45479610          IO cost=5629     Optimizer=ANALYZED          Timestamp=19.3.2007 ã. 11:00:08
TABLE ACCESS FULL     Object owner=RS     Object name=EXCH_RATES     Cost=2     Cardinality=1     Bytes=28          IO cost=2     Optimizer=ANALYZED          Timestamp=19.3.2007 ã. 11:00:08
VIEW     Object owner=MDR          Cost=3203514     Cardinality=167045285     Bytes=8018173680                         Timestamp=19.3.2007 ã. 11:00:08
WINDOW SORT               Cost=3203514     Cardinality=167045285     Bytes=13530668085          IO cost=3203514               Timestamp=19.3.2007 ã. 11:00:08
HASH JOIN               Cost=6667     Cardinality=167045285     Bytes=13530668085          IO cost=6667               Timestamp=19.3.2007 ã. 11:00:08
PARTITION RANGE SINGLE                                                  Timestamp=19.3.2007 ã. 11:00:08
TABLE ACCESS FULL     Object owner=RS     Object name=LOANS     Cost=369     Cardinality=48079     Bytes=2067397          IO cost=369     Optimizer=ANALYZED          Timestamp=19.3.2007 ã. 11:00:08
TABLE ACCESS FULL     Object owner=RS     Object name=LOAN_PLANS     Cost=5629     Cardinality=826902     Bytes=31422276          IO cost=5629     Optimizer=ANALYZED          Timestamp=19.3.2007 ã. 11:00:08
So I have 3 questions that I'm fighting with since last week:
1) Why the windowing clause of the analytic function requires so many resources since I have index on the "partition by" and "order by" clauses? Is there any way to optimize it?
2) Is it possible for the query to fill all the 30GB of the temp segment? The table that the query selects from has 4 million records.
3) What can I do to run successfully my query?
Thanks.

FYI, here is the query:
INSERT INTO LoanPlans ( LoanRefNum, NumFlow, DateFlow, AmtFlowPrinc, AmtFlowInt)
SELECT t1.event || t1.branch || t1.amendm Field1,
Row_Number() over
(partition by t1.branch,t1.event,t1.amendm
order by t1.inst_nbr) Field2,
t1.mat_date Field3, t1.inst_principal*t3.ind_rate Field4,
t1."INT"*t3.ind_rate Field5
FROM RS.LOAN_PLANS t1 INNER JOIN
RS.LOANS t2 ON (t1.event=t2.event AND
t1.branch=t2.branch AND t1.amendm=t2.amendm AND
t1.DATE_KEY = t2.DATE_KEY) LEFT JOIN
( SELECT t2.branch branch, t2.event event, t2.amendm amendm,
SUM(t1.inst_principal) over
(partition by t1.branch, t1.event, t1.amendm
order by t1.inst_nbr) sum_inst,
t2.inst_nbr inst_nbr, t2.releas - t2.capital_payd inst_rest
FROM RS.LOANS t2 INNER JOIN
RS.LOAN_PLANS t1 ON (t2.branch = t1.branch AND
t2.event = t2.event AND t2.amendm = t1.amendm AND
t2.DATE_KEY = t1.DATE_KEY)
) q ON (t1.branch = q.branch AND t1.event = q.event AND
t1.amendm = q.amendm) LEFT JOIN
RS.EXCH_RATES t3 ON (t1.currency = t3.currency AND
t1.DATE_KEY = t3.DATE_KEY AND t1.DATE_KEY = t3.acc_date)

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-01652: unable to extend temp segment by 1280 in tablespace TEMP

We have a lot of version 8.5 crystal report templates, now, as required, we want to use JRC (pure java) to export those templates to PDF / RTF etc.
We have done a lot, for the most of templates, works fine, but there are some reports, once the data is large, an error coming :ORA-01652: unable to extend temp segment by 1280 in tablespace TEMP
for this problem:
1. I have read the migration guide first :http://support.businessobjects.com/communityCS/TechnicalPapers/cr_xi_designer_migration.pdf
2. I have tested the templates with the same parameters in designer, they are just fine ( and obviously, the old templates can work with COM components in wintel platform , we used VB )
3. Because 2 works fine, I tried to extend our oracle temporary tablespace, but everytime I extend, I can see it will always be fully occupied by the JRC export function.
4. The problem is occured in the repSrc.export(expOpt, reqCont) function
I am now trying to find out the reasons:
1. checking the parameters real value in the report
2. enable log4j for JRC to see the real SQL statement
This is really annoying problem, I would appreciate if anyone could give me help.

I think this is one might have some relationship with my problem
http://diamond.businessobjects.com/node/477
I found in version 8.5, the created SQL Statement is simple, all conditions come under Where clause, but the new crystal report XI convert this to "join" types.
But JRC engine will lost some very important join condition to make the result really large, so, my oracle error comes out.
I am thinking about to write command object as a workaround for this issue, woundn't JRC engine support the simple SQL Statement?
I found the release note of CR4E says some features are "Supported" instead of "Full Support", where can I find the detail list of these un-supported feature list?

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

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.

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.

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

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

Unalbe to extend temp segment

Hi, i am facing a error frequently in my alert log file .Ora-1652 unable to extend temp segment by 128 bytes.i even increased the temporary tablespace size to 4 gb from 1.5 gb ,still i am facing the problem.Even if i shut my database and again startup my dtabase my temp space is showing free_bytes=0. i am not able to get rid of this problem.
Thanks in advance
Kishore

Always the Temp segment Space shows Zero. Please check whether you are still getting the temp segment error.
It shoud not shouw this error once you increased the space.
Thanks
Ashok Salimath

Temp segments full

Similar Messages

Maybe you are looking for