IBM Security directory server 6.4 and db2 11.1, if you have issue creating istance .. read this post

IBM Security Directory server 6.4 with FP16 , released at the end of 2018,  has added support of db2 11.1 that's is an awesome news for IBM Connections customers because this match the same db2 version of Connections server .

Some  days ago this product has reached the FP18.


Here at this page , IBM has published the step by step guide to install and configure SDS 6.4 with this db2 release, but at point 9 there is an error that will probably points you to receive an error during the instance creation.

 In this step , admin have to check the file 

 ldapdb.properties

usually available inside the following path

• AIX: /opt/IBM/ldap/V6.4/etc/ldapdb.properties
• Linux: /opt/ibm/ldap/V6.4/etc/ldapdb.properties
• Windows: <SDS_V6.4_Install_Location>\etc\ldapdb.properties

updating /creating the following lines inside the file


currentDB2InstallPath=/opt/ibm/db2/V11.1
currentDB2Version=11.1.3.3 



I've followed this instruction and I've received an error due invalid db2 version while I was creating the ldap instance.


After a quick check of the same file I've edited the file as below

 #configfile
 currentDB2Version=11.1.3.3
 currentDB2InstallPath=/opt/ibm/db2/V11.1


and than I was able to create the instance successfully !
Pay attention of the whole lines and their order..

IBM Security Directory Suite 8.0.1 , how to be able to "press any key to continue" using the vmware appliance

In this days I'm working in a project that include  IBM Security Directory Suite 8.0.1.6.
IBM SDS 8.0.1 is distribuited as appliance, and after a reboot at the end of configuration I've got the VM hanging at the following state

where I wasn't able to continue ( and I know where is the "any key "  )  ..
I've started some investigaton that has pointed me on this old grub issue with the following description : "centos 6 grub 'press any key to continue' takes a long time if no serial device attached" .

I've shut down the appliance , added the serial port and at the new start the issue was fixed and i was able to press the key to continue!