ADC fails with 'ORA-01400: cannot insert NULL into ("AVUSER"."GTT_CE_RELATIONS"."SRCPK_ID")' Admin error in RSA Identity Governance & Lifecycle
3 years ago
Originally Published: 2016-01-20
Article Number
000049840
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 7.0.0
 
Issue
An RSA Identity Governance & Lifecycle Account Data Collector (ADC) fails with the following Admin Error:
 
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-01400: cannot insert NULL into ("AVUSER"."GTT_CE_RELATIONS"."SRCPK_ID")
ORA-06512: at "AVUSER.COMMON_EXPLODER", line 1099
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 244
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 447
ORA-06512: at line 1
 
User-added image
 

The following error is logged to the aveksaServer.log file:
  
11/05/2015 17:53:56.657 ERROR (Exec Task Consumer#0) [com.aveksa.server.xfw.TaskExecutor] 
Failed method=Execute ExecutionTask[TaskID=549 RunID=267 Source=25 Type=DataObjectProcessing 
Status=InProgress]
com.aveksa.server.xfw.ExecutionException: com.aveksa.server.collector.DataProcessorException: 
com.aveksa.server.db.PersistenceException: java.sql.SQLException: 
ORA-01400: cannot insert NULL into ("AVUSER"."GTT_CE_RELATIONS"."SRCPK_ID")
ORA-06512: at "AVUSER.COMMON_EXPLODER", line 1099
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 244
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 447
ORA-06512: at line 1

at com.aveksa.server.xfw.DataObjectProcessingExecutor.executeFullTask(DataObjectProcessingExecutor.java:119)
at com.aveksa.server.xfw.DataObjectProcessingExecutor.executeTask(DataObjectProcessingExecutor.java:58)
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)
Caused by: com.aveksa.server.collector.DataProcessorException: com.aveksa.server.db.PersistenceException: 
java.sql.SQLException: ORA-01400: cannot insert NULL into ("AVUSER"."GTT_CE_RELATIONS"."SRCPK_ID")
ORA-06512: at "AVUSER.COMMON_EXPLODER", line 1099
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 244
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 447
ORA-06512: at line 1

at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.loadData(DefaultAccountObjectDataFilter.java:110)
at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.process(DefaultAccountObjectDataFilter.java:72)
at com.aveksa.server.xfw.DefaultAccountObjectDataFilter.process(DefaultAccountObjectDataFilter.java:60)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)
at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)
at com.aveksa.server.xfw.DataObjectProcessingExecutor.executeFullTask(DataObjectProcessingExecutor.java:116)
... 4 more
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycleto find the location of the aveksaServer.log file for your specific deployment. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
 
Cause
This is a known issue reported in engineering ticket ACM-58258.

This issue occurs when a user has been mapped to an account that is subsequently deleted and re-collected.
 
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle versions and/or patch levels: 
  • RSA Identity Governance & Lifecycle 7.0.0 P01
  • RSA Identity Governance & Lifecycle 7.0.1

 

Related Articles

Trending Articles

Don't see what you're looking for?