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

DB2PREREQCHECK FOR PURESCALE MIGHT CRASH WITH SEGMENTATION FAULT(SEGV) IN
"VALIDATING TIE-BREAKER DISK INFO" SECTION.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
db2prereqcheck running with -tb_dev to verify tie-breaker device
for PureScale might crash with segmentation fault (SEGV) in
sqloValidateTbDisk function with the following messages printed
on the screen:

Validating "Tie-breaker disk info" ...
...
Segmentation fault


In system with core dumps enabled (ulimit -c unlimited), one
will see a backatrace similar to this one after loading the core
to the debugger (example for AIX):
$ dbx  

(dbx) where
unnamed block in sqloValidateTbDisk(), line 17275 in
"sqloPrereqCheck.c"
sqloValidateTbDisk(), line 17275 in "sqloPrereqCheck.c"
sqloCheckPrereqPureScale(), line 11627 in "sqloPrereqCheck.c"
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Skip db2prereqcheck and continue installation.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.07.2019
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)