3 Replies Latest reply: Feb 13, 2008 9:34 AM by 26741 RSS

    RMAN Recovery Error

    user59655
      Hello -

      I am getting the following error (can't find block change tracking file) during an RMAN recovery:

      RMAN> recover database;

      Starting recover at 19-SEP-07
      using target database control file instead of recovery catalog
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: sid=544 devtype=DISK

      starting media recovery

      archive log thread 1 sequence 55420 is already on disk as file /archives/phdv4/arch_1_55420_605730252.arc
      archive log filename=/archives/phdv4/arch_1_55420_605730252.arc thread=1 sequence=55420
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of recover command at 09/19/2007 10:19:08
      ORA-00283: recovery session canceled due to errors
      RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/phdv4/arch_1_55420_605730252.arc'
      ORA-00283: recovery session canceled due to errors
      ORA-19755: could not open change tracking file
      ORA-19750: change tracking file: '/u02/oracle/oradata/phdv4/bct.dbf'
      ORA-27037: unable to obtain file status
      SVR4 Error: 2: No such file or directory
      Additional information: 3

      Is the bct file not backed up automatically by RMAN?
        • 1. Re: RMAN Recovery Error
          P.Forstmann
          It is not backed up according to section 4.4.4 of Backup and Recovery Basics:

          Although RMAN does not support backup and recovery of the change-tracking file itself, if the whole database or a subset needs to be restored and recovered, then recovery has no user-visible effect on change tracking. After the restore and recovery, the change tracking file is cleared, and starts recording block changes again. The next incremental backup after any recovery is able to use change-tracking data.

          According to Metalink note:
          Subject: Ora-19755: Could Not Open Change Tracking File Ora--17503 on Database Open
          Doc ID: Note:344885.1 Type: PROBLEM
          Last Revision Date: 21-DEC-2005 Status: PUBLISHED

          you could disable block change tracking before running recover statement and reenabled it after successfull recovery.

          Message was edited by:
          Pierre Forstmann
          • 2. Re: RMAN Recovery Error
            622979
            But how do I disable block change tracking without opening the database? I don't seem to be able to issue 'alter database disable....'

            ALTER DATABASE DISABLE BLOCK CHANGE TRACKING;

            RMAN-00571: ===========================================================
            RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
            RMAN-00571: ===========================================================
            RMAN-00558: error encountered while parsing input commands
            RMAN-01005: syntax error: found "identifier": expecting one of: "mount, open"
            RMAN-01008: the bad identifier was: DISABLE
            RMAN-01007: at line 1 column 16 file: standard input

            Linda
            • 3. Re: RMAN Recovery Error
              26741
              BCT can be disabled with the database in a MOUNT state.

              ALTER DATABASE MOUNT

              ALTER DATABASE DISABLE BLOCK CHANGE TRACKING