How to determine Simpana backed up a specific Oracle archive log and How to determine the CV_MAGNETIC path where the file was written to?

Last post 09-21-2011, 11:04 AM by techdawg70. 0 replies.
Sort Posts: Previous Next
  • How to determine Simpana backed up a specific Oracle archive log and How to determine the CV_MAGNETIC path where the file was written to?
    Posted: 09-21-2011, 11:04 AM

    When we attempt a RMAN recovery from command line we get the following error.

    ORA-19870: error reading backup piece GEMPRD_DB_6147_03mma14h_20110911_1_761595025
    ORA-19507: failed to retrieve sequential file, handle="GEMPRD_DB_6147_03mma14h_20110911_1_761595025", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
    sbtrestore: Job[0] thread[30406]: Restore: GetBackupInfoForRestore() for Archive File[GEMPRD_DB_6147_03mma14h_20110911_1_761595025] failed
    released channel: ch1

    ****How can we validate CommVault backed up the archive log listed below?****

     

    GEMPRD_DB_6147_03mma14h_20110911_1_761595025

     

    ****How can we determine the CV_MAGNETIC path where the file was written to?****

     

    For clarity, "ALL" of the full and archive log backups for Oracle are completing without error.

    Below is a copy of our RMAN script we are executing.

    rman target sys/########@gemprd log /data/orascripts/refresh/gemini/gemuat/log/gemuat__duplicate.log catalog gemcprd/gemcprd@rmanprd auxiliary /<< EOF2
    run {
    set until scn 66940053013;
    allocate auxiliary channel ch1 type 'sbt_tape' PARMS="BLKSIZE=262144 SBT_LIBRARY=/opt/simpana/Base/libobk.so";
    allocate auxiliary channel ch2 type 'sbt_tape' PARMS="BLKSIZE=262144 SBT_LIBRARY=/opt/simpana/Base/libobk.so";
    duplicate target database to gemuat
    nofilenamecheck;
    }
    exit
    EOF2

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.
Close
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy