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
Failed to cleanup RADIUS data when restoring backup from Operations Console of RSA Authentication Manager 8.4.x Number of Views AWS IAM Identity Center - SAML Relying Party Configuration - RSA Ready Implementation Guide Number of Views Getting the RSA backup files from the RSA Authentication Manager 8.x primary instance Number of Views AWS IAM Identity Center CloudWatch - RSA Ready Implementation Guide Number of Views Unable to restore a backup data more than once when a restore destination is not same Authentication Manager of the backup… Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?
