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 IC69209 Status: Closed

SQL30082N ERROR WITH RC=3 ("PASSWORD MISSING") OCCURS WHEN ONE
ATTEMPTS TO UPDATE A REMOTE DATABASE'S DB CFG PARAMETER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When one tries to update a remote database's following database 
configuration parameters: logbufsz, dbheap, locklist, and 
stmtheap; SQL30082N Security processing failed with reason "3" 
("PASSWORD MISSING"). SQLSTATE=08001 error is returned on the 
Client side. 
 
To reproduce the problem: 
 
1. db2 attach to <remote node> user <user ID> using <password> 
2. db2 create database <db name> using codeset UTF-8 territory 
us collate using identity 
3. db2 update db cfg for <db name> using logbufsz <value>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* When user try to update db cfg of a remote database.         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When one tries to update a remote database's                 * 
* followingdatabaseconfiguration parameters: logbufsz, dbheap, * 
* locklist, andstmtheap; SQL30082N Security processing failed  * 
* with reason"3"("PASSWORD MISSING"). SQLSTATE=08001 error is  * 
* returned ontheClient side.To reproduce the problem:1. db2    * 
* attach to <remote node> user <user ID> using<password>2. db2 * 
* create database <db name> using codeset UTF-8territoryus     * 
* collate using identity3. db2 update db cfg for <db name>     * 
* using logbufsz <value>                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v97fp3 or later version.                      * 
****************************************************************
Local Fix:
Connect to db using the user ID and password and then issue the 
update db cfg command.
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
db2_v97fp3 includes the fix of this issue. After the fix, 
 
customer will not see any error message.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2010
23.09.2010
23.09.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList