- SAP Community
- Products and Technology
- Additional Q&A
- Problems alert generation / AC5.3 SP10
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Problems alert generation / AC5.3 SP10
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-22-2011 2:07 PM
Hi all,
i have a strange issue while trying to run the alert log jobs.
Error:AlertListDAO.sqlj=> ORA-00001: unique constraint (SAPPTFDB.SYS_C005535) violated
com.virsa.cc.alert.bo.AlertListBO.insert(AlertListBO.java:151)
com.virsa.cc.comp.BackendAccessInterface.update_AlertList(BackendAccessInterface.java:3111)
com.virsa.cc.comp.BackendAccessInterface.alertGenerate(BackendAccessInterface.java:2270)
com.virsa.cc.comp.wdp.InternalBackendAccessInterface.alertGenerate(InternalBackendAccessInterface.java:4355)
com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.alertGenerate(InternalBackendAccessInterface.java:4824)
com.virsa.cc.xsys.bg.BgJob.alertGen(BgJob.java:1211)
com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:530)
com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:292)
....
and
-
Error in Alert Generation!----
com.virsa.cc.xsys.bg.BgJob.alertGen(BgJob.java:1219)
com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:530)
com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:292)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:264)
com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:444)
com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1236)
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
....
anyone an idea?
Thanks and best regards,
Christian
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Christian,
There are many reasons for this error.
If you have done a new installation, ensure that the post installation steps are successfully completed.
Also, check the following:
- Ensure that the SP level on Netweaver /Oracle and SAP GRC. If you have have mismatch of the SP's these, you may have similar issues.
- Check all the parameter values in Configuration tab. Ensure that they are updated properly.
- Check if BITMAPINDEX is created on table virsa_cc_prmvl table. Check with your developers to identify the same.
- Please check if you are able to run risk analysis in Foreground mode? If successul, check the table VIRSA_CC_GSEQ, and look for the entry JOBID.
If you don't see a Job ID, then it is the issue with the JOBID. Make sure to have the entry created in the table VIRSA_CC_GSEQ.
You may reach SAP to support on the format of the JOBID.
Check SAP note 1463294 & 1435605 for further reference.
Regards,
Raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Raghu,
checked everything and implemented the note via snote. There is no problem with the background jobids. I can run riskanalysis jobs in the background without any problems.
On the alert monitor tab I can see results for conflicting actions and critical actions - but not for control monitoring.
I knew these controls have never been performed. But they won't show up. Is there anything I have to setup in backend? All the jcos etc. are working fine. Do I have to schedule a job for control monitoring in backendß
Thanks!!
Christian
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
FINEST: Analysis Daemon started background Job ID:114 (Daemon ID /usr/sap/PTF/JC13/j2ee/cluster/server0/. Thread ID 2)
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
-
Scheduling Job =>114----
-
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob run
INFO: --- Starting Job ID:114 (GENERATE_ALERT) - control monitoring
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 114 Status: Running
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
-
1@@Msg is control monitoring started :threadid: 2
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
-
Background Job History: job id=114, status=1, message=control monitoring started :threadid: 2
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Alert Generation Started @@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Conflict Risk Input has 1 records @@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Critical Risk Input has 1 records @@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Mitigation Monitor Control Input has 1 records @@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: @@@@@ Backend Access Interface execution has been started @@@@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
WARNING: Error:
com.virsa.cc.rulearchitect.dao.DAOException
at com.virsa.cc.alert.bo.AlertLogBO.insert(AlertLogBO.java:143)
at com.virsa.cc.comp.BackendAccessInterface.alertGenerate(BackendAccessInterface.java:1964)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.alertGenerate(InternalBackendAccessInterface.java:4355)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.alertGenerate(InternalBackendAccessInterface.java:4824)
at com.virsa.cc.xsys.bg.BgJob.alertGen(BgJob.java:1211)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:530)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:292)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:264)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
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:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
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)
Aug 26, 2011 3:08:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: ==$$$===Notif Current Date=>2011-08-26==$$$==Notif Current Time=>15:08:32===$$$===
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: Start AlertStats.............
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: MSG:Error in Statics Record BAPI Call!
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
WARNING: @@@=== Error in Alert Generation!===@@@
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob run
WARNING: *** Job Exception: -
-
Error in Alert Generation!----
-
com.virsa.cc.rulearchitect.dao.DAOException: -
-
Error in Alert Generation!----
-
at com.virsa.cc.xsys.bg.BgJob.alertGen(BgJob.java:1219)
at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:530)
at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:292)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:264)
at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
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:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
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)
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 114 Status: Error
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
2@@Msg is Error while executing the Job:----
Error in Alert Generation!----
-
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: -
-
Background Job History: job id=114, status=2, message=Error while executing the Job:----
Error in Alert Generation!----
-
Aug 26, 2011 3:08:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
-
Complted Job =>114----
-
Edited by: Christian Hofmann on Aug 26, 2011 3:09 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Christiana,
I see some configuration issues with the Alert jobs. You can find out the same from the log which says the same.
I further recommend to go through the SAP Note 1015921 - Collective note for Alerts Log not capturing data
This is an excellent note that helps you to check every corner to make sure that the Alert configuration is proper.
Hope this will help you in resolving the issue.
Regards,
Raghu
Answers (0)
- IoT - Ultimate Data Cyber Security - with Enterprise Blockchain and SAP BTP 🚀 in Technology Blogs by Members
- Kyma Integration with SAP Cloud Logging. Part 2: Let's ship some traces in Technology Blogs by SAP
- SAP HANA Cloud Vector Engine: Quick FAQ Reference in Technology Blogs by SAP
- SAP Document and Reporting Compliance - 'Colombia' - Contingency Process in Technology Blogs by SAP
- UNVEILING THE INNOVATIONS OF ARTIFICIAL INTELLIGENCE in Technology Q&A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.