We identified an issue where it appeared internal database tables (QRZT) were getting corrupted, not allowing users to see and modify target account scheduled jobs.
The problem occurs when creating scheduled jobs. If you have multiple jobs and modify an existing job, you will most likely get an “error while accessing the database” error.
This state can also cause other, unrelated, jobs to be deleted. You will see the following in the Tomcat catalina.out file:
SEVERE: Servlet.service() for servlet [ndg-rest-service] in context with path [/cspm] threw exception
[com.fasterxml.jackson.databind.exc.InvalidFormatException: Can not deserialize value of type int from String "jobc": not a
valid Integer value
There is a second, unrelated issue, we found in this context:
It is possible that jobs displayed in the table no longer exist because they have run.
If the user tries to edit such a job they will get a “PAM-CM-0039: Unable to perform the operation” error.
Instead of displaying a message “Job no longer exists”.
You will see the following in the catalina.out file:
SEVERE: GetScheduledJob.invoke exception
all versions between CA PAM 3.1 and 3.2.2
As a workaround, ONLY create scheduled jobs and never modify them.
If the job was defined incorrectly, it is recommend to delete it and create a new one instead of modifying it.
We are working towards a fix for both issues.