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

"DB2CLUSTER -CM -ENTER -MAINTENANCE" COMMAND FAILS IF RUN ON A TIEBREAKER
HOST IN GDPC ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In a GDPC pureScale environment, the following error may be
encountered when attempting to enter maintenance mode on the
tiebreaker host:

$ /opt/IBM/DB2/V11.1.3/bin/db2cluster -cm -enter -maintenance
DBT8066E Unable to enter maintenance mode on host "TBhostA".
Reason code = "3".
A diagnostic log has been saved to
'/tmp/ibm.db2.cluster.qyFz13s.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* pureScale GDPC users                                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 version 11.1 Mod pack 4 Fix pack 4            *
****************************************************************
Local Fix:
In order to workaround this issue, RSCT can be stopped via
native RSCT commands, e.g. the "stoprpnode TBhostA" command can
be used to stop RSCT on the tiebreaker host. In order to then
exit maintenance mode, RSCT can be started back up on the host
via the "startrpnode TBhostA" command. Note that the startrpnode
command must be issued from another host in the cluster.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.07.2018
03.12.2018
03.12.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)