Issue with JDBC connector in AS400 - SQL0204

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hello,

I have a JDBC source to connect with AS400 database. Also, I have created a provisioning rule linked to a custom connector as Sailpoint recommend in order to launch all the source operations.

I have configured the create method to call a store procedure in AS400:

QUERY_CREATE_ACCOUNT= "{call SCHEMA.PROCEDURE (?, ?,…

When I launch the user creation, the procedure is called correctly and I have a good response in our output parameters, also, I can see how the java connector finish with the “return result;” without any issues or exceptions.

The issue comes when I come back to IdentityNow to see the task result and see how the task failed with the error "SQL0204 - ACCOUNT in USER type *FILE not found ". The USER is the user that I have configured in the source form but I don’t specified “ACCOUNT” in any code or configuration… It seems like IdentityNow is triying to call a new procedure (USER.ACCOUNT) or table ACCOUNT after my successful connector result.

I tried to add the param naming=system; but I have the “same” error "SQL0204 - ACCOUNT in *LIBL type *FILE not found ". The ACCOUNT table doesn’t exist in the database, and IDN shouldn’t call it.

I don’t know what I need to do to end my successful request with my “return result” and avoid this second IDN call.

Thank you in advance!

2

Hey @senjutok, thanks for posting this and welcome to the community! We will look into this for you here shortly and provide feedback.

3

Hey @senjutok, I think the issue may be related to the jdbc driver. Let’s try this: instead of having naming=system can you try to use naming=1 instead? Let us know if this resolves your issue.

I hope this helps!

4

Hello and thank you for you early response!

I have tried with naming=1 and I have the “same” issue:

["[SQL0204] ACCOUNT in WEBR type *FILE not found. Cause . . . . . : ACCOUNT in WEBR type *FILE was not found.

WEBR is our connection user.

Thank you in advance!

5

Hi @senjutok,

Can you please see following: Behavior of the Libraries Property and Default Collection

I think, this has got something to do with you you’ve configured your JDBC string.

Please see if fixing your JDBC Connection String resolves this issue.

6

Hey @senjutok,

Were you able to resolve this issue? Let us know, we would love to hear some feedback on your outcome!

7

@senjutok Hi did you every get it to work, and could you please share the jar driver version your running, as im also trying to connect to a AS400 DB2, im a bit unsure if im using the correct version

8

Hello Serigo, Is this issue got resolved for you? If it is could you please let us know the solution of it. I am also facing similar issue. Thanks