Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Bhavani Mantena (Bhavani Mantena)
Commonwealth Bank of Australia
Senior Systems Engineer
Commonwealth Bank of Australia
AU
Bhavani Mantena Member since 2015 2 posts
Commonwealth Bank of Australia
Posted: Jul 4, 2023
Last activity: Jul 12, 2023
Posted: 4 Jul 2023 3:12 EDT
Last activity: 12 Jul 2023 0:49 EDT
Closed

Uniq Constraint violation Exceptions for PR_SYS_LOCKS_PK in Prod

Hi,

We have an application which has case management, Pega Marketing and also Decisioning Hub. This application has been quite stable but off late, we have observed that there is an increase in ORA-00001: unique constraint (Pega_DATA_OWNER.PR_SYS_LOCKS_PK) violated in the prod instance.

The DBA has raised that the count of this exceptions has shot up on an hourly basis and is only accessible to the DBA and not the developers.

Since this is only visible to the DBA, and nothing is being written to Splunk, we are a bit clueless at the moment. 

LOGGED_AT ERR_MSG ERR_CAUSE
2023-06-29 01:16:07.290300000 ORA-00001: unique constraint (Pega_DATA_OWNER.PR_SYS_LOCKS_PK) violated insert into Pega_DATA_OWNER.pr_sys_locks ( pxCreateDateTime, pxCreateOpName, pxCreateOperator, pxCreateSystemID, pxExpireDateTime, pxLockHandle, pxObjClass, pxOwnerId, pxSystemName, pxSystemNode, pxUpdateDateTime, pxUpdateOpName, pxUpdateOperator, pxUpdateSystemID, pxUserHost, pyLabel, pzInsKey) values (:1 , :2 , :3 , :4 , :5 , :6 , 'System-Locks', :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , '', :15 )?

Is this a common behaviour across all pega applications?

Is there a baseline number to say what is acceptable and what is not? Any guidance/suggestions or ideas to deal with this are welcome.

Thanks,

Bhavani

 

***Edited by Moderator Marije to add Capability tags***
To see attachments, please log in.
Pega Platform 8.3.5
Case Management
Performance
Data Model
Financial Services
Decisioning Architect

Posted: 1 year ago
Posted: 4 Jul 2023 4:24 EDT
Prakash Rai (PrakashDeep)
Aaseya IT Services Pvt LTD
Prakash Deep Rai
Aaseya IT Services Pvt LTD
SA

@Bhavani Mantena

The error suggest the Primary Key violation in the mentioned table. The same primary key is being tried to be inserted in the same table which will fail due to Unique Key constraint applied on Primary Keys of any database table.

Is this a custom schema in your application "OFE_DATA_OWNER". You should try to find the reference of the places where you are trying to update the schema table. If might be from a user action or background processing logic (Queue Processor / Job Scheduler). If you can find the update reference, it might give you an idea what the code in the application is trying to perform on this table

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice