The SAP for Oracle RMAN Restore Job Fails During the Log Restore Phase

Article ID: 85179

Article Type: Troubleshooting

Last Modified:

In the first attempt, the SAP for Oracle RMAN restore job successfully restores the control file, data files, and logs. However, during the second attempt, the RMAN restore job fails specifically during the log restore phase.

Symptoms

The Oracle RMAN restore job fails with the following script and error details: brrestore Script: [brrestore -d rman_util -a 6-9 -c force -p C:\tmp\initASJ.sap_restore -u // ] brrestore error message: RMAN-20242: specification does not match any archived log in the repository



Resolution

You need to verify the following:

1. If the flash recovery area is enabled, disable it by running the following commands:     Show parameter db_recovery_file     Select * from V$RECOVERY_FILE_DEST;

    NAME

     --------------------------------------------------------------------------------

    SPACE_LIMIT SPACE_USED SPACE_RECLAIMABLE NUMBER_OF_FILES     CON_ID

    ----------- ---------- ----------------- --------------- ------------------------

   E:\oracle\ASJ\oraflash

   3.1457E+10 2773876736        2752937984               7          0

2. Disable the Flash Recovery Area (FRA). To disable FRA, do the following: 

    - Set the DB_RECOVERY_FILE_DEST initialization parameter to a null string.

      SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = '' scope=both;

3. Kill the pending job since the data is already restored. 

4. Submit new restore with control file and log restore selection only.

5. Recover database.

Note: If required, enable flash recovery area after successful restore and recovery

           SQL> ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = 'E:\oracle\ASJ\oraflash' scope=both;

1 Commvault Way, Tinton Falls, NJ 07724 Sitemap | Legal Notices | Trademarks | Privacy Policy
Copyright © Commvault | All Rights Reserved.