The Indirect Relationship Processing task for Account Data Collectors (ADCs) and/or Entitlement Data Collectors (EDCs) shows a status of
Failed in the User Interface (
Admin >
Monitoring >
Run ID).
The following error is logged to the
aveksaServer.log file (
$AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log):
01/23/2017 15:16:26.407 ERROR (Exec Task Consumer#0) [com.aveksa.server.xfw.TaskExecutor]
Failed method=Execute
ExecutionTask[TaskID=251222 RunID=101923 Source=2962 Type=EntitlementExplosionProcessing Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.db.PersistenceException:
java.sql.SQLException:
ORA-12899: value too large for column "AVUSER"."GTT_CE_INDIRECTS"."ROOTCHILDNAME" (actual: 263, maximum: 256)
ORA-06512: at "AVUSER.CE_ACCOUNTS", line 402
ORA-06512: at "AVUSER.CE_ACCOUNTS", line 973
ORA-06512: at "AVUSER.COMMON_EXPLODER", line 298
ORA-06512: at "AVUSER.COMMON_EXPLODER", line 117
ORA-06512: at line 1
at com.aveksa.server.xfw.EntitlementExplosionProcessingExecutor.executeTask
(EntitlementExplosionProcessingExecutor.java:54)
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:745)
Please refer to RSA Knowledge Base Article
000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the
aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The
aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (
Admin >
System >
Server Nodes tab > under
Logs).
This issue occurs when a Group name is greater than 256 characters.
This is a known issue reported in engineering ticket ACM-71796.
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and patch levels:
- RSA Identity Governance & Lifecycle 7.0.2 P03
- RSA Identity Governance & Lifecycle 7.1.0
