Error "ORA-00001: unique constraint (AVUSER.PK_T_DATA_RUNS) violated" after restoring from backup in RSA Governance & Lifecycle
Last Modified: 2023-09-20
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
FAQ on restoring an RSA Authentication Manager 8.x Backup into a New Deployment 134Number of Views What kind of data is in the KCA backup files? 8Number of Views Failed to cleanup RADIUS data when restoring backup from Operations Console of RSA Authentication Manager 8.4.x 251Number of Views RSA Authentication Manager 8.x Backup Fails With Error 61Number of Views Roles in a Role Review are Incorrectly Set to the 'Changed' State Instead of the 'Committed' State in RSA Governance & Lif… 3Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process
Don't see what you're looking for?