|
Problem IC84239
|
Status: Geschlossen |
SQLOSPAWNANDWAITFORPASSWORDCHECKEXE MAY REPORTS FALSE DEADLOCK MESSAGES IN DB2CKPWD |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
sqloSpawnAndWaitForPasswordCheckExe may report false messages (
deadlock, out of memory ) in db2diag.log
like
2000-00-00-00.00.00.000000+000 LEVEL: Severe
PID : 11111111111 TID : 111 PROC : db2ckpwd
0
INSTANCE: xxxxxx NODE : 000
EDUID : 111 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, oper system services,
sqloSpawnAndWaitForPasswordCheckExe, probe:130
MESSAGE : ZRC=0x800F006A=-2146500502=SQLO_BAD_USER "Bad User"
DIA8117C Error with userid "".
CALLED : DB2 UDB, oper system services, db2ckpw::main
RETCODE : ZRC=0x00000002=2
DIA8002C A deadlock has occurred, rolling back
transaction.
This is happening because of incorrect usage of ZRC codes
received from db2ckpw executable in db2 diaglog printing
function. This messages are not indication of real deadlocks or
other events and can be safely ignored. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fixpak 1 *
**************************************************************** |
| Local-Fix: |
n/a |
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
|
| Lösung |
First fixed in DB2 V10.1 Fixpak 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.06.2012
29.04.2013
29.04.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
