home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68341 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* when trying 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:                                              * 
* Connect to db using the user ID and password and then        * 
* issuethe update db cfg command. Upgrade to db2_v95fp7.       * 
****************************************************************
Local-Fix:
Connect to db using the user ID and password and then issue the 
update db cfg command.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This issue first fixed in db2_v95fp7. After the fix, the issue 
 
got resolved.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69209 IC69210 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.05.2010
18.10.2010
18.10.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.1.0.7 FixList
9.5.0.7 FixList