Question
Infosys
US
Last activity: 18 Mar 2024 10:12 EDT
Job Scheduler Failure due to Database Exception
Hello,
I am running into a job scheduler failure, this has been happening for months.
The job scheduler is pyPegaArchivalVacuumFreeze, I am not sure if it failing because the DB table is empty or not.
The error is that it is a Database Exception (see stack trace below):
com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Job Scheduler [pyPegaArchivalVacuumFreeze] activity [pzPegaArchivalVacuumFreeze] execution marked as failed with message [Database Exception]
I have searched for documentation on this but there is very little on this particular OOTB job scheduler.
When I search in Pega for the java code to see where it is failing in that I cannot find the code.
Can someone please point me in the right direction for fixing this error
Accepted Solution
Updated: 18 Mar 2024 10:12 EDT
Virgin Media
GB
It's more likely your database is not PostgreSQL, which this is intended for. There is a bug because the SQL Connect rule states package as "ALL" instead of "postgres".
The SQL under Save shows "vacuum freeze {Class:Data-ArchivalMetadata}" which is specific to PostgreSQL and no other DB.
If your DB is not PostgreSQL, then disable this job.
Cheers Craig
Proximus
BE
I guess the logs on the server on which it runs should give more information.
Can you please check & provide the relevant lines.
You can then also maybe run it manually and trace it.
It could be also that the DB user is not having enough grants for the requested actions to be performed.
Last, if this JS tries to take actions (& fails) for month on a table which is still empty, question is whether this one is really needed for your application.
If not relevant then you could just disable it.
Regards
Anthony
Accepted Solution
Updated: 18 Mar 2024 10:12 EDT
Virgin Media
GB
It's more likely your database is not PostgreSQL, which this is intended for. There is a bug because the SQL Connect rule states package as "ALL" instead of "postgres".
The SQL under Save shows "vacuum freeze {Class:Data-ArchivalMetadata}" which is specific to PostgreSQL and no other DB.
If your DB is not PostgreSQL, then disable this job.
Cheers Craig