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
Users tab slow to load in SecurID Governance & Lifecycle Number of Views ASR fails to generate and the log file has 'ORA-04063: package body "AVUSER.SRSECTION_SYSTEM" has errors' errors in RSA Id… Number of Views RSA Identity Governance & Lifecycle Attribute Change Rule for Managed Attributes with argument "Set to old value of" does … Number of Views Java exception error during restore of default console certificate on RSA Authentication Manager 8.2 and higher Number of Views Accessing the raw data tabs for collector runs is very slow in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
Authentication Manager Supported Hardware and Upgrade Paths RSA Authentication Manager Upgrade Process Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager 'Principal Does Not Possess Authenticator' Error for Users with Multiple IDs
Don't see what you're looking for?
