Oracle Secure Backup (obtool) exit codes
When obtool encounters an error, it reports an exit code with a brief description. An exit code file called obexit.h is available at /usr/local/oracle/backup/samples. It lists and describes all obtool exit codes.
The table below holds the content of the obexit.h file for convenience. You might find it useful to anticipate errors and branch accordingly when building obtool scripts.
| Exit Code | Definition |
|---|---|
| 0 | Backup/Restore successful |
| General Errors | |
| 1 | general cmd line syntax or semantic error |
| 2 | none of the names requested to be backed up or restored were found |
| 3 | user is not a member of the operator group, yet supplied -R on cmd line |
| 4 | couldn't fork to start a subprocess |
| 5 | couldn't exec a required subprogram |
| 6 | couldn't obtain a needed resource |
| 7 | backup was interrupted by keyboard signal |
| 8 | read an eof from kbd/user input |
| 9 | system fatal error - very bad news |
| 10 | protocol version mismatch |
| 11 | executed program (before/after backup) failed |
| 12 | couldn't setup background I/O |
| 13 | operation was killed with SIGTERM |
| 14 | client host ran out of malloc'able memory |
| 15 | admin hosts skewed between client & server |
| 16 | filer delivered duplicate inodes in NODE recs |
| 17 | covers the NDMP__ILLEGAL_ARGS_ERR |
| 18 | covers the NDMP__NOT_AUTHORIZED_ERR |
| 19 | the requested backup level is not supported for one or more of the requested databases |
| Host Unavailable Errors | |
| 20 | all hosts whose data were supposed to be backed up (or to which data were supposed to be restored) were unavailable, or could not run the Reliaty Backup software |
| 21 | a communications failure occurred with all hosts supplying backup data (or receiving restoration data) occurred after the backup or restore was started |
| 22 | the host attached to the tape drive was unavailable or could not run the Reliaty Backup software |
| 23 | a communications failure with the host attached to the tape drive occurred after the backup or restore operation was started |
| 24 | the administrative host was unavailable or could not run the Reliaty Backup software |
| 25 | a communications failure with the administrative host occurred after the backup or restore operation was started |
| 26 | the BDF host was unavailable or could not run the Reliaty Backup software |
| 27 | a communications failure with the BDF host occurred after the backup or restore operation was started |
| 28 | the index host was unavailable or could not run the Reliaty Backup software |
| 29 | a communications failure with the index host occurred after the backup or restore operation was started |
| Admin File Unavailability Errors | |
| 30 | the backup description file could not be read |
| 31 | BDF is unusable because it has errors |
| 32 | the volume id file could not be read or written |
| 33 | the backup_history file could not be read or written |
| 34 | the index file could not be read or written |
| 35 | NT bdf contains non-absolute pathnames |
| 36 | undefined user or missing login token |
| 37 | restart of this operation is not possible |
| Label Event Errors | |
| 38 | label event error |
| Volume Error | |
| 39 | volume is in use by another process |
| Archive Device Errors | |
| 40 | the archive device could not be opened because it was busy |
| 41 | the archive device could not be opened (general) |
| 42 | the archive device was not ready, and did not come ready after a reasonable amount of time had elapsed |
| 43 | the archive device encountered an unrecoverable media error |
| 44 | the backup could not be performed because the media in the drive was write-protected |
| 45 | the archive device reported an unexpected error |
| 46 | device does not exist |
| 47 | permission denied on device open |
| 48 | remote access to device was denied |
| 49 | validation check failed when opening archive device |
| Volume Set/Archive Content Errors | |
| 50 | the requested archive file number (-F #) doesn't exist |
| 51 | the format of the volume set is corrupt |
| 52 | the format of the archive being read is corrupt |
| 53 | inconsistent usage of labeling on the same volume (set) |
| 54 | tape position is unknown and not discernable |
| 55 | the wrong volume was used |
| 56 | archive or volume set not expired |
| 57 | volume set already expired |
| 58 | archive expires later than volume set |
| 59 | can no longer write to this volume; it's closed |
| Restore Specific Errors | |
| 60 | could not create the file or directory being restored |
| 61 | the destination directory doesn't exist |
| 62 | a bad position string was given following -q |
| 63 | could not set protection |
| 64 | could not close object |
| 65 | could not set attribute (size, dtm) of object |
| 66 | could not write to object |
| 67 | could not seek in object |
| 68 | no rights to access backup image |
| 69 | incorrect decryption key provided |
| Library Related Errors | |
| 70 | device not connected to library and/or library database missing |
| 71 | library and/or drive database corrupted |
| 72 | library encountered empty slot |
| 73 | library could not find eligible slot |
| 74 | other library error |
| 75 | barcode is required on volume |
| 76 | connection to rbrobotd lost |
| Archive Device Errors (cont'd from 40-49) | |
| 80 | tried to change tape format when not at bot |
| 81 | mount mode doesn't allow this operation |
| 82 | quit out of lm manual mode |
| 83 | archive section verification failed |
| 84 | block size is too large for maxblockingfactor |
| 85 | drive unload operation failed after maxdriveidle time |
| 86 | NDMP device does not support the file service extension |
| 87 | disk pool space exhausted |
| 88 | A tape may be stuck in the drive. |
| General Errors (cont'd from 1-19) | |
| 89 | storage encryption error |
| 90 | a service that must be stopped is running |
| 91 | a service that must be running is stopped |
| 92 | a required library is unavailable |
| 93 | internal RB consistency error |
| 94 | backup of all requested files failed |
| 95 | one or more errors during backup |
| 96 | must be root to perform this operation |
| 97 | general NDMP internal error reported |
| 98 | unknown NDMP error reported |
| 99 | NDMP configuration error |
| 100 | some of the names mentioned on the command line or in the BDF were not found (on disk, or in the archive) |
| 101 | some of the names mentioned on the command line or in the BDF were found (on disk, or in the archive), but could not be backed up or restored |
| 102 | one or more (but not all) of the hosts whose data were supposed to be backed up were inaccessible or could not run the Reliaty Backup software |
| 103 | a communications failure occurred following a partial backup or restoration to the host supplying or receiving the data |
| 104 | domain certificates are going to expire soon. |
| 105 | copy instance job partially completed (some failed) |
| 110 | the archive device doesn't support direct-to-block positioning |
| 111 | could not obtain exit status of remote qtar probably because the status file could not be read |
| 112 | one or more of the requested files encountered failures during backup |
| 113 | unable to update the backup-dates file |
| 114 | one or more warnings or non-critical errors were reported |
| 115 | this path is invalid for NDMP filers |
| 116 | given operation is not supported |