Insert Statement run on DATA_OWNER.pr_data_qp_run_partition

General
, , ,
1

Hi in database audit trail, we see Huge insert statements failing for the data_owner.pr_data_qp_run_partition table, but the table count is not increasing and is static.

An failed insert attempt happening on the table and that is recorded in db_audit_trail in oracle.

the Insert statement is :

INSERT INTO DATA_OWNER.pr_data_qp_run_partition (pzInsKey , pxCommitDateTime , “PXCREATEDATETIME” , “PXCREATEOPERATOR” , “PXCREATEOPNAME” , “PXCREATESYSTEMID” , “PXINSNAME” , “PXOBJCLASS” , “PXQUEUEPROCESSORNAME” , “PXSAVEDATETIME” , “PXSTREAMPARTITION” , “PXSTREAMPOSITION” , “PXUPDATEDATETIME” , “PXUPDATEOPERATOR” , “PXUPDATEOPNAME” , “PXUPDATESYSTEMID”) VALUES (:1 , CURRENT_TIMESTAMP , :2 , :3 , :4 , :5 , :6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 )

Strange is , this failed insert is not getiing recorded in PEGARULES-ALERT.LOG too ..

2

This issue is happening because the insert statements are being generated by the queue processor, but they are failing at the database level due to a constraint, permission, or table issue in DATA_OWNER.pr_data_qp_run_partition. Since the failure is happening in the database layer, Pega cannot complete the request, so the table row count stays unchanged even though attempts are made. The failure is only captured in Oracle db_audit_trail because the transaction reaches the database but is rejected there. It does not appear in PEGA RULES ALERT LOG because Pega logging happens before or after rule execution, and this failure occurs outside Pega rule processing. The fix is to check database constraints, table space, and user privileges for the DATA_OWNER schema to ensure inserts are allowed.