Troubleshooting
This topic describes error and warning messages that may appear if a problem is encountered when trying to connect to a DB2 host or bind packages using StarAdmin.
Connection Error Messages
When you attempt to connect to a DB2 database, the StarSQL driver or the host database may return one of the following error messages if the DRDA connection cannot be established.
Reason: connect timed out
Verify that the Host value is correct and that it can be reached on the network from this computer using the 'ping' command from a Windows command prompt. Alternatively, specify the IP address as the Host.
Reason: [StarSQL][JDBC Driver] Communications error - the input stream ended abnormally while receiving data.
It is likely that the port number is valid on the host system but it is not serving a DB2 DRDA server. Verify that the DRDA port number is correct.
Reason: Unable to connect. Database stopped or incorrect port number
Verify that the port number is correct and that DB2 is running and listening on that port. If the Host value specified is the IP address, verify that this address is correct and that it can be reached on the network from this computer using the 'ping' command.
Reason: Unable to resolve hostname '<host>'
Verify that the Host is correct or, alternatively, specify the IP address in the Host field.
The database server '<Server>' was not found.
Verify that the Database Name is correct.
The password for user '<Username>' was missing or invalid. Or [StarSQL JDBC Driver][DB2] A Local Security Service retryable error has occurred.
The password entered for this user is not correct. Verify that you have the correct password and are typing the password in the correct case.
A Local Security Service retryable error has occurred can also result if the host has been configured to require a minimum encryption level of AES, for instance, if a DB2 for i administrator has issued the command CHGDDMTCPA AUTOSTART(*YES) PWDRQD(*USRIDPWD) ENCALG(*AES). In this case, configure StarAdmin to connect using SSL without password encryption:
- On the Advanced dialog, set Netlib to SQSSL.DLL, SSL to TLS, and useEncryption to No.
- On the connection dialog, enter the host's SSL listening port (e.g. 448).
The user ID was missing or invalid.
The user ID entered is not valid on the DB2 host system. Verify that you have the correct user ID and that you have typed it correctly.
Bind Error Messages
The host on which you are attempting to bind packages may return one of the following error messages if the bind operation cannot be completed.
Not authorized to object 'PACKAGE.<Package Collection> .SWRCxxxx ' type '*'. SQLSTATE=42501
The user does not have the necessary authority to create objects in the Package Collection specified. Either request the permission for this user or connect with a user account with elevated permissions.
Object QSYS.<Package Collection> type *COLLECTION not found. SQLSTATE=42704
The library or collection specified as the Package Collection does not exist on the host. Either create an empty library on the host called STARSQL and set the Package Collection parameter value to STARSQL, or specify the name of an existing library (e.g., QGPL) as the Package Collection.