Wednesday 15 February 2017

HPDRG0201E Error code 0x31 was received from the LDAP server. Error text: "Invalid credentials".

HPDRG0201E   Error code 0x31 was received from the LDAP server. Error text: "Invalid credentials".

 Solution:  I faced this error during IBM Security access manager packages configuration.
                  found there was no "secAuthority=Default" suffix on the ldap.
                  so I have added this suffix on SAM ldap.

/opt/ibm/ldap/V6.0/sbin/idscfgsuf -I ldapdb2 -s secAuthority=Default
                      

IBM DB2 Enterperise Server Edition V9.7 not detected, install can not continue.

IBM DB2 Enterperise Server Edition V9.7 not detected, install can not continue.

error: %pre(idsldap-srv64bit63-6.3.0-0.x86_64) scripted failed, exit status 1
error: install: %pre scriptlet failed (2). skipping idsldap-srv64bit63-6.3.0.0


Description: - I faced this error when i was installing base TDS 6.3.0 version with DB2 10.1
                     
Solution: - TDS 6.3.0 does not support Db210.1 , Minimum it is required TDS level 6.3.0.21.



                

AM GLPRPL116E Replication for DN 'CN=ip:1389,CN=ip:1389,IBM-REPLICAGROUP=DEFAULT,OU=PORTAL,DC=COM' encountered a gap in the change IDs: 26 followed 24 after trying one more time but is continuing.

AM GLPRPL116E Replication for DN 'CN=ip:1389,CN=ip:1389,IBM-REPLICAGROUP=DEFAULT,OU=PORTAL,DC=COM'
encountered a gap in the change IDs: 26 followed 24 after trying one more time but is continuing.


 This error I faced when i was doing IBM TDS master- replica configuration in the environment.

Solution:- error occur because of encryption seed & salt values different on TDS servers

1 ) check the sync & salt value on both TDS server's from the below ldap command that should be the same.

ldapsearch -D <username> -w <passowrd> -h ip -p 1389 -s base -b cn=crypto,cn=localhost cn=*

if value are different, again recreated the instance and provide the same encryption seed otherwise replication will not work.