ORA-01630: max # extents (505) reached in temp segment in tablespace

I have a problem, in creating a index with error ORA-01630: max # extents (505) reached in temp segment in tablespace.
can you any please help me on this , what could be the best steps can be taken to fix the issue.
I increased the TBS size (I have more than 6 Gb free space), verified the max extents and min extents but didn't get clear idea.
SQL> show user
USER is "APPS"
SQL> create index xyz.xygts_mtl_trx_source_idx on mtl_material_transactions(trx_source_line_id);
create index xyz.xygts_mtl_trx_source_idx on mtl_material_transactions(trx_source_line_id)
ERROR at line 1:
ORA-01630: max # extents (505) reached in temp segment in tablespace
XY_DATA
SQL> select BYTES/1024/1024 from dba_segments where SEGMENT_NAME='MTL_MATERIAL_TRANSACTIONS';
BYTES/1024/1024
10510
-- Verified the pctincrease value
SQL> select TABLESPACE_NAME,INITIAL_EXTENT,NEXT_EXTENT,MAX_EXTENTS,PCT_INCREASE from dba_tablespaces where TABLESPACE_NAME='XYZ_DATA';
TABLESPACE_NAME INITIAL_EXTENT NEXT_EXTENT MAX_EXTENTS
PCT_INCREASE
XYZ_DATA 40960 40960 505
0
Thanks,
Venkat

Pl see
How to Diagnose and Resolve ORA-1628, ORA-1630, ORA-1631, ORA-1632, ORA-1684 : max # of extents <num> reached in < OBJECT > [ID 1025581.6]
Overview Of ORA-01630 Max # Extents(%) reached in temp segment in tablespace % [ID 260944.1]
HTH
Srini

Similar Messages

  • ORA-01630: max # extents (2) reached in temp segment in tablespace USERS

    Hi all,
    I got the error when I created CLUSTER
    ORA-01630: max # extents (2) reached in temp segment in tablespace USERS
    CREATE CLUSTER trial_cluster (trialno NUMBER(5,0))
    PCTUSED 80
    PCTFREE 5
    TABLESPACE users
    STORAGE (INITIAL 250K NEXT 50K
    MINEXTENTS 1 MAXEXTENTS 2
    PCTINCREASE 0)
    HASH IS trialno HASHKEYS 150;
    And I increased maxextents to 20480
    alter tablespace users default storage(MAXEXTENTS 20480)
    same error happens.

    Here is one example from Metalink note:
    create tablespace dropme datafile 'dropme.dbf' size 200m
    extent management dictionary
    default storage (initial 100k next 100k maxextents unlimited pctincrease 0);
    SQL> create index myind on mytab (object_name)
    2 storage ( initial 16k next 16k maxextents 3 pctincrease 0)
    3 tablespace dropme;
    ERROR at line 1:
    ORA-01630: max # extents (3) reached in temp segment in tablespace DROPME

  • ORA-1631: max # extents 505 reached in table APPLSYS.WF_NOTIFICATION_IN

    Platform: RHEL 4u5
    Application: 11.5.10.2
    Database: 10.2.0.4
    2-node Installation as follows:
    1 Node for DB and Concurrent
    1 Node for Apps.
    We anabled OWF Mailer services on 2nd Sept, and on 5th Sep we started receiving following error messages in our DB alert log contnuously:
    ORA-1631: max # extents 505 reached in table APPLSYS.WF_NOTIFICATION_IN
    So, we stopped the OWF Mailer servcies and Agent Listeners.
    Got a metalink note 152475.1 but confused to alter the table definition as I am of the view that these Oracle Workflow related tables are Oracle Built-in Objects not the custom one.
    So, will it be ok to increase the Maxextents for this table?

    911748 wrote:
    Hi Asif,
    We have actually implemented it on Production now. We just tested the mailer configuration on TEST and when users give go ahead after they tested their scenarios we implemented the same on Production. Can I implement the extents increment activity on production?
    Yes you can.
    Thanks,
    Hussein

  • ORA-01631: max # extents (121) reached!!!

    Please review the following DML and error in response of that command:
    insert into dtcn (area_code, cons_code, dcdat) values(12,12,sysdate);
    ERROR at line 1:
    ORA-01631: max # extents (121) reached in table MNBSYS.DTCN
    There are only two such tables DTCN and DTCN_HISTORY in which we are unable to insert any record because of above error. Following are some reference information of these tables:
    PCT_FREE: 10, PCT_USED: 40 INITIAL_EXTENT: 5242880,
    NEXT_EXTENT: 10240, MIN_EXTENTS: 1, MAX_EXTENTS: 121,
    PCT_INCREASE: 0, FREELIST: 1, TABLESPACE_NAME: MNB_DATA,
    DBUSERNAME: MNBSYS
    It may also be noted that the above statistics are exactly same for number of tables but we are facing the problem with only these two tables. Kindly advise what could be the problem and how can I overcome this...
    Thanks in anticipation...
    Zia Shareef

    Hi,
    This error comes when table reach to his max extents,here table extend upto 121 extents that is his max value so now you have to increase the value of maxextents.
    by
    SQL> alter table <table_name> storage(maxextents unlimited);
    **also set the value of nextextent parameter because currently its define by very low value of 10240
    Kuljeet

  • ORA-01631: max # extents (4096)

    Hi
    I received below ORA error for one of my prod table, would like to in which scenario we get the below error and how to investigate why it has occured.
    ORA-01631: max # extents (4096) reached in table DWHSE.F_APS_ORDERS
    Regards

    To hit a maximum extents error on a table you pretty much have to be using dictionary tablespace management. The maximum number of extents defaults based on the block size. If your Oracle version is 8.1 and up all your tablespaces should have been rebuilt as locally managed tablespaces using either auto-allocate or uniform extents. In the case where you have a newer version you should consider creating new tablespaces and moving the objects into them so you can take advantage of modern extent management features.
    If you are running an older release then just take some time to review your object allocation layout to see if for space managment purposes you need to do any re-arranging or storage parameter modification. We used our own version of auto-allocate under 7.x where we had 4 different extent sizes for smaller objects where each size was an even multiple of the smaller sizes. For moderate size and large tables we had uniform extent sizes.
    Good luck.
    HTH -- Mark D Powell --

  • ORA-1631: max # extents  4096

    Hi
    I received below ORA error for one of my prod table, would like to in which scenario we get the below error and how to investigate why it has occured.
    ORA-1631: max # extents 4096 reached in table.......
    Regards

    And what does this database error have in common with Oracle Object and Object Relational concepts, that are the subject matter of this forum?
    Please select the appropriate forum to ask your questions - in this, find the Oracle Database > Database - General forum - and close your thread here.

  • ORA-01693-Max extents reached in lobsegment

    Hi
    getting this error in our alert log file
    ORA-01693-Max extents <> reached in lobsegment <name>
    Can any tell me how to increase (alter) logsegment
    Thanks
    Bhanu

    alter table <table> modify lob (<lobcolumn>) (storage (maxextents unlimited))
    will work

  • MAX EXTENTS have reached

    Hi Team,
    We are getting ora-1632, max extents error's.. suggest ---what all can be done..
    and in future how to avoid it...

    Seems your index extent has reached its max limit, try and see if the issue resolves and always post full error instead of just error no.
    ALTER INDEX <object_owner>.<index_name> STORAGE ( MAXEXTENTS UNLIMITED);
    Edited by: Veeresh.S on Oct 22, 2012 6:53 PM

  • ORA-1631: max # extents reached in table INFILES

    Dear friends
    kindly give me the answer weather I am correct/wrong?
    Solution i have given is
    Alter table <tablename>
    storage(maxextents unlimited)
    Srinivas

    Before changing the table to allow an unlimited number of extents I would 1- verify that the table size is in line with its design usage and 2- that the program in question is not doing something stupid. If both of these are OK, and most of the time they will not be the problem, then you might also consider resizing the object since dictionary space management is in use.
    HTH -- Mark D Powell --

  • Max # extents Error

    When I execute this query in Oracle 8i Database.
    SQL> create table MTL_MATERIAL_TRANSACTIONS_bak as select * from MTL_MATERIAL_TRANSACTIONS;
    create table MTL_MATERIAL_TRANSACTIONS_bak as select * from MTL_MATERIAL_TRANSACTIONS
    ERROR at line 1:
    ORA-01630: max # extents (505) reached in temp segment in tablespace APPLSYSD
    then Shall I use the following command Without shutting down the database. Is there any other solutions.
    Please reply.
    alter tablespace APPLSYSD default storage (maxextents unlimited);
    OR
    alter tablespace APPLSYSD storage (maxextents unlimited);

    Hi user13098327,
    Please read below thread;
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:956629961318

  • System maximum max extents....

    Hi,
    I need a clarification about the System maximum max extents...
    The oracle doc "Error messages" about The error code and message "ORA-01631: max # extents (string) reached in table string.string" points out as action:
    "If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params"
    Which is the system maximum max. extents...??? Is this of database block size???
    Thanks you,
    Sim

    sgalaxy wrote:
    Hi,
    I need a clarification about the System maximum max extents...
    The oracle doc "Error messages" about The error code and message "ORA-01631: max # extents (string) reached in table string.string" points out as action:
    "If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params"
    Which version of Oracle are you on ? I don't think maxextents has been a problem since 9i.
    In the days when "unlimited extents" had not been introduced and the entire extent map had to fit in the segment header the size of a segment map entry dictated the number of extents that could be listed, so the block size made a big difference. The maximum roughly doubled as you doubled the size of the block. From memory - 2KB blocks gave 121 extents, 4KB gave 248, 8KB gave 505 and 16KB gave 1016 - I don't have any memory of a figure for 32KB blocks.
    But from 9i (at least 9.2) Oracle ignores any maxextents setting you put into the table storage clause and uses "unlimited".
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    "For every expert there is an equal and opposite expert"
    Arthur C. Clarke

  • Max # extents exceeded

    Hi,
    I am having problems with the max # extents being exceeded.
    I am creating a spatial index using the following script:
    CREATE INDEX GIS.MYTABLE_SX ON
    GIS.MYTABLE(GEOMETRY)
    indextype is MDSYS.SPATIAL_INDEX
    parameters ( 'SDO_LEVEL=6,
         SDO_NUMTILES = 8,
         SDO_COMMIT_INTERVAL = 1000,
         TABLESPACE = GISI,
         INITIAL = 131072,
         NEXT = 131072,
         PCTINCREASE = 0,
         MINEXTENTS = 1,
         MAXEXTENTS = 2147483645,
         BTREE_INITIAL = 512K,
         BTREE_NEXT = 512K,
         BTREE_PCTINCREASE = 0')
    This in turn creates the table
    MYTABLE_SX_HL6N8$
    and
    the indexes
    MYTABLE_SX_HL6N8$_B1
    (x4 - one for each field SDO_GROUPCODE, SDO_CODE, SDO_STATUS, SDO_ROWID)
    and
    MYTABLE_SX_HL6N8$_B2
    (x1 one for SDO_ROWID)
    using the following script:
    DROP TABLE MYTABLE_SX_HL6N8$ CASCADE CONSTRAINTS ;
    CREATE TABLE MYTABLE_SX_HL6N8$ (
    SDO_GROUPCODE RAW (14),
    SDO_ROWID ROWID,
    SDO_CODE RAW (14),
    SDO_STATUS VARCHAR2 (1))
    TABLESPACE GISI
    PCTFREE 10
    PCTUSED 40
    INITRANS 1
    MAXTRANS 255
    STORAGE (
    INITIAL 131072
    NEXT 131072
    PCTINCREASE 0
    MINEXTENTS 1
    MAXEXTENTS 2147483645
    FREELISTS 1 FREELIST GROUPS 1 )
    NOCACHE;
    CREATE INDEX MYTABLE_SX_HL6N8$_B1 ON
    "GIS".MYTABLE_SX_HL6N8$(SDO_GROUPCODE, SDO_CODE, SDO_ROWID, SDO_STATUS)
    TABLESPACE GISI PCTFREE 10 STORAGE(INITIAL 524288 NEXT 524288 PCTINCREASE 0 )
    CREATE INDEX MYTABLE_SX_HL6N8$_B2 ON
    "GIS".MYTABLE_SX_HL6N8$(SDO_ROWID)
    TABLESPACE GISI PCTFREE 10 STORAGE(INITIAL 524288 NEXT 524288 PCTINCREASE 0 )
    The problem is when you create a spatial index using the top script the max # extents do not get applied to
    MYTABLE_SX_HL6N8$_B1
    and
    MYTABLE_SX_HL6N8$_B2
    Instead these tables take on the default max # extents set on the tablespace.
    How do I set the max # extents for indexes
    MYTABLE_SX_HL6N8$_B1
    and
    MYTABLE_SX_HL6N8$_B2
    to MAXEXTENTS 2147483645 for example. I am aware that this is not good practice but I would like to know if it is possible. Is it a spatial issue? I have tried to increase the size of
    the BTREE_INITIAL and BTREE_NEXT to 512K from 128K but it still complains about max # extents (999) reached. A way round it is obviously to increase the default max # extents on the tablespace but that requires DBA intervention. I would like to know how one can do this programatically using the top script or something similar.
    Thanks
    Regards
    Stephen

    Hi Stephen,
    A few thoughts:
    Oracle has pretty much dropped hybrid indexing in terms of it being
    a generically useful way to index data. As of 9.0.1.2 the suggestion
    is to use R-tree indexes unless there is something about your
    workload or data set that makes the use of R-trees bad.
    If you don't use R-tree indexing, then stick with fixed indexing. The
    original idea of hybrid indexing was to allow better approximations
    of geometries without the index growing too large, but it turns out the
    SQL index query within spatial took longer than anticipated.
    In terms of setting up the spatial index, when creating a quadtree index
    you can specify the btree_initial and btree_next in the parameters clause
    of the create index statement, which allows you to adjust the btree indexing
    parameters as you noted, but there is no way to set the max number of
    extents (or in fact the tablespace used for the b-tree indexes).
    When you need that control, you need to to have dba intervention to set the
    default tablespace and parameters at the user level before creating the spatial
    index. The parameters in the parameters clause can set up the index table
    parameters, and the default parameters can be used for the btree indexes.
    regards,
    dan

  • Temp segment

    Why am i getting this error in a select statement which does not even use a temporary table of any kind?
    unable to extend temp segment in tablespace TEMP

    I find that the following sql tells me what is being sorted and what is being copied to the datafiles. I can use is and see if a sort is being done in memory because it will not generate a temp segment on disk:
    set pages 50
    set heading on
    set wrap off
    column username format a15
    column tablespace format a10
    column user format a10
    column meg format a7
    column sid format 999999
    set lines 90
    set feedback on
    select s.sid,s.username, u."USER", u.tablespace, u.contents, u.extents, u.blocks
    from sys.v_$session s, sys.v_$sort_usage u
    where s.saddr = u.session_addr;
    select s.osuser, s.sid, s.username, s.serial#,
    sum(u.blocks)*vp.value/1024/1024 sort_size_IN_MEG
    from sys.v_$session s, sys.v_$sort_usage u, sys.v_$parameter vp
    where s.saddr = u.session_addr
    and vp.name = 'db_block_size'
    and s.osuser like '%'
    group by s.osuser, s.sid, s.username, s.serial#, vp.value
    order by sort_size_in_meg;
    select to_char(round(sum(bytes)/1024/1024)) meg,
    sum(extents),tablespace_name,segment_type,owner||'.'||segment_name
    from dba_segments where segment_type='TEMPORARY'
    group by tablespace_name,segment_type,owner||'.'||segment_name
    having round(sum(bytes)/1024/1024)>0
    order by round(sum(bytes)/1024/1024);
    column osuser format a15
    I usually set the sort big to do some maintenance with:
    -- Check the available memory on the OS with top.
    -- If you go overboard on the memory allocation, sar –g will show paging
    -- I usually set the sort_area_size some where between 200 and 900 meg to speed up index rebuilds
    alter session set workarea_size_policy='MANUAL';
    alter session set sort_area_size=900000000;
    alter session set sort_area_retained_size=900000000;
    Good luck

  • 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

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

Maybe you are looking for