DB2 - Problem description
| Problem IC90232 | Status: Closed |
THE 'DB2CLUSTER -CM -CREATE -DOMAIN' COMMAND FAILS DUE TO INCORRECT PERMISSIONS ON THE LIBDB2GPFS.SO FILE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
When creating a cluster manager domain via the 'db2cluster -cm
-create -domain <name> -host <hostname>' command, the following
error is seen:
$ ./db2cluster -cm -create -domain ha_dom -host host01
Creating domain 'ha_dom' in the cluster ...
There was an internal db2cluster error. Refer to the diagnostic
logs (db2diag.log or /tmp/ibm.db2.cluster.*) and the DB2
Information Center for details.
A diagnostic log has been saved to '/tmp/ibm.db2.cluster.*'.
In addition to this, the following error message is seen in the
generated '/tmp/ibm.db2.cluster.*' file:
2012-07-25-13.43.53.432742-240 I18000E642 LEVEL:
Severe
PID : 40666 TID : 139808626722592 PROC :
db2cluster
INSTANCE: NODE : 000
HOSTNAME: host01
FUNCTION: DB2 UDB, high avail services,
sqlhaCFSSetupInfrastructure, probe:86
MESSAGE :
ECF=0x900004F0=-1879046928=ECF_FILE_INCORRECT_PERMISSIONS
File does not have correct permissions
DATA #1 : String, 184 bytes
The Cluster File System is not initialized because the shared
library ownership is incorrect. User and group ownership of that
file should be root or bin and it should not be writable.
DATA #2 : String, 45 bytes
/opt/IBM/db2/V10.1/lib64/libdb2gpfs.so
DATA #3 : ZRC, PD_TYPE_ZRC, 4 bytes
0x00000000
DATA #4 : SQLHA CFS Control Block,
PD_TYPE_SQLHA_CFS_CONTROL_BLOCK, 656 bytes
timeout: 0
runmode: PASS_THRU_MODE
administrator
Without this APAR fix, the group id(gid) ownership of the file
must be either root(id=0) or bin. Any other value for the gid
will cause the command to fail. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 pureScale users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10.1 FP3 * **************************************************************** | |
| Local Fix: | |
Ensure that the files uid and gid are set to either bin or zero and that it is not 'other' writeable. | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Fixed in DB2 V10.1 FP3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.02.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 |
|