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.

windows error 2 occur while loading the java vm" during ADT (adaptr development tool installation)

I  face this below error during adapter development tool installation on window 7 OS.

Error:- windows error 2 occur while loading the java vm" during ADT (adaptr development tool installation



I had fixed this issue and below are the solution steps.

Steps: - 1. install the installer from the below command because that will specify the java jre path

ADT5124_ITIM51_TDI71x.exe LAX_VM "C:\Program Files (x86)\Java\jre1.8.0_101\bin\java.exe

CTGIMD803E The protocol portion of the Host URL field value is not valid

ISIM Service profile connection is not established with Manage resource SQL Database and I got this error CTGIMD803E  The protocol portion of the Host URL field value is not valid from ISIM service profile.

My Environment details:-


Connecting ISIM with SQL Server 2012, so i completed these steps:

1 ) SQL Server adapter installed on window-7. already SQL Server 2012 present on the machine.

2 ) SQL Profile is imported successfully. in ISIM

So I found the solution for this that I was using wrong URL field like (URL: jdbc:sqlserver://machineIP:1433;databaseName=dbname) in service profile which was wrong.
so i used correct URL like ( https://targetapplicationIP:45580).
after that I able to connect with target SQL application and my issue resolved.

where : 45580 --  it is sql adapter port

Tunning Tivoli Identity Manager

Tunning Tivoli Identity Manager

1 Configuring LDAP connection pooling in enRole.properties
2 Configuring list controls in ui.properties
3 Configuring Configuring report data synchronization in adhocreporting.properties file
4 Configuring the commitFrequency property in adhocreporting.properties file
5 Configuring Java™ heap size while running the report data
6 synchronization utility on OS.
7 Configuring report batch sizes in adhocreporting.properties file
8 Configuring email notifications from ITIM GUI
9 Disabling the recycle bin
10 Emptying the recycle bin
11 Configuring reconciliation threads
12 Configuring the maximum duration of a reconciliation
13 Configuring paged searches in enRole.properties file
14 disabling server-side sorting in enRole.properties file
15 Configuring the ACI cache in in enRole.properties file
16 Controlling the size of the database
 



   

Tunning RMI Dispatcher

Tunning RMI Dispatcher:-

1 ) Configuring timeouts for large reconciliations
Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update the following option:
SearchALUnusedTimeout=searchal_timeout
c. Restart the RMI Dispatcher for this change to take effect.


2 ) Configuring assembly line caching

Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update or add the following option:
   ALCacheSize=num_cached_ALs
c. Restart the RMI Dispatcher for this change to take effect.


3 ) Configuring the number of concurrently running assembly lines
Steps
a. Stop the RMI Dispatcher.
b. In itdi_home/itim_listener.properties, update the following configuration options:
GlobalRunALCount=max_running_ALs
MaxWaitingALcount=max_waiting_ALs
c. Restart the RMI Dispatcher for this change to take effect.


Happy sharing...!!