Error while using JDBC activity "Not able to get the credential with the sysId"

[Maheshwari Man1]

Hi,

While using Test Connection in JDBC Custom activity, it's throwing error message as below:

"Connection Failed: java.lang.RuntimeException: com.snc.automation_common.integration.exceptions.InvalidOperationException: Not able to get the credential with the sysId: 79f7******************************2. If the credential is an external credential, please verify your external credential setup/configuration. Otherwise, please check if the credential is active."

But the credential entry with the same sys_id ("79f7******************************2") exist in discovery_credentials table. I also have tried to create new credential entry, but still same error.

Note: JDBC credential and Connections are working fine & validated successful and this JDBC activity is working fine in other instance for same credential and connections.

[Akshata jamdar]

Hello maheswarimanokaran,

1.If you are using credential ID for connectivity there is an plugin (External Credential Storage) should be activated, this is one case.

2.check if the applied to check box is selected for specific MID server.

Hope this will resolves your query.

Regards,

Akshata

[Maheshwari Man1]

Hi Akshatha,

External credential storage plugin is already activated and credential is working fine if I use Test Credential in credential module, but it is throwing error message when I click on Test Connection or Test Inputs from Activity Designer.

If I publish the activity (without clicking Test Inputs) and use it in workflow, it is working as expected. The problem is with activity designer UI and throwing message as "Not able to get the credential with the sysId". Without testing the activity in JDBC Activity Designer, I cannot use it in workflow as I have to parse the output to individual variables and I have to use Post-Processing Script.

DB Credentials are working fine in JDBC Credential, JDBC connection and workflow modules except JDBC Activity. Sp problem is not with connecting to Oracle Database, but it is not able to identify the sys_id of credential entry from discovery_credential table in JDBC Activity Designer alone.

[dipam3]

Hi,

I am facing the exact issue. Are you able to fix this? ANy help would be appreciated.

Regards,

Dipam

[Maheshwari Man1]

Hi Dipam,

Yes... Ensure the credential entry exist with the same sys id. This issue may occur due to existing Orphan credentials in Discovery Credential table due to cloning. Delete all invalid or empty records from discovery_credentials table to fix this issue.

Regards,

Maheswari Manokaran