DB2 vendor reason codes
Data Protection for SAP uses these reason codes, which might also be displayed or logged by DB2® in the case of problems.
| Reason code | Explanation | User response |
|---|---|---|
| 1 | The library that is specified could not be loaded. | Check the DB2 diagnostic log for further details. |
| 2 | Communication error between shared library and ProLE | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log for further details. |
| 6 | Object that is specified cannot be found on IBM Storage Protect™. | There is no backup image on IBM Storage Protect matching the search criteria. |
| 10 | Invalid options that are specified with the options parameter of the DB2 backup/restore command. | Check the options string that is specified and check the Data Protection for SAP run log file tdpdb2.SID.nodename.log for further details. |
| 11 | Initialization procedure for shared library failed. | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log and the DB2 diagnostic log file for further details. |
| 17 | During end processing of either backup/archive or restore/retrieve session or sessions, an error occurred. | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log for further details. |
| 18 | An error occurred during reading or writing data from or to IBM Storage Protect. | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log for further details. |
| 26 | An error occurred during deleting data from IBM Storage Protect. | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log for further details. |
| 29 | A terminate request from DB2 could not be handled correctly. | Check the Data Protection for SAP run log file tdpdb2.SID.nodename.log and the DB2 diagnostic log file for further details. |
| 30 | A severe error occurred. | Check the DB2 diagnostic log file for further details. |