Error "ORA-00001: unique constraint (AVUSER.PK_T_DATA_RUNS) violated" after restoring from backup in RSA Governance & Lifecycle
Article Number
Issue
After running the collector there's no run reflected in the monitoring tab.
The aveksaServer.log file showed a large number of the following errors,
ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-00001: unique constraint (AVUSER.PK_T_DATA_RUNS) violated
Cause
If there is activity on the system like background process being submitted they will use additional sequence values, but the backup will still have the lower value.
On a restore this can account for the difference in the table and sequence values that were found.
Resolution
select * from user_sequences where sequence_name='DATA_RUN_SEQUENCE';
select max(id) from t_data_runs;
Related Articles
Where is the tem-service.config file in DLP 9.5? Number of Views AWS IAM Identity Center - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views RSA Governance & Lifecycle Collections (Vol.16) : Amazon AWS IAM Number of Views AWS IAM Identity Center CloudWatch - RSA Ready Implementation Guide Number of Views Failed to cleanup RADIUS data when restoring backup from Operations Console of RSA Authentication Manager 8.4.x Number of Views
Trending Articles
An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
