Loading...
Loading...
Restoring an Oracle RMAN client using script should first restore the spfile or control file from the AUTOBACKUP.However, in this scenario, the RMAN process fails with the following error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 11/02/2022 16:02:35 RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece The avtar.log file presents the following error: 2022-11-10 11:58:33 avtar Info <5582>: Avamar Server login successful 2022-11-10 11:58:33 avtar Info <5018>: - Session ID: 0 2022-11-10 11:58:33 avtar Info <10632>: Using Client-ID='d3073128693e484ef2d9b4f48c33fa12ce1e538e' 2022-11-10 11:58:33 avtar Info <5550>: Successfully logged into Avamar Server [19.4.0-124] 2022-11-10 11:58:34 avtar Info <5922>: History of /c-2502688994-20221110-02 for /OracleClients/csuxprdbs079.chorus.co.nz as of 2022-11-10 11:58:34 NZDT 2022-11-10 12:06:06 avtar Error <5920>: File /c-2502688994-20221027-06 not found. 2022-11-10 12:06:06 avtar Info <6149>: Error summary: 1 error: 5920 2022-11-10 12:06:06 avtar Info <5314>: Command failed (1 error, exit code 10027: no matching backups selected) However, from the Avamar User Interface (AUI) the AUTOBACKUP is available with the specified name.Below is an example of the script used for this restore: RMAN> connect target * 2> run { 3> allocate channel c1 device type sbt_tape PARMS="SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so"; 4> send channel 'c1' '"--prefix=/" "--flagfile=/u01/app/oracle/datacom/scripts/rmanBackup/avamar/var/restore.avtar.txt" "--bindir=/usr/local/avamar/bin"'; 5> set dbid=2502688994 6> restore spfile to pfile '/u01/app/oracle/product/19.3.0.0/dbhome_1/dbs/initTESTNCDB.ora' from 'c-2502688994-20221027-06'; 7> release channel c1; 8> }
The environment may have multiple Oracle databases (DBs) in the same client.The AUI did not run the Oracle restore backup and was not grouped with a prefix.
According to the Oracle RMAN User Guide, the Avamar Plug-in for Oracle supports the selection of multiple databases for both backup and restore operations. When multiple databases are backed up on the same workorder, they are logically grouped. This is so that the Avamar Administrator UI or AUI can present a hierarchical view of the databases during subsequent restore operations. This grouping is done by prefixing a path that consists of the ORACLE-INSTANCE and ORACLE-SID to each database within the backup.For example, an Oracle 11g database with ORACLE-SID set to orcl is prefixed with /11g/orcl/.If the system has multiple DBs on the same Oracle client, it must be checked to see if the DBs are grouped with a prefix first. Then use the correct prefix as per the example.If the prefix is unknown and --prefix=/ is added to the script, it limits the AUTOBACKUP search to no database. This causes the failure to find an available AUTOBACKUP.This issue is resolved by removing the --prefix=/ option from the script. The available AUTOBACKUP can be found, and the spfile/control file restore succeeds.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.