Diagnostic reference information

Edit online

Information about how to resolve errors that might occur during Data Protection for SAP operations is provided.

About this task

The following figure helps to isolate problems that occur when you back up or restore your DB2® database.
Figure 1. General problem isolation

This flow chart shows the path for tracking errors. Decision points are numbered and described by numbers in the following text.

After installation is completed (Step 1.1) and manual password handling is specified, set the password (Step 1.2). When the operation completes successfully, the informational messages BKI0051I: Password successfully verified for node NODENAME on server SERVERNAME and BKI0024I: Return code is: 0. display for each server that is configured within the initSID.utl file. An error message displays when a problem occurred.

These errors are frequently encountered at Step 1.2:
BKI2001E: Socket error while connecting to ProLE at IP-Address:PORT: Connection refused
On Windows™, verify that the ProLE Service is running by viewing the Computer Management Services screen or issue this command: 
net start
A list of all running services displays. On UNIX™ or Linux™, verify that the background daemon is running by issuing this command: 
 ps -ef | grep prole
Check the entry in /etc/services (UNIX or Linux) and %SYSTEMROOT%\system32\drivers\etc\services (Windows). Compare the port number from the error message with the port number within /etc/services. Also, check the entry in /etc/inittab (UNIX or Linux). If another port was set by using the option -pPORT, check this port as well. If all of this effort does not help, start the ProLE from another shell on UNIX or Linux with this command: 
prole -p PORT
Issue this command on Windows: 
prole -console -p PORT
Attempt to start backom again.
BKI5001E: IBM Storage Protect™ Error: Server not found in configuration file
On UNIX or Linux, the IBM Storage Protect server that is defined in the initSID.utl file does not match the server that is specified in the dsm.sys file. On Windows, the server.opt file might be missing.
BKI5001E: IBM Storage Protect Error: ANS1353E (RC53) Session rejected: Unknown or incorrect ID entered
This message can display when the node in the server stanza of the UTL file is not valid on the server.
HANG
If backom hangs after the password is entered, the server IP address that is specified in the UNIX or Linux dsm.sys file might be incorrect.
When Step 1.2 (setting the password) is successful, proceed to Step 1.3 and do a backup by using the DB2 backup command. Verify that the settings are correct. If the backup was successful, a message from DB2 is displayed: 
Backup successful. The timestamp for this backup image is: timestamp

If an error message displays, find the message and information about how to resolve the error.

When an error occurs, always view the Data Protection for SAP run log tdpdb2.SID.nodename.log first. This log file is in the directory that is specified by the TDP_DIR environment variable. If the variable is not specified, the log file is in the system temporary directory. If the tdpdb2.SID.nodename.log file does not exist (Step 2.2), then two cases are possible. The first case is that DB2 was unable to load the shared library that contains the DB2 connector for Data Protection for SAP. The second case is that an error was encountered before the Data Protection for SAP library was called. In both cases, a DB2 error message is displayed on the command line. It begins with the SQL prefix and is also written in the DB2 diagnostic log db2diag.log (Step 4.3). DB2 provides detailed error descriptions by issuing this command: 
 db2 ? SQLnumber
Replacenumber with the appropriate message number. Try to resolve this problem by using the DB2 documentation.

If the tdpdb2.SID.nodename.log file exists, search for a message beginning with BKIXXXXY where XXXX is a four-digit number, and Y is the letter I, W, or E. When such a message occurs, the DB2 connector for Data Protection for SAP that loaded correctly is called by DB2. In Step 3.1, the tdpdb2.SID.nodename.log file is created and an error message that starts with BKI is recorded.