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
000068270
Issue
There are some of failures with collections, and review generation after restoring backup although the backup restore process did not produce errors.
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
When a data backup is taken it will first capture the sequence values.
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
Please contact RSA Customer Support and quote this article number and attach the below query output in the case. 
select * from user_sequences where sequence_name='DATA_RUN_SEQUENCE';
select max(id) from t_data_runs;

 
Don't see what you're looking for?