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

EVEN IF RESERVE_POLICY IS SET TO PR_EXCLUSIVE, "DB2PREREQCHECK -TB_DEV"
NOT SUCCEED WITH "WARNING: REQUIREMENT NOT MATCHING"

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
Because "db2prereqcheck -tb_dev" command does not succeed with
"WARNING: Requirement not matching" due to APAR IT31054 during
RESERVE_POLICY is configured as "no_reserve" per the following
doc, "db2prereqcheck -tb_dev" command will be tried after
db2icrt and RESERVE_POLICY is configured as "PR_exclusive".

  However, if the "db2prereqcheck -tb_dev" command is attempted
after db2icrt and RESERVE_POLICY are configured as
"PR_exclusive", the db2prereqcheck -tb_dev command will not
succeed with "WARNING: Requirement not matching".
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* CM tiebreaker user on Db2 pureScale                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 11.5 FixPack 4 or later               *
****************************************************************
Local Fix:
Use tb_break tool to check CM tiebreaker for purescale per the
following link.

* tb_break tool to check CM tiebreaker for purescale

https://www.ibm.com/support/pages/tbbreak-tool-check-cm-tiebreak
er-purescale
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.01.2020
30.06.2020
30.06.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)