cancel
Showing results for 
Search instead for 
Did you mean: 

RAR - Management Report giving Errors

Former Member
0 Kudos

Hello

I executed the GRC AC 5.3 -> RAR -> Management Report and it gave the following errors, seen below in the background job log.

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start Insert user groups that doesn't have any violation....1272380023698

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis runBkgMgmReport

WARNING: Exception in Management Report Job: [-9210]: System error: KB Stack op illegal

com.sap.dbtech.jdbc.exceptions.DatabaseException: [-9210]: System error: KB Stack op illegal

at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:65)

at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1061)

at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:689)

at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:563)

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.bg.BgJob run

WARNING: *** Job Exception: [-9210]: System error: KB Stack op illegal

com.sap.dbtech.jdbc.exceptions.DatabaseException: [-9210]: System error: KB Stack op illegal

at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:65)

at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:1061)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.bg.BgJob setStatus

INFO: Job ID: 60 Status: Error

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory

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


2@@Msg is Error while executing the Job:[-9210]: System error: KB Stack op illegal

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -


Background Job History: job id=60, status=2, message=Error while executing the Job:[-9210]: System error: KB Stack op illegal

Apr 27, 2010 10:53:43 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: -


Complted Job =>60----


Has anyone experience the above error before.

What does "System error: KB Stack op illegal" mean? Is it due to a memory problem or is there any RAR configurations that I am missing?

Thanks,

Imran

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Imran,

One of our customer has got similar issue and it is not because of "Memory" issue.

They had a wrong risk name "FO01" instead of "F001". Risk name has alphabet 'O' instead of numeric zero '0'.

The issue was resolved once customer deleted this risk and re-ran all Synchronization, BatchRisk Analysis & Management Reports.

Please make sure your "Risk Names" are inorder.

Best Regards,

Sirish Gullapalli.

Former Member
0 Kudos

Hi Sirish,

I checked the Risk Names. There appear to be in order and there are 203 risks in our system. I uploaded these risks through SAP GRC Text files. We have not added any custom Risks of our own.

Currently we only have SAP Default Risks got from the uploaded text files.

The Full user/profile/role sync job completed successfully and Batch risk analysis job also completed without errors. But when I execute management report, I am getting the above error.

Is there any OSS Notes, URL available for management report issues.

Thanks,

Imran

Former Member
0 Kudos

Hi Imran,

Following are few OSS Notes related to "Management Reports"

Note 1034117 - Management Reports run too long, not updating, or inaccurate

Note 1179717 - Risk Analysis and Remediation - Management Reports

If you still facing the issue after going through these messages, please open a message with GRC support to look into the issue.

Best Regards,

Sirish Gullapalli.

Former Member
0 Kudos

Hi we are having the same problems.

As question is marked answered, can you please post the solution.

Former Member
0 Kudos

Hi Kraell,

The solution was that the risk which were not in proper order were deleted and all Synchronization, BatchRisk Analysis & Management Reports were executed again.

Thanks,

Imran

Former Member
0 Kudos

What do you mean with "risks that were not in proper order were deleted"?

Much appreciated

Answers (0)