DB2 - Problem description
Problem IT35828 | Status: Closed |
"DB2CLUSTER | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The "db2cluster -cfs -set -option ccrEnabled -value no" command will not complete within 22 minutes and times out. $ db2cluster -cfs -set -option ccrEnabled -value no The db2cluster command has timed out and is now terminating. When completed successfully, the "db2cluster -cfs -set -option ccrEnabled -value no" command should disable Spectrum Scale Cluster Configuration Repository (CCR). However, after the db2cluster command times out, "db2cluster -cfs -list -configuration" command will still show "ccrEnabled yes". $ db2cluster -cfs -list -configuration OPTION VALUE ------------------------------ --------------------------------- ccrEnabled yes | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Local Fix: | |
Run "/usr/lpp/mmfs/bin/mmchcluster --ccr-disable" command as root instead of "db2cluster -cfs -set -option ccrEnabled -value no" to disable the CCR feature. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5.6 or later * **************************************************************** | |
Comment | |
Upgrade to 11.5.6 or later | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.02.2021 21.06.2021 21.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |