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

Similar Messages

  • READER_1_1_1RR_4035SQL Error [ ORA-01652: unable to extend temp segment b

    Hi,
    I am still facing the error for table space evnthough datafile is avl
    READER_1_1_1     RR_4035     SQL Error [
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT
    ONLINE     DATA     PERMANENT     LOCAL     200     0.063     0.03
    ONLINE     DEV1_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV1_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV1_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     DEV_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     EXAMPLE     PERMANENT     LOCAL     975.188     109.125     11.19
    ONLINE     FLA_TBS1     PERMANENT     LOCAL     10     0.063     0.63
    ONLINE     MES_DW2     PERMANENT     LOCAL     2,091.19     1,794.19     85.8
    ONLINE     SYSAUX     PERMANENT     LOCAL     1,245.38     906.938     72.82
    ONLINE     SYSTEM     PERMANENT     LOCAL     3,300.00     2,429.44     73.62
    ONLINE     TEMP     TEMPORARY     LOCAL     24,458.00     5,020.00     20.52
    ONLINE     TOOLS     PERMANENT     LOCAL     1,050.00     0.063     0.01
    ONLINE     UNDOTBS1     UNDO     LOCAL     2,670.00     95.438     3.57
    ONLINE     USERS     PERMANENT     LOCAL     43,530.98     30,366.30     69.76

    No Sense:
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    tablespace TEMP2
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT
    ONLINE     DATA     PERMANENT     LOCAL     200     0.063     0.03
    ONLINE     DEV1_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV1_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV1_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     DEV_BIPLATFORM     PERMANENT     LOCAL     64     44.313     69.24
    ONLINE     DEV_IAS_TEMP     TEMPORARY     LOCAL     100     0     0
    ONLINE     DEV_MDS     PERMANENT     LOCAL     100     5.438     5.44
    ONLINE     EXAMPLE     PERMANENT     LOCAL     975.188     109.125     11.19
    ONLINE     FLA_TBS1     PERMANENT     LOCAL     10     0.063     0.63
    ONLINE     MES_DW2     PERMANENT     LOCAL     2,091.19     1,794.19     85.8
    ONLINE     SYSAUX     PERMANENT     LOCAL     1,245.38     906.938     72.82
    ONLINE     SYSTEM     PERMANENT     LOCAL     3,300.00     2,429.44     73.62
    ONLINE     TEMP     TEMPORARY     LOCAL     24,458.00     5,020.00     20.52
    ONLINE     TOOLS     PERMANENT     LOCAL     1,050.00     0.063     0.01
    ONLINE     UNDOTBS1     UNDO     LOCAL     2,670.00     95.438     3.57
    ONLINE     USERS     PERMANENT     LOCAL     43,530.98     30,366.30     69.76
    tablespace TEMP2 doesn't exist.
    i used statement
    ALTER TABLESPACE temp
    ADD TEMPFILE 'D:\app\TEMP16.DBF' SIZE 128M autoextend on;
    ALTER TABLESPACE
    USERS ADD DATAFILE 'D:\app\SYS00.DBF' SIZE 1080M autoextend on;
    alter user DATAWAREHOUSE quota unlimited on USERS
    why add datafile in user tablespace¿?
    and you solved the issue doing the same like we told you a few days before in:
    ORA-1652: unable to extend temp segment by 128 in tablespace
    unable to create INITIAL extent for segment in tablespace USERS
    Remember close your threads:
    896398     
    Handle:      896398 
    Status Level:      Newbie
    Registered:      Nov 9, 2011
    Total Posts:      530
    Total Questions:      158 (116 unresolved)

  • Trying to install inDesign.  Receiving error message: Unable to extract Temp Directory (EX11)

    Trying to install inDesign.  Receiving error message: Unable to extract Temp Directory (EX11)

    Creative Cloud Error Codes (WIP) | Mylenium's Error Code Database
    Mylenium

  • Unable to extend temp segment by 4096 in tablespace  error

    Hi
    Can some help me resolving this problem .which occured when i try to import some dump file to an user.
    ORA-39171: Job is experiencing a resumable wait.
    ORA-01652: unable to extend temp segment by 4096 in tablespace HDM_INDEX
    i added 2 gb of datafile to the table space it is still shows the same .
    any expert suggestion is highly apprciated.
    thanks

    790072 wrote:
    Hi
    Can some help me resolving this problem .which occured when i try to import some dump file to an user.
    Pl post details of OS and database versions, along with the complete import command and parameters used.
    ORA-39171: Job is experiencing a resumable wait.
    ORA-01652: unable to extend temp segment by 4096 in tablespace HDM_INDEX
    i added 2 gb of datafile to the table space it is still shows the same .Pl identify the tablespace you added space to (and the commands used to add space)
    >
    any expert suggestion is highly apprciated.Pl post relevant sections from the database alert.log
    >
    >
    thanks
    ORA-1652 Error Troubleshooting          [Document 793380.1]
    ORA-01652: Estimate Space Needed to CREATE INDEX          [Document 100492.1]
    TROUBLESHOOTING GUIDE (TSG) - UNABLE TO EXTEND Errors          [Document 1025288.6]
    HTH
    Srini

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

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

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

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

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

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

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

    ORA-01652: unable to extend temp segment by 256 in tablespace HDM_DBUSER_TEMP
    HI GURUS PLEASE HELP ME,
    I Have 9i database on solaris version 9,
    i am repeatedly getting the following error in the alert.log file.
    Failed write to clobORA-01652: unable to extend temp segment by 256 in tablespace HDM_DBUSER_TEMP
    using the meta link Doc ID:     280578.1, i have increased the temp TS, but still getting the same alert message in alert.log file.
    In metalink it is given second solution,
    If there is severe temp segment space contention across instances, a
    slowdown can occur. The following are potential workarounds:
    - Increase size of the temp tablespace
    - Do not use the DEFAULT temp tablespace feature in RAC.
    - Increase sort_area_size and/or pga_aggregate_target "
    I have increased the size of the temp TS, but the error is poping up still in alert.log.
    I don't know how to assign DEFAULT temp tablespace feature in RAC????
    SQL> select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks
    from gv$sort_segment; 2 ^R
    from gv$sort_segment;
    INST_ID TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
    1 TEMP 2304 0 2304
    1 HDM_DBUSER_TEMP 519424 519424 0
    PLEASE Help !!!
    Thanks in advance

    Hello,
    Add additional datafile to followign tablespace, also post out of the followign command
    SELECT dt.tablespace_name,
           file_name,
           bytes,
           extent_management,
           segment_space_management
    FROM dba_tablespaces dt, dba_data_files ddf
    WHERE dt.tablespace_name = ddf.tablespace_name;
    ALTER TABLESPACE hdm_dbuser_temp ADD DATAFILE '/location/...' SIZE 512M
          AUTOEXTEND ON NEXT 256M MAXSIZE 4096M;   -- or unlimited on 8192 MRegards

  • 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-01652 unable to extend temp segment in 11gR2 with ASM and 2 node RAC

    Hi ,
    I have a 11.2.0.1 system with 2 node RAC and ASM . We are hitting ORA-01652 very frequently
    and I can see space is available in TEMP .
    CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
    SIZE 21474836480,
    SIZE 137437904896
    AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M ( Will the next size ignored as the extent size is 1MB ?)
    EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    And during the failure
    SELECT tablespace_name,
    total_blocks,
    used_blocks,
    free_blocks,
    total_blocks*32768/1024/1024 as total_MB,
    used_blocks*32768/1024/1024 as used_MB,
    free_blocks*32768/1024/1024 as free_MB
    FROM gv$sort_segment;
    TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB
    TEMP 4849568 2385728 2463840 151549 74554 76995
    TEMP 0 0 0 0 0 0
    Also when I checked from v$sort_usage I see only two session consuming space
    SQL> SELECT b.tablespace tablespace,
    2 -- b.segfile#,
    3 -- b.segblk#,
    4 b.blocks,
    5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
    6 a.sid,
    7 a.username username,
    8 a.osuser osuser,
    9 a.inst_id,a.sid,a.serial#,a.module
    10 FROM gv$session a, gv$sort_usage b
    11 WHERE a.saddr = b.session_addr and
    12 b.blocks != 16 and
    13 a.inst_id = b.inst_id
    14 ORDER BY b.tablespace, b.blocks, bytes desc;
    BLOCKS BYTES SID USERNAME OSUSER INST_ID SID SERIAL# MODULE
    1,192,864 37277 381 CN obiqb 2 381 860 nqsserver@icmqapp01cdp (TNS V1
    1,192,864 37277 3952 CN obiqb 2 3952 1374 nqsserver@icmqapp01cdp (TNS V1
    2,385,728 74554 (mb)
    Wat is causing the 1652 ?

    877394 wrote:
    Thanks Srini,
    But I did try all that notes with no luck .
    I have a temporary tablespace with 150gb (130+20) datafiles .
    TABLESPACE_NAME FILE_NAME (BYTES/1024/1024)
    TEMP +DATA_01/tempfile/temp.314.743964            131071
    TEMP +DATA_01/tempfile/temp.312.757303             20480
    and the DDL is
    CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
    SIZE 21474836480,
    SIZE 137437904896
    AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M
    EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
    And on querying v$sort_usage
    SQL> SELECT b.tablespace tablespace,
    2 -- b.segfile#,
    3 -- b.segblk#,
    4 b.blocks,
    5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
    6 a.sid,
    7 a.username username,
    8 a.osuser osuser,
    9 a.inst_id,a.sid,a.serial#,a.module
    10 FROM gv$session a, gv$sort_usage b
    11 WHERE a.saddr = b.session_addr and
    12 b.blocks != 16 and
    13 a.inst_id = b.inst_id
    14 ORDER BY b.tablespace, b.blocks, bytes desc;
    TABLESPACE BLOCKS BYTES SID OSUSER INST_ID SID SERIAL# MODULE
    TEMP 63,328 1,979 3952 CN 2 3952 1374
    TEMP 84,384 2,637 381 CN 2 381 860
    TEMP 433,184 13,537 381 CN 2 381 860
    TEMP 1,117,728 34,929 3952 CN 2 3952 1374
    sum 1,698,624 53,082 (mb)
    So the space utilization was less than 150gb and on querying v$sort_Segment
    SQL> SELECT tablespace_name,
    total_blocks,
    used_blocks,
    free_blocks,
    total_blocks*32768/1024/1024 as total_MB,
    used_blocks*32768/1024/1024 as used_MB,
    free_blocks*32768/1024/1024 as free_MB
    FROM gv$sort_segment;
    TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB inst
    TEMP 4849568 2311104 2538464 151549 72222 79327 2
    TEMP 0 0 0 0 0 0 1
    why for inst 1 it is showing 0 (which means no sort is happening in instance 1)
    But still we got the error
    ORA-1652: unable to extend temp segment by 32 in tablespace TEMP
    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 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

Maybe you are looking for