The idscfgdb command fails to configure a database

Edit online

The idscfgdb command might fail to configure a database for a directory server instance on Red Hat Enterprise Linux™ (RHEL) v4, 64-bit operating system. You can update the kernel parameter to resolve this problem.

When you configure a database for a directory server instance by using the idscfgdb command on RHEL 4 64-bit operating system, the tool might exit with the following error messages:

GLPCTL026I Creating database: 'mydata'.
GLPCTL028E Failed to create database: 'mydata'. The failure might 
have occurred because the system was not set up correctly before using the tool.
GLPCTL011I Stopping database manager for the database instance: 'mydata'.
GLPCTL012I Stopped database manager for the database instance: 'mydata'.
GLPCDB004E Failed to add database 'mydata' to directory server instance: 
'mydata'.
GLPCDB026W The program did not complete successfully. View earlier error messages 
for information about the exact error.

In this situation, the db2diag.log file might contain the following information:

2008-03-20-11.33.32.471455+330 I5410E982LEVEL: Error
PID: 3214TID: 182960860768 PROC : db2fm
INSTANCE: mydataNODE : 000
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:30
MESSAGE : ECF=0x9000036D=-1879047315=ECF_FM_DB2FMD_PROCESS_NOT_EXIST
There is no fault monitor daemon running
CALLED: OS, -, open
RETCODE : ECF=0x9000001A=-1879048166=ECF_FILE_DOESNT_EXIST
File doesn't exist
CALLSTCK:
[0] 0x0000002A956FF982 /opt/ibm/db2/V10.5/lib64/libdb2osse.so.1 + 0x1A7982
[1] 0x0000002A956FF82F ossLogRC + 0x6B
[2] 0x0000002A9BCBDB01 gcf_stop + 0x42B
[3] 0x0000002A95DB9559 _ZN9GcfCaller4stopEP12GCF_PartInfomP11GCF_RetInfo + 0x105
[4] 0x0000000000405708 main + 0x17F0
[5] 0x0000003049D1C3FB __libc_start_main + 0xDB
[6] 0x0000000000403E7A __gxx_personality_v0 + 0x9A
[7] 0x0000000000000000 ?unknown + 0x0
[8] 0x0000000000000000 ?unknown + 0x0
[9] 0x0000000000000000 ?unknown + 0x0


2008-03-20-11.33.32.472141+330 I6393E948LEVEL: Error
PID: 3214TID: 182960860768 PROC : db2fm
INSTANCE: mydataNODE : 000
FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:170
MESSAGE : ECF=0x90000349=-1879047351=ECF_FM_FAIL_TO_STOP_GCF_FM
Failed to stop the GCF fm module
CALLED: DB2 Common, Generic Control Facility, GcfCaller::stop
DATA #1 : signed integer, 8 bytes
0
DATA #2 : unsigned integer, 8 bytes
1CALLSTCK:
[0] 0x0000002A956FF982 /opt/ibm/db2/V10.5/lib64/libdb2osse.so.1 + 0x1A7982
[1] 0x0000002A956FF883 ossLogRC + 0xBF
[2] 0x0000000000405772 main + 0x185A
[3] 0x0000003049D1C3FB __libc_start_main + 0xDB
[4] 0x0000000000403E7A __gxx_personality_v0 + 0x9A
[5] 0x0000000000000000 ?unknown + 0x0
[6] 0x0000000000000000 ?unknown + 0x0
[7] 0x0000000000000000 ?unknown + 0x0
[8] 0x0000000000000000 ?unknown + 0x0
[9] 0x0000000000000000 ?unknown + 0x0

To resolve this problem:

Update the kernel parameter, kernel.shmmax. For example:
```
kernel.shmmax = 3221225472
```
Run the idscfgdb tool again.