Question
exception on log post upgrade to Pega 8.4
Exception in executing Job[pyClusterAndDBCleaner] com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Activity execution failed with [User marked activity execution to failed with message [ Exception while defragmenting Table::pr_sys_delayed_queue associated with class::System-Message-QueueProcessor-DelayedItem: code: 1031 SQLState: 42000 Message: ORA-01031: insufficient privileges ORA-06512: at "PRPC_APP.SPPR_DEFRAGMENT_TABLE", line 54
Is there any answer to this yet?
From my understanding it means DATA schema user needs the privilege EXECUTE ANY PROCEDURE in order to make this work, however in the Pega 8.3 installation guide this privilege is not supposed to be granted for DATA schema user.
This procedure requires (in Oracle) DROP ANY TABLE privilege because it uses a SQL TRUNCATE. The privilege should be granted to the user configured on the admin data source.
A common scenario where I see this exception is a system that uses only a base user. In that case you would need to implement an external DB maintenance process to defragment tables such as pr_sys_locks.
In our Pega 8.3 setup we use a dual-user configuration and the very same error pops up and points to the DATA schema like this:
ERROR - Exception in executing Job[pyClusterAndDBCleaner] com.pega.platform.executor.jobscheduler.scheduler.JobExecutionException: Activity execution failed with [User marked activity execution to failed with message [ Exception while defragmenting Table::pr_sys_delayed_queue associated with class::System-Message-QueueProcessor-DelayedItem: code: 1031 SQLState: 42000 Message: ORA-01031: insufficient privileges ORA-06512: at "DATA_SCHEMA.SPPR_DEFRAGMENT_TABLE", line 54
We installed Pega from scratch (Oracle+Tomcat), which means that we initially installed Pega with a new created admin user and data / rules schema users as well (they have all the privileges granted which the installation guide is defining). This means our admin user has DROP ANY TABLE privilege granted too, still this error pops up. How come?
Check this:https://community.pega.com/support/support-articles/schedulerjobexecutionexception-activity-execution-failed