000037642 - 'ORA-00001: unique constraint (AVUSER.IDX_AK_DASHBOARD_COMPONENT) violated' error upgrading to version 7.1.0 of RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 20, 2019Last modified by RSA Customer Support Employee on Apr 18, 2020
Version 6Show Document
  • View in full screen mode

Article Content

Article Number000037642
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.x, 7.x
 
IssueAfter upgrading to RSA Identity Governance & Lifecycle 7.1.0, users are unable to access the RSA Identity Governance & Lifecycle login screen:
 
Initialization operations completed with errors. Please resolve the problem(s) before the application server can accept requests.

Errors found while patching the schema


 


Error when accessing User Interface


The following errors are seen in the aveksa installation log (/tmp/aveksa-install.log):  




[0:00:41 93%] .executing com.aveksa.migration.jdbctool.JavaStepPopulateReports
0 [main] INFO org.hibernate.Version - HHH000412: Hibernate Core {5.0.11.Final}
2 [main] INFO org.hibernate.cfg.Environment - HHH000206: hibernate.properties not found
3 [main] INFO org.hibernate.cfg.Environment - HHH000021: Bytecode provider name : javassist
380 [main] INFO org.hibernate.annotations.common.Version - HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
1157 [main] INFO org.hibernate.engine.jdbc.connections.internal.ConnectionProviderInitiator
- HHH000130: Instantiating explicit connection provider: com.aveksa.migration.utils.db.MigConnectionProvider
1177 [main] INFO org.hibernate.dialect.Dialect - HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect
1439 [main] WARN org.hibernate.orm.deprecation - HHH90000018: Found use of deprecated transaction factory setting
[hibernate.transaction.factory_class]; use the new TransactionCoordinatorBuilder settings
[hibernate.transaction.coordinator_class] instead
3582 [main] WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper - SQL Error: 1, SQLState: 23000
- ORA-00001: unique constraint (AVUSER.IDX_AK_DASHBOARD_COMPONENT) violated

3582 [main] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper
- ORA-00001: unique constraint (AVUSER.IDX_AK_DASHBOARD_COMPONENT) violated


java.sql.SQLException: com.aveksa.server.db.PersistenceException: Executing JDBC update failed
  at com.aveksa.migration.jdbctool.PopulateAvReports.insertNonExistingReports(PopulateAvReports.java:2606)
  at com.aveksa.migration.jdbctool.PopulateAvReports.execute(PopulateAvReports.java:83)
  at com.aveksa.migration.jdbctool.JavaStepPopulateReports.run(JavaStepPopulateReports.java:17)
  at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:211)
  at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:107)
  at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:98)
  at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
  at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:159)
  at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:83)
  at com.aveksa.cli.CreateMigrateSchemaModule.runCommandImpl(CreateMigrateSchemaModule.java:211)
  at com.aveksa.cli.BaseDatabaseCLIModule.runCommand(BaseDatabaseCLIModule.java:80)

(...)

[0:00:45 96%] executing migration/createPublicSchema.sql
[0:00:45 96%] .executing com.aveksa.migration.jdbctool.JavaStepPublicSchemaViews
[0:01:03 98%] executing Create Scripts/Grant_Select_To_Reports.sql
[0:01:13 98%] executing migration/updateRemoteDB.sql
[0:01:13 98%] .executing com.aveksa.migration.jdbctool.JavaStepUpdateRemoteDB
[0:01:13 98%] executing migration/setVersion.sql
[0:01:13 98%] .executing com.aveksa.migration.jdbctool.JavaStepSetVersion
[0:01:13 98%] executing migration/deleteHotFixes.sql
[0:01:13 98%] executing migration/recompileAll.sql
CauseDuring database migration, the migration script is trying to enter a duplicate entry into one of the database tables in the AVUSER schema which violates an index constraint. The exact reason for this is unknown.
 
ResolutionPlease contact RSA Identity Governance & Lifecycle Support for resolution and mention this RSA Knowledge Base Article ID 000037642 for reference.
 

Attachments

    Outcomes