DB2 ERRORCODE以及SQLSTATE错误解决方案小结
The DB2 Content Manager installation is blocked: failure to connect to the DB2 database
| ||||||
ERRORCODE以及SQLSTATE错误解决方案小结" alt="" src="http://www-01.ibm.com/support/docview.wss?uid=swg21322400&aid=1" border="0" real_src="http://www-01.ibm.com/support/docview.wss?uid=swg21322400&aid=1"> | ||||||
| ||||||
Cause | ||||||
Error 1: DB2 return code is
-4499 Three problems might be the cause of this error.
Error 2: DB2 return code is -4222 For this problem, the host name is probably specified incorrectly. Error 3: DB2 return code is -4214 Three problems might be the cause of this error.
| ||||||
| ||||||
| ||||||
Resolving the problem | ||||||
The following procedures might help you resolve the connection
failure problem: Resolving Error 1: DB2 return code is -4499
|
- Check the DB2 listening port. The DB2 instance is listening on Port 50000 by default, but the port number might have been modified.
- Restart DB2 or restart the computer on which DB2 is running, because there
might be too many connections already active for DB2 to respond to the new
request.
Resolving Error 2: DB2 return code is -4222- If the wrong host name is specified, or the DNS server cannot parse the host name, then you can use the command ping hostname, where hostname is the host name, to test the connection. You can also use the IP address directly in this command.
- Check the privileges of folder /tmp/CM/db2cmv8. The DB2 Content Manager installer performs the su command to DB2 Content Manager accounts to test the connection. For example, if you have an icmadmin account as the library server administrator, the installer uses this account, creates a shell script under the /tmp/CM/db2cmv8 folder, and runs it to see the result. If the folder does not have the write and execute privileges for icmadmin, the connection test fails.
Resolving Error 3: DB2 return code is -4214 - Check that the user name and password are specified correctly.
- Check that the password does not contain special characters, such as the dollar sign ($).
ANR2971E Database backup fails with DB2 sqlcode -5005 error
Technote (troubleshooting)
Problem(Abstract)
Tivoli Storage Manager DB backup fails with DB2 sqlcode -5005 error.
Symptom
While attempting to run BACKUP DB the command fails, and the activity log reports the following error message:
ANR2971E Database backup/restore/rollforwardterminated - DB2 sqlcode -5005 error.
The db2diag.log shows following error:
2013-06-29-10.38.23.072007-420 I1493A414 LEVEL: Error
PID : 5308450 TID : 772 PROC : db2acd 0
INSTANCE: tsminst1 NODE : 000
EDUID : 772 EDUNAME: db2acd 0
FUNCTION: DB2 UDB, config/install, sqlfGetDbmCfg, probe:10
MESSAGE : SQL5005: sqlf_openfile rc =
DATA #1 : Hexdump, 4 bytes
0x000000011050A250 : 860F 000A
Cause
The sqlcode -5005 translates to:
"The operation failed because the database manager failed to access either the database manager configuration file or the database configuration file."
Diagnosing the problem
When querying DB2 for more details on this error the following explanation is shown:
$ db2 "? sql5005"
SQL5005C System Error.
Explanation:
A system error, probably an I/O error, was encountered while accessing a configuration file.
The command cannot be processed.
User Response:
Resubmit the command.
If the error persists, check the db2diag.log file for details and ensure that the configuration file is accessible. If unable to resolve the problem, contact an IBM Service Representative for assistance.
Resolving the problem
The db2systm configuration file is created in the sqllib subdirectory of the instance directory (/home/<instance_name>/sqllib) when the instance is initially created.
To resolve this error, check following:
1. The permissions for this file should be similiar to the following:
-rw-rw-r-- 1 <instance_name> <sysadm group> 16384 Jun 29 2013 db2systm
2. If the db2systm file is not present then contact DB2 support for further assistance.
Product Alias/Synonym
TSM