QE-DEF-0285 The logon failed with Reason code: "3".

Technote (troubleshooting)


Problem(Abstract)

ITNM v3.9 new installation with NCIM configured in DB2. TCR cognos reports are not generating, showing an logon failed error SQL10007N Message "0" could not be retrieved. Reason code: "3". Attached screenshot has complete error details.

Symptom

QE-DEF-0325 The logon failed for the following reason:RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: NCIM UDA-SQL-0031 Unable to access the "NCIM" database.UDA-SQL-0107 A general exception has occurred during the operation "attach".[IBM][CLI Driver] SQL10007N Message "0" could not be retrieved. Reason code: "3".


Cause

Multiple DB2 instances running on the same database like db2inst1, db2inst2

Diagnosing the problem

Make sure the environment variable pointing to correct NCIM instance, for example

DB2INSTANCE=db2inst1.


Resolving the problem

SQL10007N Message msgno could not be retrieved. Reason code: code.

Explanation
The requested message <msgno> could not be retrieved from the message file. Reason code <code> is one of the following:
1. The environment variable “DB2INSTANCE” is either not set, or is set to an invalid instance. Correct it and try again.
2. The message file was found, but the file could not be opened because of permissions. Check the file permissions of the files under the message directory.
3. The message file could not be found. Either the file does not exist, or the directory the message file should be in does not exist. Check that either a default directory or a directory with the same name as the 'LANG' environment variable exists under the message directory.
4. The requested message does not exist in the message file. Either the message file is outdated, or it is the wrong one.
5. Either DB2CODEPAGE is set to a code page which the database does not support, or the client's locale is not supported by the database.
6. An unexpected system error occurred. Try execution again. If problem persists, contact your IBM representative.
7. Not enough memory. An attempt to get private memory failed. Try again.
User response
Reissue the command after verifying the following:

  • ensure that the DB2INSTANCE environment variable is set to the correct literal string for the username attempting this command
  • ensure that correct home directory is specified for the username attempting this command (i.e. in the /etc/passwd file)
  • ensure that the LANG environment variable is set to the correct value for the installed language, or is set to 'C', on the username attempting this command
  • Even if the message file is outdated, you can still find up-to-date information about the message in the database server documentation.

If all of the above are correct and the error still occurs, reinstall DB2.

Related information

DB2 Doc

Historical Number

71230
000
744

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Network Manager IP Edition

Software version:

3.9

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1649150

Modified date:

2013-09-23

Translate my page

Machine Translation

Content navigation