Reading a View in SAP IDM: 7.2

[Former Member]

  HI experts,

I'm needing to read a view in legacy system for database of IDM.

this View are in other server, out of IDM, then created in IDM a Repositorio Database.

Follows the print:

and set up a pass FROM DATABASE:

when i run this error appears

how to test the connection I used Sql Developer, and configured with the same data connection and User configured in the IDM repository, and it worked.

Someone knows how to solve?

Tks

[Former Member · Accepted solution]

Hello Gustavo,

in the screenshot I can see you use the identitycenter variable in the source tab. This should be the connection string to the database.

In addition it could also be necessary to add the full name including the database like otherdatabase.idm.idm_funcionar.

Best regards

Dominik

[Former Member · Accepted solution]

Hi Dominik,

I tried to set the string and it did not work, also added the name of the data base and also did not work apl.idm.idm_funcionar

Tks

[Former Member · Accepted solution]

Did you configure the tnsnames.ora for the apl database?

Do you know whether there is a firewall inbetween both servers? Sometimes even the virus scanner was the reason for connection problems.

[Former Member · Accepted solution]

Hi Domink,

I found a mistake in my connection string, fix and managed to make one load.

Today when I redo the load returned me this error, have any idea of what can be?

addEntry failed

java.sql.SQLException: Missing IN or OUT parameter at index:: 24

[former_member2987 · Accepted solution]

the %ddm.identitycenter% is valid and maps to the connection string to the IDM database.

[former_member2987 · Accepted solution]

Gustavo,

Did you specify the right java drivers? Also are you using any scripts?

Matt

[Former Member · Accepted solution]

Hi Gustavo,

Did you upgrade the database in between ? Did you set the JAVA_HOME & PATH correctly with appropriate path to oracle jdbc driver?

Can you try to set the java_home & path once again and try this.

As Matt mentioned, usually such problems occur when there is mismatch between the database version and oracle jdbc drivers.

All the best.

Thanks,

Krishna.