|
Problem IC65705
|
Status: Geschlossen |
PANIC/CRASH IN SQLPLUHD() TRYING TO UNHOLD AN INVALID LOCK FOLLOWING A -911 (LOCK TIMEOUT) ERROR IN THE DB2DIAG.LOG |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
When trying to unhold a lock for a given agent in function
sqlpluhd(), we panic/crash the instance. This happens
immediately after -911 (lock timeout) error message. You will
see similar entries as following in your db2diag.log:
.
2009-08-19-07.04.47.955650+000 I415597A422 LEVEL: Error
PID : 145102 TID : 1 PROC :
db2agntp (DBAP) 0
INSTANCE: <inst_name> NODE : 000 DB :<db_name>
APPHDL : 99-1123 APPID: <app_id>
AUTHID : <auth_id>
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
MESSAGE : Received sqlcode -911 for request 80000004 from node
number 1
[...]
2009-08-19-07.05.02.689675+000 I418443A1618 LEVEL: Severe
PID : 275430 TID : 1 PROC :
db2agntp (DBAP) 0
INSTANCE: <inst_name> NODE : 000 DB :<db_name>
APPHDL : 99-1120 APPID: <app_id>
AUTHID : <auth_id>
FUNCTION: DB2 UDB, lock manager, sqlpluhd, probe:10
MESSAGE : ZRC=0x82100001=-2112880639=SQLP_NONSEVERE_PRGERR
"DPS detects non-severe programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 22 bytes
Invalid lockInfo->pLRB
CALLSTCK:
[0] 0x0900000002DFCB9C sqlzSetAndLog901 + 0x29C
[1] 0x090000000360337C
sqlpluhd__FP20sqle_agent_privatecbP14SQLP_LOCK_INFO + 0
x4B4
[2] 0x090000000344D150
sqldmclo__FP20sqle_agent_privatecbPP8SQLD_CCBi + 0x6A8
[3] 0x0900000003ACE404
sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3U
iN26P8SMemPoolP21sqlrlc_systables_infoP8SQLZ_RIDPUi + 0x1A08
[4] 0x0900000003AD2944
sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry |
| Problem-Zusammenfassung: |
When trying to unhold a lock for a given agent in function
sqlpluhd(), we panic/crash the instance. This happens
immediately after -911 (lock timeout) error message. You will
see similar entries as following in your db2diag.log:
.
2009-08-19-07.04.47.955650+000 I415597A422 LEVEL: Error
PID : 145102 TID : 1 PROC :
db2agntp (DBAP) 0
INSTANCE: <inst_name> NODE : 000 DB :<db_name>
APPHDL : 99-1123 APPID: <app_id>
AUTHID : <auth_id>
FUNCTION: DB2 UDB, base sys utilities, sqleMergeSqlca, probe:20
MESSAGE : Received sqlcode -911 for request 80000004 from node
number 1
[...]
2009-08-19-07.05.02.689675+000 I418443A1618 LEVEL: Severe
PID : 275430 TID : 1 PROC :
db2agntp (DBAP) 0
INSTANCE: <inst_name> NODE : 000 DB :<db_name>
APPHDL : 99-1120 APPID: <app_id>
AUTHID : <auth_id>
FUNCTION: DB2 UDB, lock manager, sqlpluhd, probe:10
MESSAGE : ZRC=0x82100001=-2112880639=SQLP_NONSEVERE_PRGERR
"DPS detects non-severe programming error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 22 bytes
Invalid lockInfo->pLRB
CALLSTCK:
[0] 0x0900000002DFCB9C sqlzSetAndLog901 + 0x29C
[1] 0x090000000360337C
sqlpluhd__FP20sqle_agent_privatecbP14SQLP_LOCK_INFO + 0
x4B4
[2] 0x090000000344D150
sqldmclo__FP20sqle_agent_privatecbPP8SQLD_CCBi + 0x6A8
[3] 0x0900000003ACE404
sqlrlc_systables_fetch_from_disk__FP8sqlrr_cbPUcUsT2T3U
iN26P8SMemPoolP21sqlrlc_systables_infoP8SQLZ_RIDPUi + 0x1A08
[4] 0x0900000003AD2944
sqlrlc_systables_load_entry__FP8sqlrr_cbP22sqlrlc_entry |
| Local-Fix: |
Stopping the load may reduce the chance of hitting this problem
until you have a fix for this APAR in place. |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Lösung |
Defect => wsdbu00584324
Fixed in => V9.7 + FP2
Module => ENGN_SQR |
| Workaround |
Stopping the load may reduce the chance of hitting this problem
until you have a fix for this APAR in place. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 20.01.2010
10.06.2010
10.06.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
