RAR: Batch Risk (Full) not completing - gets hung

[Former Member]

Hi everyone:

We are on RAR 5.3 and we have 3 backend systems (ECC, CRM, Banking Services). We have run Full User/Role/Profile sync jobs for all 3 backends, all completing successfully. So our connectors are working fine.

When we try to run the Full Batch Risk Analysis to establish our baseline, the CRM and Banking Services jobs complete successfully in under 1 hour.

When we try to run the Full Batch Risk Analysis for ECC system, we get the error below. After this error, the job hangs and does not continue - but does not error out....it just stays in "running" state.

Can anyone offer any insight?

Thanks in advance!

Margaret

Apr 20, 2011 8:43:44 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis

WARNING: Error: while executing BatchRiskAnalysis for JobId=104 and object(s):E30765: Skipping error to continue with next object: [jcc][t4][102][10040][3.59.81] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.

Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

Apr 20, 2011 8:43:44 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory

FINEST: --- @@@@@@@@@@@ Updating the Job History -

---

2@@Msg is Error while executing the Job for Object(s) :E30765:[jcc][t4][102][10040][3.59.81] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.

Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

Apr 20, 2011 8:43:44 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -

---

Background Job History: job id=104, status=2, message=Error while executing the Job for Object(s) :E30765:[jcc][t4][102][10040][3.59.81] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.

Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null

[Former Member]

Hi,

We are getting the same error in our environment. Could you please let us know how you resolved this issue?

Thanks

[frank_bannert]

Hi Margaret,

for that on you would need to look into the whole log file and analyze it.

I would suggest you open an OSS message to get somebody looking into it.

Best,

Frank