on 12-04-2012 10:16 AM
SAP GRC RAR BG Mangmnt jobs are showing completed status,but when I check in Log file, it shows same error message.
Error Log:
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
FINEST: Analysis Daemon started background Job ID:2240 (Daemon ID
[505214651]/usr/sap/YXX/DVEBMGS50/j2ee/cluster/server1/. Thread ID 0)
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -----------------------Scheduling Job
=>2240---------------------------------------------------------------
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.bg.BgJob run
INFO: --- Starting Job ID:2240 (RISK_ANALYSIS_BATCH) - mgmt reports - YRSCLNT100
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1007
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 2240 Status: Running
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.bg.BgJob findJobHistory
FINEST: --- @@@@@@@@@@@ Find the Job History ----1
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1007
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis
INFO: --- Batch Sync/Analysis/Mgmt Report started ---
Nov 21, 2012 8:37:01 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis runBkgMgmReport
INFO: --- Running the Background Management Report ------
Nov 21, 2012 8:38:12 AM com.virsa.cc.xsys.mgmbground.dao.MgmStats execute
INFO: Start insert int cc_mgriskd all violations.... 1353483492598
Nov 21, 2012 8:38:13 AM com.virsa.cc.xsys.util.Lock lock
WARNING: It is used by the another owner: For current thread retrying to get lock : 1004
Nov 21, 2012 8:38:14 AM com.virsa.cc.xsys.util.Lock lock
WARNING: It is used by the another owner: For current thread retrying to get lock : 1004
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.util.Lock lock
FINEST: Lock:1004
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.util.Lock unlock
FINEST: Unlock:1004
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis runBkgMgmReport
WARNING: Exception in Management Report Job: ORA-00001: unique constraint
(SAPSR3DB.SYS_C00169234) violated
com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00169234)
violated
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.bg.BgJob run
WARNING: *** Job Exception: ORA-00001: unique constraint (SAPSR3DB.SYS_C00169234) violated
com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00169234)
violated
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)
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 2240 Status: Error
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History ----2@@Msg is Error while executing the
Job:ORA-00001: unique constraint (SAPSR3DB.SYS_C00169234) violated
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO: ----------- Background Job History: job id=2240, status=2, message=Error while
executing the Job:ORA-00001: unique constraint (SAPSR3DB.SYS_C00169234) violated
Nov 21, 2012 8:47:01 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -----------------------Complted Job
=>2240---------------------------------------------------------------
As per Google search, we applied below note for this issue, but still we have same issue
SAP Note 1463294 - Failed to schedule background job ORA-00001"
Again we analyse and found that, need to apply below SAP Notes for this issue
1512688 - Introducing RAR Netweaver Server Logical Locks.
( Need to enable Logical Locks: Go to Configuration >> Performance Tuning >> "Use Netweaver logical
lock" and choose "Yes" option to enable this.)
1652240 - Executing Batch Risk Analysis results in Unique Constraint Errors
1463294 - Failed to schedule background job ORA-00001 - Already Applied
Can you please check error log file and suggest how can i process further.
And
I also just found one other issue that I think is related. The screenshots below show that the Production Management Report in GRC isn't reflecting properly. The report shows that a user has a SOD conflict but the real time report shows the user doesn't have any conflicts. I don't think the GRC Management Report is reflecting properly, possibly due to the Notes above? Please suggest
GRC Management Reports
Real-Time
Good day Nagaraju.
The Management Reports check shouldn't to apply in all Jobs. Each INITIAL BGJob must be independent.
**User, Role, Profile Synchronization
(1) User Synchronization with Sync Mode FULL
(2) Role Synchronization with Sync Mode FULL
(3) Profile Synchronization with Sync Mode FULL
**Batch Risk Analysis
(4) User Analysis with Permission Level Analysis & Management Reports check
(5) Role Analysis with Permission Level Analysis & Management Reports check
(6) Profile Analysis with Permission Level Analysis & Management Reports check
(7) Critical Action and Role/Profile Analysis w/Permission Level Analysis &Management Reports check
Notes:
-Each Job has that done without errors for to prepare another next BGJob. For this, review "View Log" option
-The "Action Level Analysis" check level isn't adivsable.
- If you faced Memory issues about BGJob contect, please review SAP Note 1044173.
- If you faced long time in BGJob, can to exclude User, Roles or Profiles. Only apply for INITIAL BGJobs.
Erick Verbena
PROLAMSA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good day Nagaraju.
How scheduling the RAR Jobs?
Erick Verbena
PROLAMSA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.