Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC93536 Status: Closed

DB2ADULT RETURNS READING OF DB CFG FILE FAILED! AND TSM RC=137 IN PURESCALE
INSTANCE ENV

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
1.  Problem description 
db2adult may acquire an incorrect partition number for databases 
within a pureScale environment not created on member zero. 
Causes db2adutl to be unable to correctly resolve the database 
path and retrieve a TSM password stored within the database 
configuration file. 
 
db2adutl query full db customdb 
Reading of DB CFG file failed! 
 
Error: Initialize session failed with TSM return code 137
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 FP3                                         * 
****************************************************************
Local Fix:
Always create your database on member zero or manually specify 
the TSM password.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First Fixed in V10.1 FP3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList