|
Problem IC84336
|
Status: Geschlossen |
DB2 SNAPSHOT MONITOR MAY RETURN SQL1042C ERROR WHEN THERE ARE INDOUBT TRANSACTIONS |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
When there are indoubt transactions, db2 get snapshot for locks
on <db2_name> may receive sql1042c error.
E.g.
$ db2 get snapshot for locks on sample
SQL1042C An unexpected system error occurred. SQLSTATE=58004
The following records could be found in db2 trace:
| | | | | | | | | sqm___sqm_snap_db_locks entry [eduid 80577
eduname db2agent]
| | | | | | | | | | sqlpm_write_locks_indoubt_tran entry [eduid
80577 eduname db2agent]
| | | | | | | | | | | sqlpm_write_locks entry [eduid 80577
eduname db2agent]
| | | | | | | | | | | | pdLogPrintf entry [eduid 80577 eduname
db2agent]
| | | | | | | | | | | | | pdIsDiagLevelOk entry [eduid 80577
eduname db2agent]
| | | | | | | | | | | | | pdIsDiagLevelOk data [probe 10]
| | | | | | | | | | | | | pdIsDiagLevelOk data [probe 20]
| | | | | | | | | | | | | pdIsDiagLevelOk data [probe 500]
| | | | | | | | | | | | | pdIsDiagLevelOk exit
| | | | | | | | | | | sqlpm_write_locks data [probe 55]
| | | | | | | | | | | | pdLogPrintf exit
| | | | | | | | | | | sqlpm_write_locks exit [rc =0x000004E2 =
1250]
diag.log shows:
2012-01-25-11.22.21.035956-300 E853625A479 LEVEL: Info
PID : 2687188 TID : 89596 PROC : db2sysc
0
INSTANCE: NODE : 000
APPHDL : 0-1403 APPID:
AUTHID :
EDUID : 89596 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, lock manager, sqlpm_write_locks, probe:55
DATA #1 : <preformatted>
Transaction changed underneath sqlpm_write_locks.
tidhdl=2, tentryState=7
2012-01-25-11.22.21.036274-300 I854105A798 LEVEL: Info
PID : 2687188 TID : 89596 PROC : db2sysc
0
INSTANCE: NODE : 000
APPHDL : 0-1403 APPID:
AUTHID :
EDUID : 89596 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1042 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLMSSAG
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000040
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 58004 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Db2 v10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Uprade to DB2 10.1 fixack 2 *
**************************************************************** |
| Local-Fix: |
using db2pd -locks -db <db_name> to collect lock information |
| 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 |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.06.2012
02.11.2012
02.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
