GLPCTL019E Error Running idsicrt
While trying to configure an ITDS instance and database, I ran into the generic GLPCTL019E error. The only thing I know from this error message is that there was a failure and not much else. In hopes of finding more information, I reviewed the ibmslapd.log, db2cli.log, and the others, still finding no hints as to why this problem occurred.
Here is the command I ran and the failure.
idsicrt -I idsinst -e password4seed -p 389 -s 636 -a 3538 -c 3539 -l /home/idsinst -t idsinst
GLPICR020I A new directory server instance 'idsinst' will be created. GLPICR057I The directory server instance will be created at: '/home/idsinst'. GLPICR013I The directory server instance's port will be set to '389'. GLPICR014I The directory server instance's secure port will be set to '636'. GLPICR015I The directory instance's administration server port will be set to '3538'. GLPICR016I The directory instance's administration server secure port will be set to '3539'. GLPICR019I The description will be set to: 'IBM Tivoli Directory Server Instance V6.1'. GLPICR021I Database instance 'idsinst' will be configured. Do you want to.... (1) Continue with the above actions, or (2) Exit without making any changes:1 GLPICR028I Creating directory server instance: 'idsinst'. GLPICR025I Registering directory server instance: 'idsinst'. GLPICR026I Registered directory server instance: : 'idsinst'. GLPICR049I Creating directories for directory server instance: 'idsinst'. GLPICR050I Created directories for directory server instance: 'idsinst'. GLPICR043I Creating key stash files for directory server instance: 'idsinst'. GLPICR044I Created key stash files for directory server instance: 'idsinst'. GLPICR040I Creating configuration file for directory server instance: 'idsinst'. GLPICR041I Created configuration file for directory server instance: 'idsinst'. GLPICR034I Creating schema files for directory server instance: 'idsinst'. GLPICR035I Created schema files for directory server instance: 'idsinst'. GLPICR037I Creating log files for directory server instance: 'idsinst'. GLPICR038I Created log files for directory server instance: 'idsinst'. GLPICR088I Configuring log files for directory server instance: 'idsinst'. GLPICR089I Configured log files for directory server instance: 'idsinst'. GLPICR085I Configuring schema files for directory server instance: 'idsinst'. GLPICR086I Configured schema files for directory server instance: 'idsinst'. GLPICR073I Configuring ports and IP addresses for directory server instance: 'idsinst'. GLPICR074I Configured ports and IP addresses for directory server instance: 'idsinst'. GLPICR077I Configuring key stash files for directory server instance: 'idsinst'. GLPICR078I Configured key stash files for directory server instance: 'idsinst'. GLPICR046I Creating profile scripts for directory server instance: 'idsinst'. GLPICR047I Created profile scripts for directory server instance: 'idsinst'. GLPICR103I Adding instance information to the .profile file for directory server instance: 'idsinst'. GLPICR104I Added instance information to the .profile file for directory server instance: 'idsinst'. GLPICR069I Adding entry to /etc/inittab for the administration server for directory instance: 'idsinst'. GLPICR070I Added entry to /etc/inittab for the administration server for directory instance: 'idsinst'. GLPICR118I Creating runtime executable for directory server instance: 'idsinst'. GLPICR119I Created runtime executable for directory server instance: 'idsinst'. GLPCTL074I Starting admin daemon instance: 'idsinst'. GLPCTL075I Started admin daemon instance: 'idsinst'. GLPICR029I Created directory server instance: : 'idsinst'. GLPICR031I Adding database instance 'idsinst' to directory server instance: 'idsinst'. GLPCTL017I Cataloging database instance node: 'idsinst'. GLPCTL019E Failed to catalog database instance node: 'idsinst'. The failure might have occurred because the system was not set up correctly before using the tool. GLPICR033E Failed to add database instance 'idsinst' to directory server instance: 'idsinst'. GLPIDP002I Deleting directory server instance: 'idsinst'. GLPCTL077I Stopping admin daemon instance: 'idsinst'. GLPCTL078I Stopped admin daemon instance: 'idsinst'. GLPIDP072I Deleting the runtime executable for directory server instance: 'idsinst'. GLPIDP073I Deleted the runtime executable for directory server instance: 'idsinst'. GLPIDP035I Removing entry from /etc/inittab for Admin Daemon Instance: 'idsinst'. GLPIDP036I Removed entry from /etc/inittab for Admin Daemon Instance: 'idsinst'. GLPIDP057I Removing instance information from the .profile file for directory server instance: 'idsinst'. GLPIDP058I Removed instance information from the .profile file for directory server instance: 'idsinst'. GLPIDP020I Deleting profile scripts for directory server instance: 'idsinst'. GLPIDP021I Deleted profile scripts for directory server instance: 'idsinst'. GLPIDP011I Deleting log files for directory server instance: 'idsinst'. GLPIDP012I Deleted log files for directory server instance: 'idsinst'. GLPIDP008I Deleting schema files for directory server instance: 'idsinst'. GLPIDP009I Deleted schema files for directory server instance: 'idsinst'. GLPIDP014I Deleting configuration file for directory server instance: 'idsinst'. GLPIDP015I Deleted configuration file for directory server instance: 'idsinst'. GLPIDP017I Deleting key stash files for directory server instance: 'idsinst'. GLPIDP018I Deleted key stash files for directory server instance: 'idsinst'. GLPIDP077I Deleting the ldapdb.properties file for directory server instance: 'idsinst'. GLPIDP075I Deleted the ldapdb.properties file for directory server instance: 'idsinst'. GLPIDP023I Deleting directories for directory server instance: 'idsinst'. GLPIDP024I Deleted directories for directory server instance: 'idsinst'. GLPIDP039I Unregistering directory server instance: 'idsinst'. GLPIDP040I Unregistered directory server instance: 'idsinst'. GLPIDP003I Deleted directory server instance: : 'idsinst'. GLPICR024W The program did not complete successfully. View earlier error messages for information about the exact error.
In order to get more information about the real cause of the failure, I would need to run an ASCII trace of the idsicrt. This will allow me to see the processes interaction with the operating system. In these interactions I should be able to see which step is failing and a more details error message.
Running an ASCII trace
1. Prior to running the idsicrt debug, I need to enable ldtrc. This is what turns on tracing for the processes.
ldtrc on
2. Now I need to recreate the error. I re-run the idsicrt with the -d and -b flags.
idsicrt -I idsinst -e password4seed -p 389 -s 636 -a 3538 -c 3539 -l /home/idsinst -t idsinst -d 65535 -b /tmp/idsicrt.out
The -d 65535 turns on the debug and will provide me the most detailed information about the error.
The -b /tmp/idsicrt.out is telling the command where I want the detailed output written to. In this case I’m writing the log to /tmp/idsicrt.out.
3. Turn off tracing
ldtrc off
Note: Not turning this off can cause problems with the operation of your ldap server.
Reviewing the Trace Output
Reviewing the trace file for the first time can be overwhelming, as it contains a lot of information. What I would suggest is searching the file for the error message. In my case the error message is ‘GLPCTL019E Failed to catalog database instance node: ‘idsinst’. The failure might have occurred because the system was not set up correctly before using the tool.’ After locating the error, work your way up in the trace. The cause of the failure should be close by.
In my case, the real error message is only 10 lines above the generic message.
GLPCTL017I Cataloging database instance node: 'idsinst'. 053:19:41:42 T1 K12718279 vPrintMessage: catid=29, level=1, num=17. 053:19:41:42 T1 K12718279 do_iconv_open: local_codepage=NULL 053:19:41:42 T1 K12718279 xlate_utf8_to_localcp: inlen=8 053:19:41:42 T1 K12718279 xlate_utf8_to_localcp: rc=0 053:19:41:42 T1 K12718279 checkSQLStatus: sclca->sqlcode=-1092 buff=[SQL1092N "ROOT " does not have the authority to perform the requested command. ] 053:19:41:42 T1 K12718279 catalogInstanceNode: sqlectnd() failed with rc=0 and sqlca.sqlcode=-1092. 053:19:41:42 T1 K12718279 ldap_getenv: LDAP_DEBUG_TIME=NULL 053:19:41:42 T1 K12718279 vPrintMessage: catid=29, level=1, num=19. 053:19:41:42 T1 K12718279 getmessage: msgnum=19 catid=29 053:19:41:42 T1 K12718279 getmessage: msgnum=19, catid=29, catalog_only=TRUE 053:19:41:42 T1 K12718279 do_iconv_open: local_codepage=NULL 053:19:41:42 T1 K12718279 xlate_utf8_to_localcp: inlen=8 053:19:41:42 T1 K12718279 xlate_utf8_to_localcp: rc=0 GLPCTL019E Failed to catalog database instance node: 'idsinst'. The failure might have occurred because the system was not set up correctly before using the tool.
Now, I have a error message that points me in a better direction. I can see from the SQL1092N that their is a permission problem somewhere.
Reviewing the documentation for IBM Tivoli Directory Server 6.1, I find that the ‘root’ user is required to be a member of the SYSADM group for the DB2 instance. This is because of the way the idsicrt and idsxinst tools create the DB2 instance.
After I added the root user to the SYSADM group for the instance the idsicrt successfully create my instance. From that point I was able to continue configuring the ITDS environment I was setting up.
Leave a Reply
Additional comments powered by BackType



