RPLDAP_EXTRACT_IDM - HCM to VDS LDAP error

[Former Member]

Hi IDM experts,

When trying to extract the data from HCM to VDS, we have followed the steps as per the guide, but when running the "RPLDAP_EXTRACT_IDM" program, we get the following errors when looking at the "SPLDAP_DISPLAY_LOG_TABLES" report:

Could not logon to directory - Message no. LDAPRC049
No data found for field P0000-PERNR of structure P0000

The "no data found for field P0000-PERNR" error, we are researching on our end with the related data team, but the strange error that it isn't able to logon to the directory, even though I can see it logon and authenticate successfully within the VDS operational logs, and then it prematurely ends, with these messages:

"Unbind request received on engine id=1"

"VDS ends the LDAP session"

"LDAP Message handler for session id=6: Closing"

"LDAP Connection: Closed 5184"

Prior to reaching this point, we have tested our LDAP connector along with our newly created LDAP server within the "LDAP" TCODE, and also using a newly created "System User" ("hruser" that matched with the VDS "Authenticated User" we have created when initially setting up the "HCM - LDAP extract for IDM" configuration within VDS, and we were able to successfully logon within the "LDAP" TCODE; however when trying to just to do a basic search after logging on in the TCODE, we get the following error logged within the VDS operational log:

"SQLException: Cannot open database "SQLDB01" requested by the login. The login failed."

"Could not create a connection"

This error used to show up when trying to execute the "RPLDAP_EXTRACT_IDM" program, but this doesn't happen anymore; but this error occurring for a simple LDAP "find" operation, definitely points to bigger errors, when trying to do the HCM EXTRACT; so I believe fixing this error, should get rid of the other errors upstream. It doesn't make sense why we should be getting a "Cannot open database" error, because the database connection string was created with valid "mxmc_rt" credentials when initially setting up VDS, so ideally it should be able to "open the database".

Here are the only things I can think of that could be wrong:

1. Does a DB login need to be created for the "System User" used within ECC LDAP connector - "hruser", so that it can open the database "SQLDB01"?
2. Does anything have to be set up within the VDS "Database properties", such as "Data source attributes" to match the data being sent from ECC?
3. Right now, the USER ID for the created "System User" is "HRUSER" and the distinguished name for the same entry is "hruser", as it matches the same "Authenticated User" created within the VDS config; is this right? Or does it have to be something else based on the error LDAPRC049?

Is there anything else, blatantly obvious that I might be overlooking?

Would greatly appreciate your insight / advice on the issue!

Thanks a ton in advance!

Best regards,
Sandeep

[Former Member · Accepted solution]

Fixed it. The DB Server name in VDS was wrong, and in trying to create the attribute mapping between TCODE: "LDAP" and TCODE: "HRLDAP_MAP", to be EXACTLY THE SAME, the LDAP attribute server mapping (TCODE: "LDAP") needed an additional a CN "Employee" Key field.