Unable to extend temp segment by 64 in tablespace TEMP

hi,
anyone can help on this issue. I have a procedure in this procedure one statement
INSERT INTO prod.temp select * from .........
this statement giving the unable to extend temp segment by 64 in tablespace TEMP
error.
this is a big query.
when we run that procedure in development and testing environmenmt it's running fine but in staging database it's given the trouble.
when DBA extent the temp tablespace upto 10gb.

If »prod.temp« is empty and truncated you can try append hint:
INSERT /*+ append */ INTO prod.temp select * from .........In addition try to remove any sortings from your »select *« statement.
Edited by: michaels2 on Jan 16, 2009 3:05 PM

Similar Messages

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

  • 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

  • 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

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

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

  • How to find which query ORA-1652: unable to extend temp segment by 128 in

    How can i find which query caused the below error,the query is not running currently
    ORACLE ERRORS IN ALERTS LOG dnb2stg3 - lnx300 on Thu Jun 17 12:10:01 EDT 2010
    1 ORA-1652: unable to extend temp segment by 128 in tablespace TEMP_SCHED
    SQL> select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks from gv$sort_segment;
    INST_ID TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
    1 TEMP 638336 0 638336
    4 TEMP 565760 0 565760
    4 TEMP_SCHED 16776704 0 16776704
    3 TEMP 484864 0 484864
    3 TEMP_SCHED 0 0 0
    2 TEMP 455808 0 455808
    6 rows selected.
    SQL> SQL> SELECT S.sid || ',' || S.serial# sid_serial, S.username,
    2 T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
    3 T.sqladdr address, Q.hash_value, Q.sql_text
    FROM v$sort_usage T, gv$session S, gv$sqlarea Q, dba_tablespaces TBS
    4 5 WHERE T.session_addr = S.saddr
    6 AND T.sqladdr = Q.address (+)
    7 AND T.tablespace = TBS.tablespace_name
    8 ORDER BY S.sid;
    no rows selected

    Hello,
    You may try to catch the SQL with a Servererror Trigger.
    This link will give you an interesting example:
    http://oratips-ddf.blogspot.com/2008/09/to-err-is-human.html
    Hope this help.
    Best regards,
    Jean-Valentin

  • 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

  • Query to find which past ses caused ORA-1652: unable to extend temp segment

    Hi,
    I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
    I have generated the AWR report but not able to figure it out which sessions caused this error.
    Thanks in advance

    913410 wrote:
    Hi,
    I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
    I have generated the AWR report but not able to figure it out which sessions caused this error.
    Thanks in advance
    01652, 00000, "unable to extend temp segment by %s in tablespace %s"
    // *Cause:  Failed to allocate an extent of the required number of blocks for
    //          a temporary segment in the tablespace indicated.
    // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
    //          files to the tablespace indicated.

Maybe you are looking for