Oracle full backup fails with RMAN script error [18:106] after restore

Last post 01-23-2020, 2:56 AM by chelydridae. 2 replies.
Sort Posts: Previous Next
  • Oracle full backup fails with RMAN script error [18:106] after restore
    Posted: 01-22-2020, 3:01 AM

    Hello all,

    we did a full database restore of an Oracle instance, but since then the full backups fail with RMAN script error [18:106] : RMAN Script execution failed with error [ORA-19625: error identifying file /u01/oracle/oradata/TEST/arch/arc_dupl_1_710_1002728610.arc]

    The restore was carried out by leaving all the options untouched at standard selection, that is:

    - selected all tablespaces from the instance
    - restore in-place
    - Restore Options
    -- Restore Control File
    -- Restore Data
    -- No Catalog
    -- Recover
    - Advanced-tab -> Options
    -- Open DB
    -- Reset Logs: yes
    -- Disable Oracle Channel Restore Failover

    Hence I have no Oracle knowledge and the Oracle admin on the other hand does not know Commvault we are in a kind of deadlock ...

    Any hint about what we missed in the configuration of our restore test or how we get Oracle back to normal condition is appreciated.

    thx and regards

  • Re: Oracle full backup fails with RMAN script error [18:106] after restore
    Posted: 01-22-2020, 10:58 AM
    • efg is not online. Last active: 02-26-2020, 2:57 PM efg
    • Top 10 Contributor
    • Joined on 02-02-2010
    • CommVault Tinton Falls NJ
    • Master
    • Points 1,718

    Sounds like the Oracle restore is fine, the problem is that you performed a point in time restore of your DB, and now there are potentially some older archivelogs that are "missing/deleted" that the restored control file has a record of.  

    If you log onto the Oracle DB using RMAN you can perform a crosscheck command.  This will update the controlfile/catalog so that is is aware of the "missing/deleted" logs and will not try to back them up.  Your DBA should know the RMAN syntax for running the crosscheck. 

    Once the "missing" logs have been marked as "expired" they can also be deleted from the catalog as well.   Again this can be accomplished from an RMAN command.


    RMAN crosscheck:

    RMAN>  crosscheck archivelog all;


    RMAN log delete:

    RMAN>  change archivelog like '/path/to/archivelog/file.arc' delete;

    in your case:

    RMAN> change archivelog like '/u01/oracle/oradata/TEST/arch/arc_dupl_1_710_1002728610.arc' delete;

    Once this is done, the backups should run fine.

    Ernst F. Graeler
    Senior Engineer III
  • Re: Oracle full backup fails with RMAN script error [18:106] after restore
    Posted: 01-23-2020, 2:56 AM

    Hello Ernst

    The DBA ran the check and everything works fine now.

    Thank you very much for your fast and accurate response.

    Best regards


The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy