Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

customqueryjob failing after version upgrade to V23.5

Nagendra
New Contributor II
New Contributor II

We have created a custom query job of type 'Execute Extension Queries' to update the account type of a specific endpoint's account. It was functioning properly until the recent upgrade to Saviynt version 23.5. Have any specific changes been made to this query? Has anyone else encountered a similar issue after the upgrade? Has anyone experienced and resolved this issue?

Query: Update accounts set ACCOUNTTYPE='Service Account' where endpointkey=4 and status=1

10 REPLIES 10

NageshK
Saviynt Employee
Saviynt Employee

@Nagendra Thanks for posting your question. The attachments provided here seem to be applicable for the other post you created. For the current issue, can you check what the error message is in the job detials? It should tell you why the execution is failing. 

Also, what was the version prior to the upgrade?

Thanks,

Nagesh K

lionelrl
New Contributor III
New Contributor III

Can someone please help us figure out why the custom query job is failing? , we are just using this to classify the account type as Service Account.

Query: Update accounts set ACCOUNTTYPE='Service Account' where endpointkey=4 and status=1

 

[Edited] : I see debug message in the logs that the custom query job is not running.

Could someone please us on above issue.

NageshK
Saviynt Employee
Saviynt Employee

@sureverma @lionelrl I have tried this query in one of my internal environments and it is working fine. Also, this query will update accountype of all accounts of the endpoint to 'Service Account'. Is that what you want? Can you elaborate the use case? And are other custom query jobs working fine in your env?  

Thanks,

Nagesh K

lionelrl
New Contributor III
New Contributor III

Hi @NageshK ,

We have all the application accounts / service accounts imported using a separate connection and associated with this endpoint. Yes, the requirement is to update all accounts in this endpoint of type service account. 

Apart from this we have another on demand query job, to update the localauthenabled=1 , which is working as expected. 

 

-Lionel 

What is the error in UI under JOB LOG History? Can you share the screenshot of JOB configuration and job history log?


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

lionelrl
New Contributor III
New Contributor III

Hi SK,

Please find the details below.

lionelrl_0-1689109827679.png

It fails , but there is no error mentioned in the JOB Log . However I see this in the logs.

2023-07-11T17:11:50-04:00-ecm-worker-2023-07-11T21:11:50.484648844Z stdout F 2023-07-11 21:11:50,484 [quartzScheduler_Worker-6] DEBUG jobs.CustomQueryJob - Executing CustomQueryJob
2023-07-11T17:11:50-04:00-ecm-worker-2023-07-11T21:11:50.484684045Z stdout F 2023-07-11 21:11:50,484 [quartzScheduler_Worker-6] DEBUG jobs.CustomQueryJob - Custom Query Job Started at- Tue Jul 11 21:11:50 UTC 2023
2023-07-11T17:11:50-04:00-ecm-worker-2023-07-11T21:11:50.520890682Z stderr F 11-Jul-2023 21:11:50.520 WARNING [quartzScheduler_Worker-6] groovy.sql.Sql.withBatch Error during batch execution: Data truncation: Truncated incorrect DOUBLE value: 'SUSPENDED FROM IMPORT SERVICE'
2023-07-11T17:11:50-04:00-ecm-worker-2023-07-11T21:11:50.522211691Z stdout F 2023-07-11 21:11:50,522 [quartzScheduler_Worker-6] DEBUG services.SaviyntCommonUtilityService - Error Occured in customQueryExecution - true and exception - java.sql.BatchUpdateException: Data truncation: Truncated incorrect DOUBLE value: 'SUSPENDED FROM IMPORT SERVICE'
2023-07-11T17:11:50-04:00-ecm-worker-2023-07-11T21:11:50.526217917Z stdout F 2023-07-11 21:11:50,526 [quartzScheduler_Worker-6] DEBUG jobs.CustomQueryJob - Error Occured for customQueryExecution - true

Can you try below query

Update accounts set ACCOUNTTYPE='Service Account' where endpointkey=4 and status='1'


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

lionelrl
New Contributor III
New Contributor III

Hi SK,

It worked, so what was the issue ? . Is Saviynt looking for status value as String ?

 

-Lionel

Yes status column is varchar type and based on the logs I see there is a data type issue and Hence asked you to update as string.

Since your issue resolved please mark the appropriate response as solution so that it helps the others who are in same situation


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.