Jobs are not running with ORA-00028 in the bg-ca.logs


Article ID: 74804


Updated On:


CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM SaaS - Application Clarity PPM On Premise


After upgrading to PPM 15.3 or higher, there are times when jobs are not executing properly. Jobs set to run immediately do not execute and instead go into the 'Scheduled' status, and jobs that are scheduled do not run even after reaching their scheduled start time.

The bg-ca.log files display the following error messages when this occurs

ERROR 2018-03-06 00:02:13,608 [Thread-6] niku.njs (clarity:admin:7969970__851A9445-9C29-4BD6-A265-9BE35024798B:none) 
SQL error code: 0 
Error message: [CA Clarity][Oracle JDBC Driver]Object has been closed. 
Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-00028: your session has been killed 


This behavior is being investigated in the defect DE38782.


CA PPM 15.3 and higher


There is no resolution for this defect yet.

  1. Cancel any jobs in the 'Processing' status, and pause any that are scheduled
  2. Restart the background services
  3. After the restart has been completed, reschedule and run jobs as necessary
For On-Demand users, please open a Support case to have step 2 taken for the affected environment.

Additional Information

For information regarding other causes on jobs remaining in the 'Waiting' or 'Scheduled' status, see here Clarity: Scheduled jobs stuck in waiting or scheduled status