In particular, the CleanUpHistory job could have problems if a page lock is set in the database tables SCHEDULER_HISTORY and SCHEDULER_ORDER_HISTORY.
Please call the following SQL statements
MSSQL Server
ALTER INDEX SCHEDULER_HISTORY_START_TIME ON SCHEDULER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_HISTORY_SPOOLER_ID ON SCHEDULER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_HISTORY_JOB_NAME ON SCHEDULER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_H_CLUSTER_MEMBER ON SCHEDULER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_O_HISTORY_SPOOLER_ID ON SCHEDULER_ORDER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_O_HISTORY_JOB_CHAIN ON SCHEDULER_ORDER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF); ALTER INDEX SCHEDULER_O_HISTORY_START_TIME ON SCHEDULER_ORDER_HISTORY SET (ALLOW_PAGE_LOCKS = OFF);
Sybase
ALTER TABLE SCHEDULER_HISTORY LOCK DATAROWS; ALTER TABLE SCHEDULER_ORDER_HISTORY LOCK DATAROWS;
MySQL
work in progress
Oracle
work in progress
DB2
work in progress