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

DB2 STANDBY CRASH ON SQLOGETMEMPOOLSTATSUNLATCHED WHEN DB2_HADR_ROS IS
ENABLED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A DB2 HADR standby might crash if a Snapshot is run and
DB2_HADR_ROS  is enabled.
The stack will show the following functions:

0 ossDumpStackTraceInternal

1 ossDumpStackTraceV98

2 OSSTrapFile::dumpEx

3 sqlo_trce

4 sqloEDUCodeTrapHandler

5 __PRETTY_FUNCTION__.6036

6 sqloGetMemPoolStatsUnlatched

7 sqlmindb

8 sqm_snap_dbase

9 sqlmonssagnt

10 sqlmonssbackend

11 sqlesrvr

12 sqleMappingFnServer

13 sqlerKnownProcedure

14 sqlerCallDL

15 sqljs_ddm_excsqlstt

16 sqljsParseRdbAccessed

17 sqljsParse

18 sqljsSqlam

19 sqljsDrdaAsInnerDriver

20 sqljsDrdaAsDriver

21 sqeAgent::RunEDU

22 sqzEDUObj::EDUDriver

23 sqloEDUEntry

24 pthread_attr_setinheritsched

25 clone
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Use this registry to force db latch over database snapshot and
other snapshots that report memory usage:
db2set db2_system_monitor_settings=nodblatch:none
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.06.2018
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)