Lock and primary key constraint violation errors
Lock errors and primary key constraint violation errors in the Autonomic Event Services (AES) system logs. This results in large log files and subsequently the system does not work correctly.
104 [WebContainer : 8] [STANDARD] [AES:07.14] (Line.PegaAES_Data_Alert.Action) ERROR your_node|your_ip|SOAP|PegaAES|Events|logAlert|A9FFE283AB6CBD6877F049869A5021DE6 - obj-save failed.
DatabaseException caused by prior exception: com.ibm.websphere.ce.cm.DuplicateKeyException: Violation of PRIMARY KEY constraint 'PEGAAM_ALERT_PK'. Cannot insert duplicate key in object 'dbo.pegaam_alert'. The duplicate key value is (PEGAAES-DATA-ALERT 20170914T134101.263 GMT!41FBB9B0F0281094E929905EA9EE5B36!1564).
Steps to Reproduce
A software use or operation error The prlogging file contained references to the AES SOAP appenders. The Predictive Diagnostic Cloud (PDC) URL landing page also specified the AES server and enabled the dynamic appenders. Hence, the alerts were sent twice which resulted in duplicate key violation.
As a local-change, remove the appender references from the prlogging file and restart the monitored nodes.
0% found this useful