Loading...
Loading...
Observed Symptoms Multiple PDB backups run in parallel in an Oracle Multitenant environment. One PDB backup fails during execution. All other parallel PDB backups also fail, although they do not have direct errors. The issue occurs only when the RMAN script includes a taskfile parameter. Example RMAN script: connect target / run {allocate channel t1 type sbt PARMS 'SBT_LIBRARY=/usr/local/avamar/lib/libobk_avamar64.so' SEND '"--prefix=19c/PDB1/" "--flagfile=/home/oracle/flagfile.txt" "--taskfile=/home/oracle/taskflag1.txt" "--bindir=/usr/local/avamar/bin" "--cacheprefix=PDB1" "--vardir=/usr/local/avamar/var"' trace 5;backup format "PDB1_%U" filesperset 4 incremental level 0 pluggable database PDB1;} Error message channel t1: starting piece 1 at 13-APR-22 released channel: t1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on t1 channel at 04/13/2022 11:15:11 ORA-27192: skgfcls: sbtclose2 returned error - failed to close file ORA-19511: non RMAN, but media manager or vendor specific failure, error text: sbtclose2: invalid response from avoracle NOTE: This KB article does not apply if: The backup is scheduled from Avamar server. If there is NO --taskfile in the rman script used to do backups.
Avamar queries Oracle dynamic views to determine RMAN backup status. The product continuously checks for failure indicators during backup execution. The following conditions apply: The queries search for keywords such as FAILED , ERRORS , or RMAN-03099 . If any query result contains these keywords, Avamar marks the backup as failed. During concurrent PDB backups: All sessions share the same Oracle instance views. If one PDB backup fails, its failure appears in the query results. Other running PDB backups detect the failure in the shared query output. Avamar incorrectly marks all concurrent backups as failed.
Use one of the following workarounds: Option 1: Remove Taskfile From RMAN Script Edit the RMAN script. Remove the --taskfile parameter from the rman string. Save the script. Run the backup again. Option 2: Use Avamar Scheduler Configure the backup through the Avamar Administrator or Avamar Server Scheduler. Avoid using custom RMAN scripts with taskfile parameters. Additional Information / Notes This behavior applies only to concurrent PDB backups that use a taskfile. The issue does not occur when taskfile is not used. The issue affects Oracle Multitenant environments with parallel backup execution.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.