DB2 - Problem description
Problem IT30806 | Status: Closed |
DB2CLUSTER -CM -LIST -TIEBREAKER RETURNS INCORRECT OUTPUT WHEN THE DOMAIN IS STOPPED OR IN MAINTENANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The way we query CM domain tiebreaker is essentially by running "lsrsrc -c IBM.PeerNode OpQuorumTieBreaker" ?when domain is stopped or in maintenance, we can't query tiebreaker , the CM tiebreaker type is NOT actually being changed , so our command "db2cluster -cm -list -tiebreaker " didn't return the correct value .The problem can be reproduced via following ways : => ./db2cluster -cm -list -tiebreaker The current quorum device is of type Disk with the following specifics: *DEVICE=/dev/hdisk2*. => *./db2cluster -cm -enter -maintenance -all* Domain ?db2domain_20150922152232? has entered maintenance mode. => *./db2cluster -cm -list -tiebreaker* The current quorum device is of type *Majority Node Set*. =>lsrsrc -c IBM.PeerNode OpQuorumTieBreaker 2610-405 Cannot obtain values for 1 persistent attributes. => ./db2cluster -cm -exit -maintenance -all Domain ?db2domain_20150922152232? has successfully exited maintenance mode. => *./db2cluster -cm -list -tiebreaker* The current quorum device is of type Disk with the following specifics: *DEVICE=/dev/hdisk2*. => stoprpdomain -f db2domain_20150922152232 => lsrsrc -c IBM.PeerNode OpQuorumTieBreaker 2610-405 Cannot obtain values for 1 persistent attributes. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * pS env * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * it's display issue , no impact for the cluster * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT28983 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.10.2019 31.10.2019 31.10.2019 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |