Unable to extend segment by 128 in tablespace

Hi experts;
Initially this may seem a simple thing to fix, and I understand that it is. My confusion comes because when I check thru OEM the size of one tablespace is 1,500 MB; Used Percent = 0.0; Free = 1.500 MB. Has a datafile which has a size of 1500 MB, and used 1499 MB. I have NO warning messages about the size of the tablespace, and the warning threshold is 85%.
Any suggestion to do in this case? Why If I get a tablespace with 100% free and when I try to do a sort of a table thru sql developer I get the message ORA-01652: Unable to extend temp segment by 128 in tablespace RADIUS_DATA_TEMP?
Any comments, idea, suggestion will be appreciated.
Regards
Al

user12048358 wrote:
Hi experts;
Initially this may seem a simple thing to fix, and I understand that it is. My confusion comes because when I check thru OEM the size of one tablespace is 1,500 MB; Used Percent = 0.0; Free = 1.500 MB. Has a datafile which has a size of 1500 MB, and used 1499 MB. I have NO warning messages about the size of the tablespace, and the warning threshold is 85%.
Any suggestion to do in this case? Why If I get a tablespace with 100% free and when I try to do a sort of a table thru sql developer I get the message ORA-01652: Unable to extend temp segment by 128 in tablespace RADIUS_DATA_TEMP?
Any comments, idea, suggestion will be appreciated.
Regards
AlThat is a SMALL tablespace.
Let's say you are attempting to populate a table in this tablespace with 2MB worth of data.
It starts to populate the table, runs out of disk space, throws the error & does ROLLBACK so it remains empty.
so what is the confusion?
You need to make the TS larger.

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

  • ORA-1652: unable to extend temp segment by 128 in tablespace

    HI,
    i am getting an error in alert log file.....
    Thread 1 advanced to log sequence 1758
      Current log# 2 seq# 1758 mem# 0: /dev/vx/rdsk/racdg/orcl_raw_log12
    Mon Sep  8 12:34:16 2008
    ARC1: Evaluating archive   log 1 thread 1 sequence 1757
    ARC1: Beginning to archive log 1 thread 1 sequence 1757
    Creating archive destination LOG_ARCHIVE_DEST_1: '/arch/log/1_1757.dbf'
    ARC1: Completed archiving  log 1 thread 1 sequence 1757
    Mon Sep  8 13:04:26 2008
    Completed checkpoint up to RBA [0x6de.2.10], SCN: 0x0000.6c1f757f
    Mon Sep  8 13:49:16 2008
    ORA-1652: unable to extend temp segment by 128 in tablespace                 TEMPI don';t want to add datafile
    SQL> select bytes,maxbytes,increment_by from dba_temp_files;
         BYTES   MAXBYTES INCREMENT_BY
    6134169600          0            0
    SQL> select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;
    TABLESPACE_NAME                BYTES_USED BYTES_FREE
    TEMP                           6037700608   96468992i have also referred metalink note: 19047.1
    Is there any way to avoid this problem without adding any datafile........

    how to find out which session is using temp tablespace
    SQL> select * from v$sort_usage;
    USERNAME                       USER                           SESSION_ADDR
    SESSION_NUM SQLADDR             SQLHASH TABLESPACE
    CONTENTS  SEGTYPE     SEGFILE#    SEGBLK#    EXTENTS     BLOCKS   SEGRFNO#
    DATA3                        DATA3                        000000044D84F558
          25860 00                        0 TEMP
    TEMPORARY DATA             201     183561          1        128          1pls correct me if the above query is worng to find out the no. of session s using temp tablespace
    i think we have already allocated good amt of space to pga_aggregate_target
    SQL> show parameter pga
    NAME                                 TYPE        VALUE
    pga_aggregate_target                 big integer 524288000
    SQL>Edited by: user00726 on Sep 8, 2008 2:29 AM

  • ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

    Hi,
    I am getting the following error while executing an insert query.
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP.
    I have tried increasing the TEMP tbsp size it got resolved temporarily but occurred again after few days.
    When the problem occured, following query shows all insert queries in TEMP tablespace and one of them consumes about 5GB and others are about 24MB.
    SELECT S.sid || ',' || S.serial# sid_serial, S.username,
    T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
    T.sqladdr address, Q.hash_value, Q.sql_text
    FROM v$sort_usage T, v$session S, v$sqlarea Q, dba_tablespaces TBS
    WHERE T.session_addr = S.saddr
    AND T.sqladdr = Q.address (+)
    AND T.tablespace = TBS.tablespace_name
    ORDER BY S.sid;
    The insert query is :
    INSERT INTO SEOSDATA (ENTRYID,DOMAINNAME,USERNAME,EVENTTYPE,LOGNAME,TIMSTAMP,SOURCE,COMPUTERNAME,EVENTID,EVENTCATEGORY,SEARCHSTRINGS,MSGTEXT) VALUES (ENTRYID_SEQ.NEXTVAL,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)
    It is not expected that an insert query consumes such a huge memory.
    Can someone help me in figuring out what the problem is.
    What might have gone wrong? Seems like sorting is used, why an insert query uses sorting?
    Regards
    Ishu

    Hi,
    Insert statement should not use TEMP tablespace. Please check with following query which user and session id is using TEMP tablespace.
    SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
    a.username, a.osuser, a.status
    FROM v$session a,v$sort_usage b
    WHERE a.saddr = b.session_addr
    ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
    Dilipkumar Patel.

  • Need help on "unable to extend temp segment by 128 in tablespace TEMP..

    Dear All,
    I recently ported my code from Vs 2003 running on Windows 2003 Server to VS 2010 running on Windows 2008 Server 64bit.
    The DB query that we trigger from the code has not been changed but forming the query is changed.Like in very high level initally I was getting data at execution level so I use sprintf to form the query along with required params and then use SQLExecute. The application runs fine for few hrs after that I get the below error.
    6/23 15:40:11 (4396 0214): ExecuteDirectly::Failed Query is [insert into Test  (bbid, keyOrder, keyLength, keyValue) values (?, ?, ?, ?)]
    06/23 15:40:11 (4396 0214): Encountered ODBC error -1: S1000, 1652, [Oracle][ODBC][Ora]ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
    I am using Oracle 11g client on Windows 2008 Server R2. Surprisingly when we get this temp space issue in the DB, that time when I run the same query through application from a 32bit it is able to execute successfully same doesn't happen with 64bit machine.
    Any suggestion to resolve the above error ?Am I doing a memory leak of something which is causing the above issue.
    Thanks in advance.
    -R

    I was trying to monitor as which inserting is causing this issue.It looks to be the insertion of blob data is causing the issue.When I disable all the insertions of Blob data the temp space issue doesn't come.
    I am seeing some trailing characters in the coloumn when we are inserting Blob. I am doing SQLBindParameter with SQL_C_BINARY and SQL_LONGVARBINARY as InputOutputType and ValueType respectively.Do you see any problem in this.
    Thanks,
    -R

  • ORA-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-1652: unable to extend temp segment by 128 in tablespace   TEMP

    Hi All,
    Today in we have faced the below issue in our production database
    ORA-1652: unable to extend temp segment by 128 in tablespace                 TEMP
    ORA-1652: unable to extend temp segment by 128 in tablespace                 TEMP
    when we checked we are having 99% of free space in temp tablespace,we are not able to understand why we got this error.
    earlier also we got the same issue adding datafile to the tablespace solved the issue. wanted to know if free space exsists why we getting this error.
    Thanks....

    Hi,
    Please check Oracle support id : TROUBLESHOOTING GUIDE (TSG) : ORA-1652: unable to extend temp segment (Doc ID 1267351.1)
    and OTN Form :
    https://forums.oracle.com/thread/457771?start=0&tstart=0
    https://forums.oracle.com/thread/703095?start=0&tstart=0
    Thank you

  • ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1/TEMP2

    db version: 11.1.0.7
    I detect the error log on dbTier's alertlog as below, BUT I think the temp tbs is enough because of the SQL output(you can see as below too)
    so I want to know why and how can I fix it. thanks
    ORA-1652: unable to extend temp segment by 128 in tablespace TEMP1
    ORA-1652: unable to extend temp segment by 128 in tablespace TEMP2
    SQL> select TABLESPACE_NAME,TOTAL_BLOCKS,USED_BLOCKS,FREE_BLOCKS from v$sort_segment;
    TABLESPACE_NAME-------TOTAL_BLOCKS-----------USED_BLOCKS--------------FREE_BLOCKS
    TEMP1 -------------1048448------------9472--------1038976
    TEMP2---------------1048448 -----------5248---------1043200
    TEMP--------0--------0-------------0

    Unless you are running the query against v$sort_segment at the point in time that you are getting the errors, I would strongly suspect that something tried to use more than 16 GB of TEMP space, the query died, and when you subsequently looked, nothing was attempting to use much TEMP space. That doesn't mean that some process wasn't eating up all your TEMP space earlier.
    My guess (no evidence, just a hunch) is that you have a query that is doing a Cartesian join, that query rapidly consumed all the space in the TEMP1 and TEMP2 tablespaces, encountered this error before exiting and freeing all the TEMP1 and TEMP2 space it had acquired before you ran your query.
    Justin

  • ORA-1652: unable to extend temp segment by 128 in tablespace 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

  • 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 by 128 in tablespace TEMP

    Hi all,
    I am using apps 11.5.10.2 and i think this is a database issue
    ERROR at line 1:
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
    Do i have to increase the tablespace, if so how to do it. I don't even know the EM Pass
    Regards
    Jagan

    what is the size of your temp tablespace?
    Have another try, if the problem persists, increase the temp datafile size.
    alter database tempfile <temp file name> resize <integer> M;
    You can also add a new datafile.
    ALTER TABLESPACE name ADD TEMPFILE 'filename.dbf' SIZE 10M;
    You can always investigate and try to avoid too much sort by checking the SQL.
    Jaffar

  • Doubt regarding ORA-30036: unable to extend segment by 8 in undo tablespace

    I am using 11g Release 1 Database .
    I have to analyze the performance of two tables of different designs which serve the same purpose and come up with the design which is efficient .
    SQL> desc staging_dict
    Name                                      Null?    Type
    SNO                                                NUMBER
    CODE_FRAGMENTS                                     CLOB
    CODE_FRAGMENTS_U                                   CLOB
    CODE_FRAGMENTS_D                                   CLOB
    CODE_FRAGMENTS_DO                                  CLOB
    SQL> desc staging_dict1
    Name                                      Null?    Type
    SNO                                                NUMBER
    CODE_FRAGMENTS                                     CLOB
    CODE_FRAGMENTS_UD                                  CLOB
    CODE_TYPE                                          VARCHAR2(5 CHAR)Initially I tried inserting a few thousand records into both the tables . Then I did some conversion on one column and I populate the result on other column of the same table . So I update the table in bulk mode and I commit for every thousand records .
    I have a undo tablespace of 2G with undo_retention=900 , retention guratantee is not set for the undo tablespace .
    When I tried the conversion and update on the first table (STAGING_DICT) it took more time for around 2500 records compared to other table and when I increased the number of records to 10000 it threw an error
    ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS'
    But I didn't come across this error when I tried the conversion and update on the table for the same 2500 records (STAGING_DICT1) and it was also 10 times faster .
    My doubt is does the error ORA-30036 occur because it is saving the undo image of all the four clob columns though I am doing conversion on one column and updating the other column (using only two columns in the update and only one column is affected by update command) ?
    Also how is that having less CLOB rows prove more effective by adding one more VARCHAR column which differentiates the code_frament type in the STAGING_DICT1 table than having it as more CLOB columns as in STAGING_DICT table ?

    Don't you think the error OP reported is kind of weird?
    Because as you said, Oracle stores "undo" of lob in user tablespace not undo tablespace if the lob is stored out-of-line.
    1. If the size of lob was small, small size of undo would be stored into undo tablespace,
    and OP would'nt have undo tablespace shortage problem.
    (How does small lob flood undo tablespace?)
    2. If the size of lob was big, OP would have 01555 error on user tablespace not undo tablespace shortage error.
    So, i think there are 2 theories that can explain this abnormality.
    1. OP hit the bug of massive undo generation.
    2. OP is using securefile which is 11g new feature.
    Oracle documents says that undo for securefile lob is stored in "undo" tablespace, not user tablespace.
    But unfortunately, i'm not sture about this coz i didn't try it myself

  • ORA-30036: unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'

    Hi,
    A user who is trying to run a report on an EBS system, gets the following error from the application end:
    java.sql.SQLException: ORA-30036: unable to extend segment by 8 in undo tablespace 'APPS_UNDOTS1'
    I would have expected to see this ORA error in the Oracle database alert log as well, however this is not the case.
    I increased the size of the APPS_UNDOTS1 tablespace from 1700mb with autoextend to max 3000mb, however it seems that the tablespace is not extending beyond it's original size of 1700mb. In TOAD, I see that the tablespace has not grown even after the user ran the report again. Any idea why? Is there perhaps something that needs to be adjusted on the application side as well?
    Thanks.

    Hi,
    The tablespace is not extending and this error is not written to the alert log, but I found a trace file with the following information....
    ORA-30036 happens when trying to extend undo segment SYSSMU91258636580$ (usn=9) by 8 blocks
    Reason: Fail to Steal
    Current undo tablespace APPS_UNDOTS1 (tsn=1)
    undo tablespace current size 218240 blks, maxsize 218240 blks, fixed sized
    Undo Retention (reactive): 936, Parameter Undo Retention: 900, Tuned Undo Retention: 936, High threshold Undo Retention: -2
    Retention Guarantee FALSE
    Does anyone know how to solve this "Fail to Steal" problem?
    Btw, the query SELECT DISTINCT STATUS, SUM(BYTES), COUNT(*) FROM DBA_UNDO_EXTENTS GROUP BY STATUS; returns about 55 expired extents, therefore there are still available extents to "steal" from. So why does this fail?

  • ORA-30036: unable to extend segment, our UNDO TABLESPACE grow to 500 GB

    Our client report that when they run their batch job the error "ORA-30036: unable to extend segment..." came into their log file.
    I have checked with alert log but nothing there. We use Oracle 11g on Solaris 10 SPARC.
    Any suggestion ?
    Thanks & Regards

    Refer to
    Troubleshooting ORA-30036 - Unable To Extend Undo Tablespace [ID 460481.1]
    ORA-30036: unable to extend segment by <N> in undo tablespace '<tname>' [ID 271664.1]

Maybe you are looking for