000037632 - The Account Data Collectors (ADC) fail with ORA-00904: "RESOURCE_NAME": invalid identifier after uprgading RSA Identity Governance & Lifecycle from 7.0.2 to 7.1.1

Document created by RSA Customer Support Employee on Jun 14, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037632
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1
IssueThe Account Data Collectors (ADC) fail with the following error after uprgading RSA IdentityGovernance & Lifecycle from 7.0.2 to 7.1.1. 
ORA-00904: "RESOURCE_NAME": invalid identifier

The following errors are seen in the aveksaServer.log:

03/22/2019 13:48:42.480 WARN (Exec Task Consumer#0 - Accounts Sequence)
[org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 904,
SQLState: 42000 03/22/2019 13:48:42.481 ERROR (Exec Task Consumer#0 - Accounts Sequence)
ORA-00904: "RESOURCE_NAME": invalid identifier
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 197
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 477 ORA-06512: at line 1
CauseThe cause of this issue is unknown at this time.
ResolutionThere is no known resolution for this issue. If you encounter this issue, please open a case with RSA Identity Governance & Lifecycle support and submit the following artifacts:

  • /home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServer.log
  • /home/oracle/wildfly-10.1.0.Final/standalone/log/aveksaServerInfo.log
  • /home/oracle/wildfly-10.1.0.Final/standalone/log/migrate.log
  • /u01/app/oracle/diag/rdbmsavdb/ADB/trace/alert_AVDB.log (Oracle database alert log)
  • Note which collector is running at the time of the error and send screenshots of the failure in the RSA Identity Governance & Lifecycle User Interface, the database logs for the collector and the collector metadata definition.

The log file references above are for a standalone WildFly deployment. If you have RSA Identity Governance & Lifecycle deployed on a different platform or on a WildFly cluster, please refer to 000030327 - Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files in your deployment.

WorkaroundIn this case the customer recreated the database schema, imported the metadata and reran collections. This solution worked but the problem with this solution is that data prior to the upgrade is lost.