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

    Expected archived log not found, lost of archived log compromises recoverability

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

    Description:
    After deleting some archive logs (in order to make space to do a cold backup) -- as described in KB 16384-35105 --, the cold backup (as seen in the ora_cold_a1_Detail_110217_0015.log) failed:

    RMAN-03002: failure of backup plus archivelog command at 02/17/2011 00:16:47
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /exlibris2/oradata/alephp/arch/arch_alephp_1_735_683110451.dbf
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    <etc.>

    and util f/4, util o/1/4, etc., showed this:

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

    Resolution:
    After deleting the archive log files (as you did yesterday), the files need to be removed from RMAN's list. This required logging into RMAN and doing:

    connect target /
    crosscheck archivelog all;
    delete expired archivelog all;

    This removed the 25 archive log files deleted yesterday from RMAN's catalog. The cold backup was then successful.

    Of course, you should delete archive log files *only* in exceptional circumstances, such as these, and it should be followed by a cold backup to make the archive logs irrelevant.

    • Article last edited: 10/8/2013