Unification failing with ORA-00904: "B"."AVAILABILITY_STATUS": invalid identifier in RSA Identity Governance & Lifecycle
3 years ago
Originally Published: 2018-08-31
Article Number
000041285
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
 
Issue
Unification starts to fail with an Invalid Identifier error:
User-added image
User-added image

The following error is seen in aveksaServer.log:
  
ERROR (Exec Task Consumer#8) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00904: "B"."AVAILABILITY_STATUS": invalid identifier
ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 47
ORA-06512: at line 1

06/28/2018 12:03:53.413 INFO  (Exec Task Consumer#8) [com.aveksa.server.xfw.UnificationExecutor] Failed method=Process subTask=CompleteMergeTasks Default User Population, 22109
com.aveksa.server.db.PersistenceException: java.sql.SQLSyntaxErrorException: ORA-00904: "B"."AVAILABILITY_STATUS": invalid identifier
ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 47
ORA-06512: at line 1

        at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1534)
        at com.aveksa.server.db.persistence.PersistenceServiceProvider.runStoredProcedure(PersistenceServiceProvider.java:1469)
        at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:269)
        at com.aveksa.server.xfw.UnificationExecutor.executeTask(UnificationExecutor.java:122)
        at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:99)
        at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:116)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "B"."AVAILABILITY_STATUS": invalid identifier
ORA-06512: at "AVUSER.UNFC_PROCESSOR", line 47
ORA-06512: at line 1
Cause
AVAILABILITY_STATUS is an internal attribute.  Unification fails on a statement that is dynamic and built on a collector configuration. The column might be in a configuration for some collector where we weren't expecting it.
Resolution
Check all the collectors (IDC/ADC/MAADC/EDC/MAEDC/RDC) and see if this attribute is used in any of its resolution rules and remove the mapping to this attribute to fix the issue.
 

Related Articles

Trending Articles

Don't see what you're looking for?