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 IC76622 Status: Geschlossen

MEMORY FAULT : WHEN AUTHENTICATION IS CLIENT AT THE SERVER AND NEWPWD IS
SPECIFIED FROM THE CLIENT WITHOUT USERID.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When authentication is client at the server and trying to 
connect to server using NEWPWD in the connection string and 
there is no UID in the connection string, Memory Fault is 
received. 
Steps 
1. Set the authentication as client at the server. 
    db2 update dbm cfg using authentication client 
 
2. Now in the client pass this commands 
 
opt callerror on 
opt echo on 
SQLAllocEnv 1 
SQLAllocconnect 1 1 
db2trc on 
sqldriverconnect 1  0 
"PROTOCOL=TCPIP;HOSTNAME=9.124.100.24;DATABASE=test123;PORT=5000 
0;newpwd=sdsdsd" 
-3 500 SQL_DRIVER_NOPROMPT 
 
There is a Memory Fault. 
 
Issue can be reproducible from all clients.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* When CLI driver is used for remote server.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When authentication is client at the server and trying to    * 
* connect to server using NEWPWD in the connection string and  * 
* there is no UID in the connection string, Memory Fault is    * 
* received.                                                    * 
* Steps                                                        * 
* 1. Set the authentication as client at the server.           * 
*     db2 update dbm cfg using authentication client           * 
*                                                              * 
* 2. Now in the client pass this commands                      * 
*                                                              * 
* opt callerror on                                             * 
* opt echo on                                                  * 
* SQLAllocEnv 1                                                * 
* SQLAllocconnect 1 1                                          * 
* db2trc on                                                    * 
* sqldriverconnect 1  0                                        * 
* "PROTOCOL=TCPIP;HOSTNAME=9.124.100.24;DATABASE=test123;PORT= * 
* 50000;newpwd=sdsdsd" -3 500 SQL_DRIVER_NOPROMPT              * 
*                                                              * 
* There is a Memory Fault.                                     * 
*                                                              * 
* Issue can be reproducible from all clients.                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp5 or later releases.                     * 
****************************************************************
Local-Fix:
use NEWPWD with UID and PWD in the connection string.
verfügbare FixPacks:
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

Lösung
db2_v97fp5 contains the fix. After the fix, CLI will give proper 
error without any memory fault.
Workaround
use NEWPWD with UID and PWD in the connection string.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.05.2011
12.12.2011
12.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.5 FixList