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

    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 16.02

    Description:
    I went to run a words index rebuild last week and somehow or another it locked up the linux server. I came in the next morning and the server had trouble booting up but now runs, but now when I start the Oracle database it seems I have some data corruption.

    The alert_aleph0.log has a bunch of block errors in data file 25.

    Trying to start oracle (util o/1/1) we get:

    SQL> SQL> ORACLE instance started.

    Total System Global Area 355537712 bytes
    Fixed Size 451376 bytes
    Variable Size 184549376 bytes
    Database Buffers 167772160 bytes
    Redo Buffers 2764800 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

    And util o/1/3 then shows oracle processes running.

    But when we do util f/4 to look at doc records, we get:

    Oracle error: handle_connection
    ORA-01033: ORACLE initialization or shutdown in progress

    Load: /exlibris/aleph/u16_1/alephe/tab/tab_io_remote
    Error: io_z00 - table doesn't exist in database or tab_io_remote for library: ABC01

    Resolution:
    Analysis by Ex Libris staff concluded that this Cataloging server's Oracle was not recoverable. (The site did not have Archiving turned on and there were no archive logs to use for recovery.)

    The site had a separate OPAC server to which they periodically copied tables. The tables were successfully copied back from that server to the Cataloging server.

    • Article last edited: 10/8/2013