HP Archive Backup System for OpenVMS Guide to Operations

System Backup to Tape for Oracle Databases
9.11 Troubleshooting Tips
9.11.2 Fatal Internal Error
SBT-00008140 12/17/01 09:50:50 MBytes/sec: 1.752 10
SBT-00008140 12/17/01 09:50:50 Bytes/sec : 1752820.870 11
The following describes the entries in Example 9–19:
1. DB block size:-this is the size of blocks that Oracle sends to SBT.
2. I/O block size:-this the size of blocks that SBT writes to the I/O device. You can change this
with the logical MDMS$SBT_IO_BLOCK_SIZE which can be specified in an Oracle
Recovery Manager script or as a system wide logical.
3. Total I/Os:-total I/Os to write the I/O block size blocks to the I/O device. In this example:
620 total I/Os writing 65024 byte blocks to the I/O device.
4. Total I/O wait:-this is the number of milliseconds that SBT waited while the blocks are
being written to the I/O device.
5. Maximum I/O wait:-this is the longest wait that SBT made to write a block to the I/O
device.
6. Average I/O wait:-this the average wait of the total I/Os for the total I/O wait time.
7. Total Kbytes:-total Kbytes transferred to the I/O device. It is a truncated value. See total
bytes below.
8. Total bytes:-total bytes transferred to the I/O device.
9. Total seconds:-this is the number of seconds that SBT waited while the blocks are being
written to the I/O device. This does not have the time that Oracle took to provide the information
to write to the I/O device. The value is truncated from the total I/O wait in milliseconds.
10. Mbytes/sec:-Mbytes per second transferred based on total Kbytes and total seconds.
11. Bytes/sec:-bytes per second transferred based on total bytes and total seconds.
Note
These values are the time that SBT waited for the I/O device to give back control. The
values have nothing to do with how long it took Oracle to give information to SBT.
If you should ever get an Internal error, you should report it to the customer support center.
Example 9–20 shows an example of a fatal internal error. Anyplace that SBT could have
received a value that it did not expect, it is captured and reported as a fatal internal error.
Example 9–20 Fatal Internal Error Example
SBT-00001DB2 12/17/01 13:53:45 Internal error
SBT-00001DB2 12/17/01 13:53:45 Extended Status:
The invalid archive type, 23
SBT-00001DB2 12/17/01 13:53:57 ABEND (abnormal end ) was passed
in sbtend flag
9.11.3 Check ORA_DUMP:SBTIO.LOG for Errors
Any time you receive an error in Oracle's Recovery Manager that is related to SBT, you should
check ORA_DUMP:SBTIO.LOG for errors. We are limited to 250 characters returned to the
Oracle Recovery Manager. Therefore, you may not receive all of the information about the error.
However, I am not limited to what I put in the ORA_DUMP:SBTIO.LOG file. So be sure to look
in ORA_DUMP:SBTIO.LOG when getting an error message that in not all there.
9-22 System Backup to Tape for Oracle Databases