ORA-1630: max # extents 75 reached in temp segment for tablespace INVX
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: ORA-1630: max # extents 75 reached in temp segment for tablespace INVX

  1. #1
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865
    The error is

    ORA-1630: max # extents 75 reached in temp segment for tablespace INVX


    Cause: The maximum amount of space allowed for saving undo entries has been reached for a temporary segment in the named tablespace, or space could not be
    allocated in the data dictionary to contain the definition of the object.

    How do I rectify this?

    Thanks.

    With regards.




  2. #2
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    increase maxextents for your tablespace :
    alter tablespace INVX default storage (maxextents 100);

  3. #3
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865

    Max extents ?

    I have quite a lot of MAX_EXTENTS

    TST > select max_extents from dba_tablespaces where TABLESPACE_NAME LIKE 'INVX';

    MAX_EXTENTS
    -----------
    2147483645

    1 row selected.

    So, what is the problem?

    Thanks.



  4. #4
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    what is the value of the contents column from dba_tablespaces ?? your tablespace should be in temporary mode, else just look at the maxextents of the segment which can not extend

  5. #5
    Join Date
    Apr 2001
    Posts
    46
    Check the pctincrease, and raise the pctincrease for the tablespace


  6. #6
    Join Date
    Feb 2001
    Location
    Bombay,India
    Posts
    530
    Hi,
    There are 2 options for resolving this problem.

    Solution 1: Shutdown the database with normal,immediate
    option so that all the temporary segments will be
    released.

    Solution 2: Add a datafile to the temporary tablespace.

    In case of any help please be free to ask me at rohitsn@altavista.com

    Regards,
    Rohit Nirkhe,Oracle DBA,OCP 8i
    rohitsn@altavista.com

  7. #7
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    you do not need to shutdown the databse to free temp tablespace !!!
    and adding a datafile will not be useful since this one is not full, message if that maxextents has been reached, not that segment cannot allocate n bytes in file ... so tablespace should not be full, but the segment just cannot grow

  8. #8
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865

    info

    Thanks for the replies.

    The info requested is as follows...


    TST > select max_extents, contents, pct_increase from dba_tablespaces where TABLESPACE_NAME LIKE 'INVX'

    MAX_EXTENTS CONTENTS PCT_INCREASE
    ----------- --------- ------------
    2147483645 PERMANENT 50

    1 row selected.

    Regards.


  9. #9
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    Originally posted by yotot
    Check the pctincrease, and raise the pctincrease for the tablespace

    Absolutely NOT! Always set pctincrease 0, specially temporary tablespaces

  10. #10
    Join Date
    Apr 2001
    Posts
    108
    What's the size of the tablespace, and what is the size of the initial and next extent for the tablespace. Could these values be large enough that you quickly run out of space?

    ie; With a 1 Gbyte temp tablespace and initial and next extents set at 20 Mbytes and pctincrease of 50, you would run out of space in the tablespace after your ninth extent was created. And your tenth extent would want apprix 512 Mbytes of contigous space. So you can see the dangers of the pctincrease setting.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width