OSB - "Error: can't execute command - drive didn't come online" when loading tape into drive
(Doc ID 960972.1)
Last updated on DECEMBER 01, 2019
Applies to:Oracle Secure Backup - Version 10.3.0.1 to 10.3.0.3 [Release 10.3]
Information in this document applies to any platform.
Checked for relevance on 29-Jun-2011.
When using Oracle Secure Backup (OSB) and attempting to load a tape into a tape drive (DTE*), the following error is observed:
"Error: can't execute command - drive didn't come online; check configuration/hardware"
This error message arises whether the tape is being loaded into a drive by issuing 'obtool loadvol', using web tool or via automount during a backup or restore operation.
(*) DTE -- Data Transfer Element -- the SCSI term for a tape drive inside a robotic library.
This error often indicates that the DTE number and device attachment used to create the drive with 'obtool mkdev' did not match those from the hardware's perspective so an incorrect DTE number has been assigned.
NOTE: When trying to resolve misappropriated drives (depending on your hardware) it is sometimes possible to get the serial numbers for 'drive1'(DTE1) and 'drive2' (DTE2) from the control panel of your library. You can then compare these to the serial numbers output from 'obtool lsd -lvdg' to see which DTE numbers have been assigned to the tape drives. By comparing serial numbers the attachments can be changed in OSB so that there is correspondence between the hardware and OSB. This can be especially helpful if there are more than 2 tape drives in the library and you're having trouble sorting out the DTE numbers and their attachments.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document