Management reports Erroring out

[Former Member]

Greetings Experts,

I have completed a full batch analsys of users with Batch Risk Analysis , Later Roles with batch Risk Analysis, later Profiles with batch risk analysis and Then critical profiles with Batch risk analysis.

After Sequential completion of these changes, I scheduled the management report and the background jobs errors out and shows an error as below :

There was an empty user group in the backend in table "USGRP", I removed the empty user ggroup and re-ran the jobs again the above sequence, still get the below error :

Any Advise /Help is greatly appreciated.

FINEST: Unlock:1004

Apr 6, 2011 2:46:46 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start populate virsa_cc_mgrisks....1302115606211

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish populate virsa_cc_mgrisks....876

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start populate virsa_cc_mgmttot violation data....1302115607269

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish insert virsa_cc_mgmttot violation data....688

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

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

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish Insert user groups that doesn't have any violation....778

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start update mitref.1302115608737

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish update mitref.135

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Update urnone....1302115608872

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis runBkgMgmReport

WARNING: Exception in Management Report Job: Cannot assign an empty string to host variable 4.

com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 4.

[Former Member · Accepted solution]

Hi,

Did you check that the user data and roles data in GRC system after finished the job(user/roles/profile Full sysnc) successfully. if you find the data for the user/roles, then goahead to sechedule the remaining jobs(user/role/profile full batch risk analysis) and finally run the management reports job.

Regards,

Arjuna.

[Former Member · Accepted solution]

Greetings Arjuna,

yes, I have scheduled the jobs ins equential order :

Job1. User Sync (FULL) and Batch Risk Analysis for User (Full) - Completed successfully. then executed job2

Job 2. Role Sync (Full) and Batch Risk Analysis for Roles (Full) - Completed successfully. then executed job3

Job 3: Profile sync (FULL) and batch Risk analysis for profiles (Full) - Completed successfully. then executed job4

Job 4: Critical action and role profiles analysis under Batch Risk Analysis - Completed successfully. then executed job5

Job 5 : Management reports (Full) - Failed with an error cannot assign empty string to Host variable 4.

For all the ablve all systems were choosen (*)

I still get the same error..

[Former Member · Accepted solution]

I would try again with the user group set as *

What is your OS and the databse that you are using and also whats your support packs on the front end and the back end?

Regards,

Chinmaya

[Former Member · Accepted solution]

Greetings Chinmaya,

I have re-scheduled the job with full Sync and (*) for User groups and then re-scheduled the job for the Management reprots. This again errored out with the same error :

Error :

Background Job History: job id=26, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 4.

Comming to the Systems :

RAR is kooked up to backend HCM and ECC development systems :

The Operating system is : OS400

Database is : DB400

Backend Patches : HCM : VIRSAHR 5300_700 patch level 13

HCM: VIRSANH 5300_700 patch level 15

ECC : VIRSAHR 5300_700 patch level 13

ECC: VIRSANH 5300_700 patch level 15

Front End : GRC release 5.3 patch level 14

[Former Member · Accepted solution]

Hi Angara,

This it seems may be a problem with OS400, I had faced a similar problem with OS400 in the past. Are you using an iseries by any chance?

Is the Front end SP14 in sync with virsanh15? I dont have a good understanding of these later support packs?

Regards,

Chinmaya

[Former Member · Accepted solution]

Chinmaya,

Yes, We are on OS 400 on iseries, And as well Yes we are on back end support pack virsanh15 and front end Support pack 14.

We just applied the front end support patches 1-4 ffor SP14 for AE as we were having issues with CUP on Mandatory risk analysis.

I have also opened the customer message with SAP and looking forward for some answers for the long impending issue.

Please let me klnow if you had faced a similar issue in the past how did you resolve it? Your help will be greatly appericiated.

Best Regards,

Angara Rao

[Former Member · Accepted solution]

Angara,

I dont recollect but I dont think I got a reasonable resolution from SAP support for this ( for its based on the i-series platform.) The problem is that it does not really have a databse, but i think it is integrated in the OS.

I also had a similar problem with the User Groups. but for some reason it worked in my production system.

I remember seeing the correction notes suggesting that the RAR managment reports had fixed a problem with DB2 in SP14 I think. I would syncrinize the support packs first.

Also, I would try and assign user groups to all users if possible and not leave any one of those blank.

Regards,

Chinmaya

[Former Member · Accepted solution]

After performing all the activity of having appropriate user groups and leaving no blank users we still have the same issue. SAP came back after 2 weeks to state the issue is a generic issue with users on OS 400 iseries systems.

SAP has raised the issue with IBM and IBM is supposedly working on the fix - Not sure how long it will take to get the fix currently we are the same issue and having a work around on pulling the conflicts on users manually.

Best Regards

Angara Rao

[Former Member]

I Re-Ran the job after checking all the tables and the rule sets again, I received the same error as before. Complete error log below ;

Experts which tables has the Host variable "4"???

FINEST: Lock:1004

Apr 6, 2011 2:46:41 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:41 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:41 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:41 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:41 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock lock

WARNING: It is used by the another owner: For current thread retrying to get lock : 1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:42 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1010

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1010

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1004

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock lock

FINEST: Lock:1010

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1010

Apr 6, 2011 2:46:43 PM com.virsa.cc.xsys.util.Lock unlock

FINEST: Unlock:1004

Apr 6, 2011 2:46:46 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start populate virsa_cc_mgrisks....1302115606211

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish populate virsa_cc_mgrisks....876

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start populate virsa_cc_mgmttot violation data....1302115607269

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish insert virsa_cc_mgmttot violation data....688

Apr 6, 2011 2:46:47 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

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

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish Insert user groups that doesn't have any violation....778

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Start update mitref.1302115608737

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Finish update mitref.135

Apr 6, 2011 2:46:48 PM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute

INFO: Update urnone....1302115608872

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis runBkgMgmReport

WARNING: Exception in Management Report Job: Cannot assign an empty string to host variable 4.

com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 4.

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)

at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)

at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)

at com.virsa.cc.xsys.mgmbground.dao.MgmStats.execute(MgmStats.java:790)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.runBkgMgmReport(BatchRiskAnalysis.java:1306)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1562)

at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)

at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)

at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)

at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

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

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.BgJob run

WARNING: *** Job Exception: Cannot assign an empty string to host variable 4.

com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 4.

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)

at com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:57)

at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)

at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)

at com.virsa.cc.xsys.mgmbground.dao.MgmStats.execute(MgmStats.java:790)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.runBkgMgmReport(BatchRiskAnalysis.java:1306)

at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1562)

at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:560)

at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:363)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:375)

at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:92)

at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)

at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)

at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(AccessController.java:219)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

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

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.BgJob setStatus

INFO: Job ID: 21 Status: Error

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory

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

---

2@@Msg is Error while executing the Job:Cannot assign an empty string to host variable 4.

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -

---

Background Job History: job id=21, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 4.

Apr 6, 2011 2:46:51 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob

INFO: -

---

Complted Job =>21----

---