DB2 - Problem description
Problem IT36894 | Status: Closed |
"TOO MANY ARGUMENTS" MESSAGE WHEN RUNNING DB2CM | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
An error may be observed when running the db2cm command under a HADR with Pacemaker environment, with multiple standby setup: [root@host1 ~]# ./db2cm -create -db coral -instance db2inst1 ./db2cm: line 1071: [: too many arguments Database resource for CORAL created successfully. This error is caused by incorrect parsing of db2pd multiple peer_window values from auxiliary standbys. However as long as the user sees "Database resource for CORAL created successfully." as a result of this command, the error has no effect on the functionality. Users can safely assume that the db resource was created successfully. The false error message will be removed in the next mod pack | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * HADR with Pacemaker * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V11.5.6.0 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * HADR with Pacemaker * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V11.5.6.0 * **************************************************************** | |
Comment | |
In Db2 V11.5.6.0, the customer would no longer see the too many arguments error when creating db resource. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.05.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) |