cancel
Showing results for 
Search instead for 
Did you mean: 

GRC 10.1 - GRAC_BATCH_RA( Job packages are failing with error)

Former Member
0 Kudos

Hi experts,

We have GRC10.1 with SP06. The problem we have s with transaction GRAC_BATCH_RA. We are running batch risk analysis in order to be able to use the offline risk analysis.

But each time we run the analysis some users are left out and not being analyzed successfully. So Offline reports are not being proper. While checked we found that the GRAC_BATCH_MONITOR shows some packages for users are running with error.

Instead of completed the users has a status "Re-Process"

Attached you can find the log and SLG1 screen with the error.

Please help us fix the issue.

The following parameter are set as "100"

1120-1123 and 1034

The parameter rdisp/wp_no_btc is set as 6 in the system.

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Dear Mainak,

Please implement SAP Note 2090933,

Let us know how it goes,

Kind Regards,

Rafael Guimbala


Former Member
0 Kudos

Thanks for the input Rafael,

I applied the Notes, Run the Batch Risk, but unfortunately the error persists,

former_member185447
Active Contributor
0 Kudos

Hello Mainak,

  • Check what type of user are they?
  • Have you ignored those user types?
  • Also Check if the user ids are locked or expired?
  • What are the SLG1 logs displaying?


Regards,

Deepak M

Former Member
0 Kudos

Hi Deepak,

The Users are not any particular Type.

No users are ignored, the parameters are set to include all users.

Expired users are also included in the parameter.

SLG1 log is already attached.

Thanks

former_member185447
Active Contributor
0 Kudos

Hello Mainak,

After going through the SLG1 logs, I can find one message which goes like this:

Error in processing the package with an exception type cx_sy_open_sql_db Occur.

Generally ,this type of error occurs if the Input data requires more space than available.The where condition in the SQL query contains too many input data. So, the query has to be split according to the input data.

Try executing the job selecting only one connector and find out if it is able to process.

Regards,

Deepak M

Former Member
0 Kudos

Hi Deepak,

I have tried with inly a small set of users, even then the same error occurs. I am already using only one connector.

Thanks and Regards,