home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC86589 Status: Closed

DB2ADUTL FAILS WITH 137 WHEN USING PASSWORDACCESS PROMPT & DB CFG
TSM_PASSWORD SET TO A VALUE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2adutl will fail with 137 when you have the following: 
 
dsm.sys contains: 
    PASSWORDACCESS PROMPT 
 
db2 connect to SAMPLE 
db2 update db cfg using TSM_PASSWORD <password> 
 
db2adutl query db SAMPLE 
 
fails with: 
 
Error: Initialize session failed with TSM return code 137
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 Fixpack 2 or higher                         * 
****************************************************************
Local Fix:
db2adutl query db SAMPLE PASSWORD <password>
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 Fixpack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2012
09.01.2013
09.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList