HP Archive Backup System for OpenVMS Guide to Operations

9.11.4 Using Tape I/O Slaves
System Backup to Tape for Oracle Databases
9.11 Troubleshooting Tips
Example 9–21 shows an example of a fatal error reported in Oracle's Recovery Manager. Example
9–22 shows what is reported in ORA_DUMP:SBTIO.LOG for the same error. The File:,
Function: and line are information for me to troubleshoot the problem if it is a software error. In
this case, there were no volumes available. Look for it in the ORA_ DUMP:SBTIO.LOG file. In
this case, you can look in the archive to see what the media type, pool, and location were.
Example 9–21 Fatal Error in Oracle's Recovery Manager
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
Fatal media movement error
Failed to allocate tape volume
MDMS object: RMAN_TAPE_TL875_ARCH
System Error: %MDMS-E-NOVOLUMES, no free volumes match selection criteria
%MDMS-E-NOVOLUMES, no free volumes match selection criteria
%MDMS-I-NOVOLSPOOL, no free volumes in the specified pool were found
Example 9–22 Fatal Error in ORA_DUMP:SBTIO.LOG
SBT-0000819F 12/17/01 14:10:20 Fatal media movement error
SBT-0000819F 12/17/01 14:10:20 Extended Status:
Failed to allocate tape volume
MDMS object: RMAN_TAPE_TL875_ARCH
System Error: %MDMS-E-NOVOLUMES, no free volumes match selection criteria
%MDMS-E-NOVOLUMES, no free volumes match selection criteria
%MDMS-I-NOVOLSPOOL, no free volumes in the specified pool were found
File: WRK$ROOT:[SRC]MDMS_SBT_API_MEDIA.C;1, Function:
sbt_media_allocate_volume,
Line 416
Failed to allocate volume with attributes:
Pool:
Media Type: TLZ88M
Location: 110281
When using tape I/O slaves, you may not receive the error message from SBT in Oracle's Recovery
Manager. Example 9–23 shows the type of error you may get reported for a tape volume
being offsite. Example 9–24 shows the tape volume offsite error reported when not using tape
I/O slaves. So when troubleshooting, also look in the trace log file ORA_ DUMP:SBTIO.LOG.
In both cases the error was reported in the trace log file.
Example 9–23 Volume Offsite Error using Tape I/O Slave
RMAN-08031: released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: vali
ate
RMAN-07004: unhandled exception during command execution on channel t1
RMAN-10035: exception raised in RPC: ORA-00447: fatal error in background
process
RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.RESTORE
ACKUPP
IECE
RMAN>
Example 9–24 Volume Offsite Error Not using Tape I/O Slave
RMAN-07004: unhandled exception during command execution on channel t1
RMAN-10035: exception raised in RPC: ORA-19507: failed to
retrieve sequential fi LE, handle="6sd8vntq_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Fatal catalog access error
Piece 6sd8vntq_1_1 cannot be restored because volume AHI164 is offsite
System Backup to Tape for Oracle Databases 9–23