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
RSA Authentication Manager 8.2 SP1 Patch 2 - Readme Number of Views Where is the tem-service.config file in DLP 9.5? Number of Views Accessing the raw data tabs for collector runs is very slow in RSA Identity Governance & Lifecycle Number of Views SSL write error error:14095412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate Number of Views Authentication Manager Log Messages (20121-20180) Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Downloading RSA Authentication Manager license files or RSA Software token seed records
Don't see what you're looking for?
