Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Unable to extend temp segment by nnn in tablespace TEMP **MASTER RECORD**

    Unable to extend temp segment by nnn in tablespace TEMP **MASTER RECORD**

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description:
    You get the messages below in building an Oracle index at the end of an indexing job, in trying to do util a/17/2 to build the Oracle index, or in some other context.

    Examples:

    CREATE INDEX xxx01.Z0102_ID1 ON xxx01.Z0102 (Z0102_REC_KEY_1 ASC)
    ERROR at line 1:
    ORA-01652: unable to extend temp segment by 6400 in tablespace TEMP


    or

    CREATE UNIQUE INDEX xxx01.Z98_ID ON xxx01.Z98 (Z98_REC_KEY ASC)
    ERROR at line 1:
    ORA-01652: unable to extend temp segment by 64 in tablespace TEMP


    Resolution:
    (It may seem that the TEMP tablespace is pretty much empty, but if you monitor the freespace as the index build is running, you will see that it rapidly becomes exhausted.)

    This message indicates the need to do one of two things:

    1. util o/14/9 ("Clean Temporary Tablespace Free Storage") (This script coalesces the freespace in the TEMP which tends to become highly fragmented.)   [Note:  Jan 23, 2018:  it seems this isn't working.  Instead do "add more files" as described below in #2]  

    or

    2. add more files to the TEMP tablespace (util o/13/3).


    You may want to try #1 first and, if that fails, add the datafiles, as described in #2.

    After doing this, you should be able to use util a/17/2 to build the Oracle index. If util a/17/2 fails because of duplicates, you could try doing util a/17/18.

    Additional Information

    One site kept increasing the size of the TEMP tablespace, and found that only after increasing it to 15 gig did the messages stop.


    • Article last edited: 9/25/2014
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Unable to extend table SYS.AUD$ by 128 in tablespace.SYSTEM
      • Unable to find Global Patron information ***COMPREHENSIVE ANSWER***
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved