|
Problem IT31054
|
Status: Closed |
EVEN IF RESERVE_POLICY IS RECOMMENDED TO NO_RESERVE, DB2PREREQCHECK -TB_DEV NOT SUCCEED WITH "WARNING: REQUIREMENT NOT MATCHING"
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
The "single_path" and "PR_exclusive" are checked as SCSI type,
and db2prereqcheck command logged "The
value of rc is :-1 Invalid SCSI type configuration of the disk
on the host", after "no_reserve" is set in reserve_policy even
though it is recommended as below.
* Shared storage disk settings for Category 1 Storage Devices
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com
.ibm.db2.luw.qb.server.doc/doc/c0070187.html
Before creating a pureScale instance, it is recommended that the
disk RSCT peer domain attribute, reserve_policy, be set to
no_reserve. This recommendation applies to all supported shared
storage devices, device drivers, and disk types.
Once db2icrt is finished running and the Db2 pureScale instance
is created, some of these attributes are updated by RSCT peer
domain and IBM Spectrum Scale as they try to open the device in
the mode specified. ... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 pureScale user *
****************************************************************
* 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 :
| 24.11.2019
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) |
