suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT23321 Status: Closed

DB2 MIGHT PANIC WHEN ATTEMPTING TO UNLOCK AN INVALID LATCH AFTER
HDRCLOSECONN CALL ON TCP/IP ERROR

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
db2diag.log shows :

2017-11-21-20.02.25.180837+480 I301643E505           LEVEL:
Error
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSendBuffer, probe:20000
MESSAGE : Error sending data: errno
DATA #1 : Hexdump, 8 bytes
0x00002AAAC77F7BB8 : 2000 0000 0000 0000
.......

2017-11-21-20.02.25.181021+480 I302149E517           LEVEL:
Warning
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSendMsg, probe:30040
MESSAGE : TCP/IP send error. Closing HADR connection.
DATA #1 : Hexdump, 4 bytes
0x00002AAAC77F7C68 : 3D01 8087
=...

2017-11-21-20.02.25.182274+480 I304104E429           LEVEL:
Warning
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrResumeLogWriting, probe:10685
MESSAGE : Loggw not suspended, no resumption needed.

2017-11-21-20.02.25.201679+480 E304534E2331          LEVEL:
Severe (OS)
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::releaseConflict, probe:330
MESSAGE :
ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
          "expected latch to be held."
CALLED  : OS, -, unspecified_system_function
DATA #1 : String, 39 bytes
Attempting to unlock an invalid latch:
DATA #2 : File name, 16 bytes
sqloLatchCAS64.C
DATA #3 : Source file line number, 8 bytes
1055
DATA #4 : Codepath, 8 bytes
2
DATA #5 : String, 125 bytes
0x0000000000000000: {
   held X: 0
   reserved for X: 0
   shared holders: 0
   firstSharIndex: 0x0
   firstExclIndex: 0x0
}
DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes
0x0 (invalid mode)
DATA #7 : String, 399 bytes
{
   state         = 0x0000000000000000
                 = {
                       held X: 0
                       reserved for X: 0
                       shared holders: 0
                       firstSharIndex: 0x0
                       firstExclIndex: 0x0
                   }
   starve X mode = false
   xWaitCount    = 0
   requestCount  = 0
   identity      = preventSuspendIOLotch (827)
}
DATA #8 : Pointer, 8 bytes
0x00000002025e7c28
DATA #9 : Hexdump, 16 bytes
0x00000002025E7C28 : 0000 0000 0000 0000 3B83 0000 0000 0000
........;.......
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00002AAAB100137D
_ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKcjmmlmiS1_mi +
0x2AD
  [1] 0x00002AAAB2059976
_ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x3B6
  [2] 0x00002AAAABF3519C
_ZN14sqeSuspendIOCB28ReleasePreventSuspendIOLotchEv + 0x12C
  [3] 0x00002AAAAFA250F1
_ZN8HDR_DBCB25hdrUnblockSetWriteSuspendEP9sqeBsuEdu + 0x41
  [4] 0x00002AAAAFA41636 _ZN6hdrEdu7hdrEduPEbPm + 0x4386
  [5] 0x00002AAAAFA4755C _ZN6hdrEdu11hdrEduEntryEv + 0xDDC
  [6] 0x00002AAAAFA4BAA7 _ZN6hdrEdu6RunEDUEv + 0x27
  [7] 0x00002AAAAF879227 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
  [8] 0x00002AAAAF0318C3 sqloEDUEntry + 0x303
  [9] 0x00002AAAAACD6DC5 /lib64/libpthread.so.0 + 0x7DC5
  [10] 0x00002AAAB74A4CED clone + 0x6D
Problem Summary:
db2diag.log shows:

2017-11-21-20.02.25.180837+480 I301643E505           LEVEL:
Error
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSendBuffer, probe:20000
MESSAGE : Error sending data: errno
DATA #1 : Hexdump, 8 bytes
0x00002AAAC77F7BB8 : 2000 0000 0000 0000
.......

2017-11-21-20.02.25.181021+480 I302149E517           LEVEL:
Warning
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrSendMsg, probe:30040
MESSAGE : TCP/IP send error. Closing HADR connection.
DATA #1 : Hexdump, 4 bytes
0x00002AAAC77F7C68 : 3D01 8087
=...

2017-11-21-20.02.25.182274+480 I304104E429           LEVEL:
Warning
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrResumeLogWriting, probe:10685
MESSAGE : Loggw not suspended, no resumption needed.

2017-11-21-20.02.25.201679+480 E304534E2331          LEVEL:
Severe (OS)
PID     : 4533                 TID : 46912979855104  PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000            DB   :
SAMPLE
HOSTNAME: machine1
EDUID   : 50750                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::releaseConflict, probe:330
MESSAGE :
ZRC=0x870F011E=-2029059810=SQLO_LATCH_ERROR_EXPECTED_HELD
          "expected latch to be held."
CALLED  : OS, -, unspecified_system_function
DATA #1 : String, 39 bytes
Attempting to unlock an invalid latch:
DATA #2 : File name, 16 bytes
sqloLatchCAS64.C
DATA #3 : Source file line number, 8 bytes
1055
DATA #4 : Codepath, 8 bytes
2
DATA #5 : String, 125 bytes
0x0000000000000000: {
   held X: 0
   reserved for X: 0
   shared holders: 0
   firstSharIndex: 0x0
   firstExclIndex: 0x0
}
DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes
0x0 (invalid mode)
DATA #7 : String, 399 bytes
{
   state         = 0x0000000000000000
                 = {
                       held X: 0
                       reserved for X: 0
                       shared holders: 0
                       firstSharIndex: 0x0
                       firstExclIndex: 0x0
                   }
   starve X mode = false
   xWaitCount    = 0
   requestCount  = 0
   identity      = preventSuspendIOLotch (827)
}
DATA #8 : Pointer, 8 bytes
0x00000002025e7c28
DATA #9 : Hexdump, 16 bytes
0x00000002025E7C28 : 0000 0000 0000 0000 3B83 0000 0000 0000
........;.......
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
  [0] 0x00002AAAB100137D
_ZNK17SQLO_SLATCH_CAS6420dumpDiagInfoAndPanicEPKcjmmlmiS1_mi +
0x2AD
  [1] 0x00002AAAB2059976
_ZN17SQLO_SLATCH_CAS6415releaseConflictEv + 0x3B6
  [2] 0x00002AAAABF3519C
_ZN14sqeSuspendIOCB28ReleasePreventSuspendIOLotchEv + 0x12C
  [3] 0x00002AAAAFA250F1
_ZN8HDR_DBCB25hdrUnblockSetWriteSuspendEP9sqeBsuEdu + 0x41
  [4] 0x00002AAAAFA41636 _ZN6hdrEdu7hdrEduPEbPm + 0x4386
  [5] 0x00002AAAAFA4755C _ZN6hdrEdu11hdrEduEntryEv + 0xDDC
  [6] 0x00002AAAAFA4BAA7 _ZN6hdrEdu6RunEDUEv + 0x27
  [7] 0x00002AAAAF879227 _ZN9sqzEDUObj9EDUDriverEv + 0xF7
  [8] 0x00002AAAAF0318C3 sqloEDUEntry + 0x303
  [9] 0x00002AAAAACD6DC5 /lib64/libpthread.so.0 + 0x7DC5
  [10] 0x00002AAAB74A4CED clone + 0x6D

Problem first fixed in Db2 10.5 Fix Pack 9
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.11.2017
29.11.2017
29.11.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)