ORA-1691: unable to extend lobsegment APPLSYS.SYS_LOB0000070652C00004$$ by

hi gurus,
i got this error when trying to export large data.
need help ...
tqvmch

Hi,
Please post the application release, database version and the OS.
How do you get this error?
Try the steps in (Note: 378377.1 - Ora-1691: Unable To Extend Lobsegment Applsys.Sys_lob0000033489c00004$$ By 92170) and see if it helps.
Thanks,
Hussein

Similar Messages

  • ORA-1691: unable to extend lobsegment SAPR3.SYS_LOB0000233227C00014$$

    Hi gurus,
    We had been updated the Oracle Database 10g to Oracle Database 11g on Aix box using SAP Application tools for this.
    We got successful on the update process.
    Now when we check the alert.log file, we noticed the error:
    ORA-1691: unable to extend lobsegment SAPR3.SYS_LOB0000233227C00014$$ by 128 in tablespace PSAPEL700D
    At the transaction DB13:
    BR0100W Internal error for 'lob_segment: SAPR3.GVD_DATAFILE.SYS_LOB0000274858C00028$$' at location BrSegListGet-25
    BR0100W Internal error for 'lob_segment: SAPR3.GVD_DATAFILE.SYS_LOB0000274858C00031$$' at location BrSegListGet-25
    We already extended the PSAPEL700D tablespace, but didn't work.
    May i use your support?
    Thanks,
    Denis

    Hello Keilor,
    Thanks for your reply.
    I checked this points about this tablespace:
    Size (MB) 31.251,00
    Free (MB) 15.631,31
    Block size (KB) 8
    Initial extent (MB) 0,063
    Next extent (MB) 0,000
    Min. extents 1
    Max. extents 2.147.483.645
    DATAFILE                                                              SIZE     AUTOEXTEND     MAXSIZE
    /oracle/TSA/sapdata1/el700d_6/el700d.data6     5.000,00     YES     5.500,00
    /oracle/TSA/sapdata1/el700d_7/el700d.data7      1.000,00     YES     1.500,00
    /oracle/TSA/sapdata1/el700d_8/el700d.data8      1.000,00     YES     1.500,00
    /oracle/TSA/sapdata1/el700d_9/el700d.data9     5.000,00     YES     5.500,00
    /oracle/TSA/sapdata4/el700d_10/el700d.data10     4.000,00     YES     4.500,00
    /oracle/TSA/sapdata4/el700d_11/el700d.data11     7.000,00     YES     7.500,00
    /oracle/TSA/sapdata5/el700d_1/el700d.data1      203     YES     500
    /oracle/TSA/sapdata5/el700d_2/el700d.data2 1.024,00     YES     1.500,00
    /oracle/TSA/sapdata5/el700d_3/el700d.data3     1.024,00     YES     1.500,00
    /oracle/TSA/sapdata5/el700d_4/el700d.data4     3.000,00     YES     3.500,00
    /oracle/TSA/sapdata5/el700d_5/el700d.data5     3.000,00     YES     3.500,00
    Thanks again.
    Denis

  • ORA-1653: unable to extend table APPLSYS.FND_LOG_MESSAGES by 128 in

    ORA-1653: unable to extend table APPLSYS.FND_LOG_MESSAGES by 128 in tablespace FND_TAB
    as this getting in alert log.........

    Hi,
    Please implement the solutions outlined in the following document.
    Note: 743785.1 - How I resolved ORA-1653 on APPS_TS_TX_DATA tablespace
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=743785.1
    Regards,
    Hussein

  • ORA-1653: unable to extend table APPLSYS.FND_ENV_CONTEXT by 16

    Database version : 10.2.0.2
    When a Query is executed from an Oracle Application Self Service Page , we are hitting the following exception from JDBC
    ## Detail 0 ##
    java.sql.SQLException: ORA-21710: argument is expecting a valid memory address of an object
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
         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:745)
         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:966)
         at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1062)
    When checking the alert.log we are getting different error
    ORA-1653: unable to extend table APPLSYS.FND_ENV_CONTEXT by 16
    The above error was not coming till June 1st. we are initially getting error
    ORA-00604: error occurred at recursive SQL level 1
    ORA-04031: unable to allocate 32 bytes of shared memory ("shared
    pool","select count(*) from sys.job...","sql area","tmp")
    Kindly advise whether this is known issue or a bug. Any Pointers to known issues of specific DBMS Versions.
    Thanks
    Joseph

    Find the tablespace where APPLSYS.FND_ENV_CONTEXT and see if you can add space to it.

  • Error: ORA-01654: unable to extend index APPLSYS.SYS_IOT_TOP_34179 by 16 in

    Hi,
    I am using Oracle API (HzLocationV2Pub.LocationRec) to update record and getting the following error message in JDeveloper log and couldn't able to update.
    x_return_status : U
    x_msg_data : Unexpected SQL error encountered during synchronization:
    Procedure: sync_party_site
    Error: ORA-01654: unable to extend index APPLSYS.SYS_IOT_TOP_34179 by 16 in tablespace APPS_TS_QUEUES
    Please contact the system administrator.
    x_msg_count : 1
    What is the reason behind this error?
    How to resolve this?
    Thanks & Regards,
    Sagarika

    Hi,
    You need to add more space to your datafile/tablespace, or extend the index.
    SQL> alter index APPLSYS.SYS_IOT_TOP_34179 storage (maxextents unlimited);
    SQL> ALTER TABLESPACE <tablespace name> ADD DATAFILE '<full path and file name>' SIZE <integer> <K|M>; Note: 1025288.6 - How to Diagnose and Resolve UNABLE TO EXTEND Errors
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=1025288.6
    Note: 19049.1 - OERR: ORA 1654 unable to extend index by for tablespace
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=19049.1
    Note: 762273.1 - ORA-1654: unable to extend index
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=762273.1
    Regards,
    Hussein

  • ORA-1653: unable to extend table

    hi guys!
    its the second time am posting this message! had this error in this alert.log
    ORA-1653: unable to extend table APPLSYS.WF_LOCAL_ROLES_STAGE by 4849950 in tablespace APPLSYSD
    the tablespace is APPLSYSD free_space 59390.4688M used_space 22495.7031M
    initial extent 40960, next_extent 1048576, max_extent 2147483645 and pct_free is set to 0!
    the tablespace contains three datafiles and their percentage used is 36%, 35% and 12%. I dont really understand how this error comes! how come in the error, it wants to extend by 4849950 while the value for next_extent is 1048576? could some one please help me overcome this problem??
    Thanls

    hi.
    here are the output to some queries.
    select initial_extent,next_extent, pct_increase from dba_tablespaces where tablespace_name='APPLSYSD'
    INITIAL_EXTENT NEXT_EXTENT PCT_INCREASE
    40960 40960 0
    select initial_extent, next_extent, pct_free, pct_increase from dba_tables where owner='APPLSYS' and table_name=('WF_LOCAL_ROLES_STAGE')
    INITIAL_EXTENT NEXT_EXTENT PCT_FREE PCT_INCREASE
    40960 1048576 10 0
    select table_name,NEXT_EXTENT,PCT_INCREASE from dba_tables where owner='APPLSYS' and table_name='WF_LOCAL_ROLES_STAGE';
    TABLE_NAME NEXT_EXTENT PCT_INCREASE
    WF_LOCAL_ROLES_STAGE 1048576 0
    select OWNER,SEGMENT_NAME,NEXT_EXTENT,PCT_INCREASE,EXTENTS from dba_segments where owner='APPLSYS' and segment_name='WF_LOCAL_ROLES_STAGE';
    OWNER SEGMENT_NAME NEXT_EXTENT PCT_INCREASE EXTENTS
    APPLSYS WF_LOCAL_ROLES_STAGE 1048576 0 1

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

    Dear all,
    received this error when generate a report.
    check the TEMP1 and TEMP2 they all have lot of spaces.
    check the env $APPLLCSP return empty.
    Please advise how to correct this error.
    Regards,
    Payables: Version : 12.0.0
    APXSSIMP module: Supplier Sites Open Interface Import
    APPLLCSP Environment Variable set to :
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.UTF8
    Enter Password:
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-300: MSG-00001: After SRWINIT
    MSG-00002: After Get_Company_Name
    MSG-00003: After Get_NLS_Strings
    MSG-00004: After Importing Suppliers
    MSG-00005: After Get_Header_Information
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
    ==> SELECT assi.org_id C_Rejected_Org_Id,
    MSG-00020: After SRWEXIT
    Report Builder: Release 10.1.2.0.2 - Production on Mon May 11 09:55:36 2009

    >
    check the TEMP1 and TEMP2 they all have lot of spaces.
    >
    How much is "lot" ? :-) How did you determine this "lot" ?
    Pl see MOS Doc 1025288.6 (How to Diagnose and Resolve UNABLE TO EXTEND Errors)
    HTH
    Srini

  • ORA-01653:enable to extend table APPLSYS.FND_LOGIN by 128

    Hi,
    I am facing the below error while running the concurrent program:
    ORA-01653:enable to extend table APPLSYS.FND_LOGIN by 128 in Tablespace FND_TAB.
    Could you please suggest me something on this.
    Thanks

    Logging into and working in EBS causes audit data to be inserted into various FND tables, one of them being FND_LOGIN. It is a best practice to run the "Purge Signon Audit Data" concurrent program regularly, based on your needs and requirements as to how long login audit data needs to be retained at your site. This program runs the script $FND_TOP/sql/FNDSCPRG.sql. This will delete data form FND_LOGIN (and other) tables and keeps them from growing too big.
    HTH
    Srini

  • ORA-1653: unable to extend table - but enough space for datafile

    We encountered this problem in one of our database Oracle Database 10g Release 10.2.0.4.0
    We have all datafiles in all tablespaces specified with MAXSIZE and AUTOEXTEND ON. But last week database could not extend table size
    Wed Dec  8 18:25:04 2013
    ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
    ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
    Wed Dec  8 18:25:04 2013
    ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
    ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
    Wed Dec  8 18:25:04 2013
    ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
    ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
    Datafile was created as ... DATAFILE '/u01/oradata/PCSDB/PCS_DATA01.DBF' AUTOEXTEND ON  NEXT 50M MAXSIZE 31744M
    Datafile PCS_DATA01.DBF had only 1GB size. Maximum size is 31GB but database did not want to extend this datafile.
    We used temporary solution and we added new datafile to same tablespace. After that database and our application started to work correctly.
    There is enough free space for database datafiles.
    Do you have some ideas where could be our problem and what should we check?
    Thanks

    ShivendraNarainNirala wrote:
    Hi ,
    Here i am sharing one example.
    SQL> select owner,table_name,blocks,num_rows,avg_row_len,round(((blocks*8/1024)),2)||'MB' "TOTAL_SIZE",
      2   round((num_rows*avg_row_len/1024/1024),2)||'Mb' "ACTUAL_SIZE",
      3   round(((blocks*8/1024)-(num_rows*avg_row_len/1024/1024)),2) ||'MB' "FRAGMENTED_SPACE"
      4   from dba_tables where owner in('DWH_SCHEMA1','RM_SCHEMA_DDB','RM_SCHEMA') and round(((blocks*8/1024)-(num_rows*avg_row_len/1024/1024)),2) > 10 ORDER BY FRAGMENTED_SPACE;
    OWNER           TABLE_NAME                        BLOCKS   NUM_ROWS AVG_ROW_LEN TOTAL_SIZE           ACTUAL_SIZE          FRAGMENTED_SPACE
    DWH_SCHEMA1     FP_DATA_WLS                        14950     168507          25 116.8MB              4.02Mb               112.78MB
    SQL> select tablespace_name from dba_segments where segment_name='FP_DATA_WLS' and owner='DWH_SCHEMA1';
    TABLESPACE_NAME
    DWH_TX_DWH_DATA
    SELECT /* + RULE */  df.tablespace_name "Tablespace",
           df.bytes / (1024 * 1024) "Size (MB)",
           SUM(fs.bytes) / (1024 * 1024) "Free (MB)",
           Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",
           Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used"
      FROM dba_free_space fs,
           (SELECT tablespace_name,SUM(bytes) bytes
              FROM dba_data_files
             GROUP BY tablespace_name) df
    WHERE fs.tablespace_name   = df.tablespace_name
    GROUP BY df.tablespace_name,df.bytes
    UNION ALL
    SELECT /* + RULE */ df.tablespace_name tspace,
           fs.bytes / (1024 * 1024),
           SUM(df.bytes_free) / (1024 * 1024),
           Nvl(Round((SUM(fs.bytes) - df.bytes_used) * 100 / fs.bytes), 1),
           Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes)
      FROM dba_temp_files fs,
           (SELECT tablespace_name,bytes_free,bytes_used
              FROM v$temp_space_header
             GROUP BY tablespace_name,bytes_free,bytes_used) df
    WHERE fs.tablespace_name   = df.tablespace_name
    GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_used
    ORDER BY 4 DESC;
    set lines 1000
    col FILE_NAME format a60
    SELECT SUBSTR (df.NAME, 1, 60) file_name, df.bytes / 1024 / 1024 allocated_mb,
    ((df.bytes / 1024 / 1024) - NVL (SUM (dfs.bytes) / 1024 / 1024, 0))
    used_mb,
    NVL (SUM (dfs.bytes) / 1024 / 1024, 0) free_space_mb
    FROM v$datafile df, dba_free_space dfs
    WHERE df.file# = dfs.file_id(+)
    GROUP BY dfs.file_id, df.NAME, df.file#, df.bytes
    ORDER BY file_name;
    Tablespace                      Size (MB)  Free (MB)     % Free     % Used
    DWH_TX_DWH_DATA                     11456       8298         72         28
    FILE_NAME                                                    ALLOCATED_MB    USED_MB FREE_SPACE_MB
    /data1/FPDIAV1B/dwh_tx_dwh_data1.dbf                                 1216       1216             0
    /data1/FPDIAV1B/dwh_tx_dwh_data2.dbf                                10240       1942          8298
    SQL> alter database datafile '/data1/FPDIAV1B/dwh_tx_dwh_data2.dbf' resize 5G;
    alter database datafile '/data1/FPDIAV1B/dwh_tx_dwh_data2.dbf' resize 5G
    ERROR at line 1:
    ORA-03297: file contains used data beyond requested RESIZE value
    Although , we did moved the tables into another TB , but it doesn't resolve the problem unless we take export and drop the tablespace aand again import it .We also used space adviser but in vain .
    As far as metrics and measurement is concerned , as per my experience its based on blocks which is sparse in nature related to HWM in the tablespace.
    when it comes to partitions , just to remove fragmentation by moving their partitions doesn't help  .
    Apart from that much has been written about it by Oracle Guru like you .
    warm regards
    Shivendra Narain Nirala
    how does free space differ from fragmented space?
    is all free space considered by you to be fragmented?
    "num_rows*avg_row_len" provides useful result only if statistics are current & accurate.

  • Oracle Alert - ORA-1652 Unable to extend the Temp Segment

    Hi Team,
    During our DB Reorg we have received the Oracle Alert - ORA-1652 Unable to extend the Temp Segment by 15485 in tablespace :PSAPBTABI.
    Our DBReorg got cancelled..
    We would like to know how we can resolve the above error so that we can reschedule the DB Reorg activity..
    Regds,
    Satyanarayana N

    Hi,
    If you are using UNIX OS, the temp files are created as sparse file due to the OS functionality.
    Altough you have assigned 49 GB the actual size will be very very less.
    You can check the actula file size with du or df command. To remove these sparse condition you will need to perform certain steps.
    Read this note and execute the steps given and then see the file size difference.
    548221 - Temporary Files are created as sparse files
    Do update the message if the OS is different.
    Regards,
    Nilesh

  • ORA-1653: unable to extend table PERFSTAT.STATS

    Hi there,
    I know it's Friday and by the end of the week we normally are not that alert anymore.
    However now we have a very puzzling problem, one that leaves two DBA's very amazed.
    This morning our alert-log of a 9.2.0.8 database on AIX 5.3 showed:
    ORA-1653: unable to extend table PERFSTAT.STATS in tablespace TOOLSEasy, one would say. Extend the tablespace and you're done.
    However the tablespace is on autoextend, not even mentioned that it has 2.5Gb of free space.
    It is also "Locally Managed", with uniform extent size of 16Kb and manual "segment space management"
    The index of this table is in the same tablespace.
    The storage parameters are set to "unlimited" possibilities.
    A manual
    exec statspack.snapresults in the same error where as a
    create table statstest as select * from stats$sqltext ; works fine. The mentioned source table here is the one which seems unable to extend due to the "tablespace restrictions"
    Some storage parameters:
    CREATE TABLE "PERFSTAT"."STATS$SQLTEXT" (
    "HASH_VALUE" NUMBER NOT NULL ENABLE,
    "TEXT_SUBSET" VARCHAR2 (31) NOT NULL ENABLE,
    "PIECE" NUMBER NOT NULL ENABLE,
    "SQL_TEXT" VARCHAR2 (64),
    "ADDRESS" RAW (8),
    "COMMAND_TYPE" NUMBER,
    "LAST_SNAP_ID" NUMBER,
    CONSTRAINT "STATS$SQLTEXT_PK" PRIMARY KEY
    ("HASH_VALUE", "TEXT_SUBSET", "PIECE
    USING INDEX
    PCTFREE 10 INITRANS 2 MAXTRANS 255
    STORAGE
    INITIAL 1048576
    NEXT 1048576
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    PCTINCREASE 0
    FREELISTS 1
    FREELIST GROUPS 1
    BUFFER_POOL DEFAULT
    ) TABLESPACE "TOOLS"
    ENABLE
    PCTFREE 5
    PCTUSED 40
    INITRANS 1
    MAXTRANS 255
    NOCOMPRESS
    LOGGING
    STORAGE (INITIAL 5242880
    NEXT 5242880
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    PCTINCREASE 0
    FREELISTS 1
    FREELIST GROUPS 1
    BUFFER_POOL DEFAULT)
    TABLESPACE "TOOLS"Can this be some kind of Data Dictionairy corruption ??

    virendra.k wrote:
    The next extent clause in creation script says that it is required to have at least 1G of contiguous memory. But the satement fails which means that a chunk of this size cannot be allocated. The situation may arise due to fragmentation of tablespace. See metalink doc id [1020182.6|https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9000433346754441541::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,1020182.6,1,0,1,helvetica] if the largest free chunk >= 1G. Other wise increase the size of tablespace. It may help you.
    I don't understand the result of 1G you calculated.
    I only see: NEXT 1048576 of the primary key, which is 1M and NEXT 5242880 ( 5M) of the table itself.
    However it the Note lead me to the solution.
    The largest piece of contiguous free space in the tablespace is, according to this Note:
    TABLESPACE NAME CONTIGUOUS BYTES
    TOOLS                                 3,407,872 ==> 3Mb
    TOOLS 3,407,872
    TOOLS 3,407,872
    TOOLS 3,301,376
    TOOLS 3,194,880
    TOOLS 3,194,880
    TOOLS 3,194,880
    TOOLS 3,194,880
    TOOLS 3,088,384
    So I executed the following:
    SQL> alter table stats$sqltext storage (next 1m);And subsequently:
    SQL> exec statspack.snap;Which now succeeds !!
    Conclusion: Tablespace REORG needs to be planned.
    One more strange thing however:
    I altered the NEXT_EXTENT size back to 5M, and again the statspack.snap now works OK.
    It must be the either a background COALESCE that solved the problem, or the (maybe existing) corruption in the dictionary is now fixed/gone
    Thanks for the assistance

  • 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-1688: UNABLE TO EXTEND TABLE IN SYSAUX TABLESPACE

    Hi,
    We are running oracle10g R-2 (10.2.0.2.0) on solaris 10.
    In our alert log file we get following message interminantely:-
    ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition
    WRH$_
    ACTIVE_455891297_399 by 128 in tablespace SYSAUX
    MMON Flush encountered SYSAUX out of space error(1688).
    MMON (emergency) purge of WR snapshots (243) and older
    The above error reproduce after every 1 hour.
    Thanks & Regards
    Rishikesh

    It seems your tablespace SYSAUX to be little: you need to make it bigger or add another datafile. Using "Oracle Enterprise Manager" is quite easy to do, in section "Storage Manager".

Maybe you are looking for

  • Some iTunes vids in library not showing on new iPad

    Im pretty sure the reason some of my music is missing is that I didn't buy it from iTunes, but rather copied it to my library from CDs (is that right?) But these are music videoes that I bought from iTunes. And, other iTunes vids did show up and offe

  • ODI - IKM SQL to File Append - Header not Generated

    I'm using ODI IKM SQL to File Append to create a text file, but the header is not being generated. And the GENERATE_HEADER is set to Yes. The file is Tab delimited and the Heading (number of lines) is set to 1. Seems to only be an issue with HFM file

  • User "not responding" when trying to audio and video chat

    Hello everyone, I know there have been many posts here about this topic - to be honest I've tried everything and thought starting a clean thread might be the way forward. Basically when I try and do a video (or audio) chat with Australia (or my dad u

  • Upgrade from OS X 10.6.8 to Mountain Lion

    Hi, my MacBook has the following specs:  2 GHx Intel Core 2 Duo, with 2 GB 667 MHz DDR2 SDRAM, with about 200 GB of available space on my hard drive, running Snow Leopard 10.6.8.  I tried to purchase and download Mountain Lion and got a message stati

  • XI in an insurance company

    Hi, If XI is being implemented in an insurance company. Could any one guide me with the correct implementation steps, in the context of an insurance company. Thanks, -Naveen.