Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    ORA-25153: Temporary Tablespace is Empty

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    Here are the error messages along with the names of the log files.

    File: p_manage_02_a_1.log

    File: create_ora_tables_z01_id.log

    aleph_admin@ALEPH0> 04:49:58
    aleph_admin@ALEPH0> old 1: CREATE INDEX
    &&1.Z01_ID ON &1.Z01 (Z01_REC_KEY ASC)
    new 1: CREATE INDEX ABC01.Z01_ID ON ABC01.Z01 (Z01_REC_KEY ASC)
    old 2: STORAGE (INITIAL &2 NEXT &3 MINEXTENTS 1 PCTINCREASE 0)
    new 2: STORAGE (INITIAL 100M NEXT 0K MINEXTENTS 1 PCTINCREASE 0)
    old 5: TABLESPACE &4
    new 5: TABLESPACE TS4X
    CREATE INDEX ABC01.Z01_ID ON ABC01.Z01 (Z01_REC_KEY ASC)
    *
    ERROR at line 1:
    ORA-25153: Temporary Tablespace is Empty

    Same for:

    create_ora_tables_z01_id5.log
    create_ora_tables_z02_id1.log

    Resolution:
    The TEMP tablespace that Oracle is trying to use to sort these internal indexes is missing from this server. You should, checking with util o/14/1, see lines like this :

    Temporary Tablespace Space Usage

    TABLESPACE_NAME SIZE M
    ------------------------------ ----------
    TEMP 749.411664

    On your server, there are none.

    util o/17/4 shows that a tablespace TEMP exists, but util/o/17/2 shows that there are no files for this tablespace.

    I found this at http://www.orafaq.com/node/2 :

    If you remove all tempfiles from a temporary tablespace, you may encounter error: ORA-25153: Temporary Tablespace is Empty. Use the following statement to add a TEMPFILE to a temporary tablespace:

    SQL> ALTER TABLESPACE temp ADD TEMPFILE '/oradata/temp03.dbf' SIZE 100M;

    If util o/17/14 shows that there is no TEMP tablespace, you need to define it. You can use the definition on production as a model if you have any questions.

    Then you can build the missing Oracle indexes via the util a/17/2 utility.

    VERIFICATION FROM CUSTOMER:

    You are right sombody was trying to synch the production and test servers and it looks like there are some files that were not synchronized properly.


    • Article last edited: 10/8/2013
    • Was this article helpful?