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 IT38383 Status: Closed

DB2 ABENDS WHILE PAGE CLEANER EXECUTING SQLBCLNRGATHERFORHATETHRESH

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A page cleaner EDU will print a message similar to the following
message in db2diag.log:

2021-06-28-16.17.02.827743+000 E11207E1830          LEVEL:
Severe (OS)
PID     : 5298                 TID : 70364323311968 PROC :
db2sysc 0
INSTANCE: db2inst1             NODE : 000           DB   :
HOSTNAME:
EDUID   : 439                  EDUNAME: db2pclnr () 0
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::getConflictComplex, probe:210
MESSAGE :
ZRC=0x870F00FE=-2029059842=SQLO_SLATCH_ERROR_HELDS_WITH_SHARED_W
AITER_NO_XWAITER
          "latch with no X starvation policy: when held shared
and a shared water, there should always be an X waiter."
CALLED  : OS, -, unspecified_system_function

The trap file for this page cleaner will have a stack trace
similar to the following:
sqle_panic
SQLO_SLATCH_CAS64::dumpDiagInfoAndPanic
SQLO_SLATCH_CAS64::getConflictComplex
SQLO_SLATCH_CAS64::getConflict
sqlbClnrGatherForHateThresh
sqlbClnrGatherPages
sqlbClnrEntryPoint

If a core file is present the address of the
SQLB_HASH_BUCKET_GROUP structure in the db2diag.log message can
be compared with the starting address of the bucketGroupArray in
the core file. This is a match for this APAR if the address of
the SQLB_HASH_BUCKET_GROUP structure in the db2diag.log message
is before the starting address of the bucketGroupArray. Note
that the address in the db2diag.log must be 1 to 3
SQLB_HASH_BUCKET_GROUP sized structures prior to the start of
the bucketGroupArray indicating a bucketGroupArray index of
-1,-2, or -3 has been used.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All users.                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1.4.7                                          *
****************************************************************
Local Fix:
Set DB2_USE_ALTERNATE_PAGE_CLEANING=FALSE or install the latest
fix pack.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All users.                                                   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1.4.7                                          *
****************************************************************
Comment
Upgrade to 11.1.4.7
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2021
17.04.2022
17.04.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)