DB2 - Problem description
Problem IC89692 | Status: Closed |
SMALL LETTER <DBNAME> DOES NOT WORK IN "DB2CLUSTER -CM -ADD -DATABASE_MOUNTS <DBNAME>" COMMAND. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If database name TESTDB exists and run "db2cluster -cm -add -database_mounts testdb", small letter database name, will not add the mounts. But if you run "db2cluster -cm -add -database_mounts TESTDB", adds the mounts. Here is an example: $ db2cluster -cm -add -database_mounts testdb $ db2hareg -dump IN,100,2,1 DN,coral19,,- NL,128,coral19,0,-,-,CF NL,129,coral19,0,-,-,CF NL,0,coral19,0,-,-,MEMBER NL,1,coral19,1,-,-,MEMBER NL,2,coral19,2,-,-,MEMBER DB,TESTDB,1 $ db2cluster -cm -add -database_mounts TESTDB $ db2hareg -dump IN,100,2,1 DN,coral19,,- NL,128,coral19,0,-,-,CF NL,129,coral19,0,-,-,CF NL,0,coral19,0,-,-,MEMBER NL,1,coral19,1,-,-,MEMBER NL,2,coral19,2,-,-,MEMBER DB,TESTDB,1 MO,/gpfs/gpfs_data,TESTDB,0,11,0 As above, "db2hareg -dump" lists added the mounts when use capital letter in <dbname> as: --- MO,/gpfs/gpfs_data,TESTDB,0,11,0 --- | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 10.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 FixPack 3. * **************************************************************** | |
Local Fix: | |
Specify all capital letter in <dbname> for "db2cluster -cm -add -database_mounts <dbname>" command. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 01.10.2013 01.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |