/virsa/ZVFATBAK background job

Hello,
SAP 4.6c.
/virsa/ZVFATBAK is running currently in the system at specific periods.
Should this job be running on each application server of the system?
Or just a one time schedule in SM36 for the entire system is good.
Kindly advise.
Thanks.
Prasanna

Hello,
Thanks for the reply.
Recently, the frequency of the job was switched from hourly to once every 4 hours.
The firefighter logs are not getting generated.
I dont see anyother changes that have been made.
1039144-Is this note the solution?
thanks.
Prasanna

Similar Messages

  • Error while opening the file in Background job in Virsa.

    We are using Virsa 5.2
    I click on the result tab to view the job results.(informer->Background job) I am getting this message.
    Mar 3, 2008 1:49:15 PM com.virsa.cc.comp.GenericRAReportView wdDoModifyView
    WARNING: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)java.io.FileNotFoundException: .\virsa\bgJobSpool\16.i (The system cannot find the file specified)
    Can you please let me know?
    Nothing has been changed including my user profile.
    From,
    PT.

    Hi,
    Here are number of notes that I have listed out to sort some issues on SAP GRC 5.2 .
    There is a note for background daemon issue as well
    Installation
    Note 1009509 - VIRSANH 5.2 Support Packages for BASIS 700
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Post Installation
    Note 1022187 - Compliance Calibrator 5.2 Support Pack
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 1060673 - Configuration of SAP Adapter in CC 5.2
    Note 709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0
    Note 1044173 - Recomended Netweaver Setting for Access Control 5.x
    Note 1044174 - Recommendation for CC 5.x running on Oracle 10G Database
    Note 1121978 - Recommended settings to improve peformance in CC 5x analysis
    Note 978536 - Language Configuration for Virsa Compliance Calibrator 5.2
    Issues
    Note 1008500 - VIRSA 4.0 Support Packages for Basis 700
    Note 999785 - CC Background Daemon will not Start
    Note 987386 - Graphics Rendering Issue in SAP Compliance Calibrator
    Note 1009267 - System ID is not available in drop down menu-CC5.1
    Note 1052455 - Error-No relevant language message available in database
    Note 1062037 - java.lang.NullPointerException error in Adapter activation
    Note 1088378 - CC 5.2 - Undeployment of ccappcomp from SDM fails
    Thanks,
    Uday

  • Fire Fighter job /VIRSA/ZVFATBAK is finishing in zero sec

    Hello Everyone,
    In my Solution Manager Production system FF job /VIRSA/ZVFATBAK is finishing in zero sec.
    Log:
    Date       Time     Message text                                                                        Message class Message no. Message type
    01.04.2014 02:30:33 Job started                                                                              00           516          S
    01.04.2014 02:30:33 Step 001 started (program /VIRSA/ZVFATBAK, variant &0000000000002, user ID DE15386)      00           550          S
    01.04.2014 02:30:33 Job finished                                                                             00           517          S
    Please suggest what could be thepossible reason.
    I am not able to get FF logs. So is this job the reason for no logs?
    Thanks,
    Ashish Gaurav

    Hi Tang,
    Did you check the configuration settings for both the FF IDs.
    Also, as a trail and error, to isolate the issue, can you check using only the 2nd FF ID for which the log was not sent. Ensure that the 1st FF ID is not used. This way you can identify whether the issue is with the FF ID or the configuration.
    Regards,
    Raghu

  • Job cycle for Prog. /VIRSA/ZVFATBAK for GRC

    Hi Experts,
       I want to know JOB cycle for Prog. /VIRSA/ZVFATBAK for GRC.
       Please advice the matter.
    Regards,
      Gaito

    Hi,
    This job scheduled every hour.
    Check SAP Note 1039144 - Superuser job is not completing or is not retrieving data
    Thanks
    Sunny

  • BCD_OVERFLOW CX_SY_CONVERSION_OVERFLOW /VIRSA/ZVFATBAK

    Hi guys,
    I have my FF user executing transaction SE38 and upon the execution, the background job /VIRSA/VFATBAK ended in status "Canceled". In the log, its shows the below description for the background job cancallation.
    Short text
    Overflow during an arithmetic operation (type P) in program "/VIRSA/ZVFATBAK".
    What happened?
    Error in the ABAP Application Program.
    The current ABAP program "/VIRSA/ZVFATBAK" had to be terminated because it has come across a statement that unfortunately cannot be executed. A value is too long for a calculation field.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not caught in
    procedure "GET_SE38_CHANGES" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is:
    In the current arithmetic operation with operands of type P an overflow has been detected. Possible causes are:
    1. The result field of type P is too small to store the result.
    2. The result or an intermediate result has more than 31 decimal places.
    How to correct the error
    Maybe the result field - if still possible - must be defined larger.
    Maybe the current process can be divided into separate units in a way that only smaller values occur.
    Anyone shares this experience before and if you have resolve it via the proposed way to coorect the error?
    If you have successfully executed the corrections, can you pls share on the steps to be taken?
    Thanks.
    Raymond

    An calculation causes an exception because the result variable is too short to store the result.
    You can 2 things to solve the problem :
    - Add an error handling mechanisme CATCH or TRY to get the exception and act on it (message or something else)
    - change the result variable so that it can store the resulting value
    regards,
    hans

  • BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED

    Hello,
    To generate the log report, /VIRSA/ZVFATBAK program is scheduled on hourly basis but some time report doesn't get generated and if we see the background job then it shows sucessfully finished.
    If we see the maually the log report for FFID then below error message is displayed.
    " BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED"
    Can anyone guide me to solve the issue.
    Thanks in advance.
    Best Regards,
    Prashant Dubey

    Hi,
    once chk the status of the job by selecting that and check job status(cltr+shift_f12)
    since it was periodically scheduled job there will be a RELEASED job after every active job..
    so try to copy that into another job using copy option and give some new name which u have to remember...
    the moment u copy u can find the same copied job in SCHEDULED status...
    from here, try to run it again on hourly basis....
    After copying the job u can unschedule the old released job to scheduled otherwise 2 will run at a time...
    rgds,

  • Run VIRSA/ZVFATBAK to generate missed log

    Hello experts, we had an upgrade a couple weeks ago and we had to put the VIRSA/ZVFATBAK job on hold. Because of this we have a couple of FF logons missing data. We have the "BACKGROUND JOB WAS NOT SCHEDULED/LOG & FILE NOT YET GENERATED" error. Usually I can run job immediately after the upgrade and gather this missed data, however this time we forgot and now trying to go back 3 weeks ago.
    I thought since I can still see the data in STAD (ST03) I should be able to get VIRSA/ZVFATBAK to run and find the data. This is not the case this time. Can anyone confirm its too late to generate these missed logs?
    Thanks
    Dave Wood

    Hi David,
    If you see that logs are missing for certain date and time then you can run the report  /VIRSA/ZVFATBAK with date and time for which logs where missing, see sap note - 1142312 (read this to understand what start & read time should be given to run the report)                                                                               
    Please be informed that the report will fetch data from STAT and CDHDR, CDPOS only if the data exists in these for the given date and time. If the data has been purged from STAT for that period then its not possible to get the logs.
    Also note this point -   As per design, manual FF log update considers only the firefighter ids
    assigned to the user who is triggering the update through the firefighter dashboard. Whereas the scheduled background job considers all the FFIDs for a particular time period.
    Best Regards,
    Sirish Gullapalli.

  • Log storage time of /VIRSA/ZVFATBAK

    Hi Guys,
    Can any one let me know how many days firefighter stores the logs generated by the background job /VIRSA/ZVFATBAK.
    I have given the user Firefighter ID from june 12th to june 19th. can I generate  a firefighter log on june 28th.
    Kindly respond.

    Hello Rahul,
      The Data which is retrieved by the /VIRSA/ZVFATBAK program is stored in Firefighter tables. If the problem was able to retrieve the data for that particular date successfully from SAP System then it will be available in the logs for review as long as it is in Firefighter tables.
    Regards, Varun

  • GRC PC Background jobs

    Hi,
    I would like to know which all background jobs are required for GRC PC 10
    We would like to schedule it through SM36. Do we also need to create variants for the same?
    Regards,
    Atul

    Hello Abdul,
    Please find the below background jobs which should be scheduled periodically.
    RAR
    1. User/Role/Profile sync incremental jobs.
    2. Batch risk analysi for user/role/profile incremental
    3. Critical action/role/profile incremental
    4. Management jobs.
    Also if your client uses the Alert you can schedule a periodically job for that.
    ERM
    If client is making lot of changes in TCODES and auth objects on daily basis then you can schedule these job as well.
    1. Org value sync
    2. Transaction/object/field sync
    3. Activity value sync.
    SPM
    /virsa/zvfatbak (log report) on hourly basis
    CUP
    All the jobs given in CUP Configuration->background jobs should be scheduled on periodically basis as per your client requirent.
    You can skip few jobs like HR trigger, SOD and UAR if your client is not using this fucntionality.
    Regards,
    Shweta

  • RE: SPM Background JObs

    Dear Experts,
    We have scheduled FF log background jobs (/VIRSA/zvfatbak) to execute for every hours. What happens if the job is not completed in two hours, will the second execution waits until the 1st execution is completed?
    Please advise.
    Thanks,
    Raj

    Hi Raj.
    I assume this is for GRC AC 5.2/3 and your concern is of potential loss of log data from not being recorded.
    Usually, an hourly job is set up (as you have done, which actually reads the previous 62 minutes of activity), but I have also seen clients set up additional jobs as a precautionary measure to ensure that all data is captured in the case of system or job scheduling issues, i.e. create a job that runs every four hours (with a read time of four (4) hours) or at the end of the day (with a read time of twelve (12) hours) in addition to having the regular hourly job scheduled. This usually works well.
    There is more details of covering such scenarios in SAP note 1039144 "Superuser job is not completing or is not retrieving data" https://service.sap.com/sap/support/notes/1039144
    Hope that helps.

  • Error while scheduling Background Job for User/Role Full Synchronization

    Hi all,
    We have installed RAR 5.3 Component and uploaded the authorization data & established the connectors to the backend system.
    We have performed all the post installation activities and everything is complete.
    When we have scheduled User -Full Synchronization with the Back End system as  a part of Post Installation Activity we are receiving the below error message
    "Error while executing the Job:Cannot assign an empty string to host variable 2."
    Also the VIEW LOG/ Terminate Job buttons are disabled  in this screen.
    Can somebody please help us in resolving the above issue
    Thanks and Best Regards,
    Srihari.K

    Hi,
    We are copy pasting the error log (Part as it is huge) below here. We could able to do Full Synch for Roles and also for Profiles. Only for User Synch we are getting this error and none of the users are sychronized to RAR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WILSONA of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WINDC of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WLADICHJ of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user WUK of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZENGS of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: Update user ZHENGL of HL2-QAHR
    Jan 13, 2009 12:34:27 AM com.virsa.cscext.dao.CSCDAO populateGenObjUser
    INFO: All System Flag:false=====Last Batch Flag:true
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis loadUserData
    INFO: @@@ User sync completed for params true: Syskey List is [HL2-QAHR]
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob run
    WARNING: *** Job Exception: Cannot assign an empty string to host variable 2.
    com.sap.sql.log.OpenSQLException: Cannot assign an empty string to host variable 2.
         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.cscext.dao.CSCDAO.updateIgnoredUserData(CSCDAO.java:1388)
         at com.virsa.cscext.dao.CSCDAO.populateGenObjUser(CSCDAO.java:1169)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.populateGenObj(BatchRiskAnalysis.java:868)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.insertBAPIUserData(BatchRiskAnalysis.java:142)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.loadUserData(BatchRiskAnalysis.java:390)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1275)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         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:319)
         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(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 13 Status: Error
    Jan 13, 2009 12:34:27 AM 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 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=13, status=2, message=Error while executing the Job:Cannot assign an empty string to host variable 2.
    Jan 13, 2009 12:34:27 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: -
    Complted Job =>13----
    Please let us know how to resolve this error
    Thanks and Best Regards,
    Srihari.K

  • Format of Date Field in RAR background job history page

    Hi Everyone,
    Is it possible to customize the format of the fileds: "last run", "next start" in RAR background job history page?
    By default it is in the format yyyy-mm-dd.
    I am just wondering my customer's requirement is possible or not?

    Hi,
    There is no option to set the date format in the Configuration settings. Check the FM /VIRSA/ZCC_GET_STATREC_DATA which has the CALL FUNCTION 'GET_SYSTEM_TIMEZONE'. RAR will read the time from the system.
    You may look at formatting the the date format here.
    Hope this helps!!
    Warm Regards,
    Raghu

  • Background job not invoking in CC.

    hi,
    I am facing a problem in running background job in CC. Actually its invoking a wrong url and when i am checking in application deployed url is different.
    We are at CC SP9.
    Url invoked is "is http://hostname:51700/webdynpro/dispatcher/virsa/ccappcomp/BgJobStart?daemonId=/usr/sap/FAP/DVEBMGS17/j2ee/cluster/server1/.&threadId=4&daemonType=WS
    As per deployment
    Url should be "http://chmsxp41.eame.syngenta.org:51700/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart"
    Please suggest.
    Thanks & Regards,
    Pravin

    Please check SAP Note 999785.
    Somewhere between SP04 and SP06 the URL changed, and you need to re-configure that on database level (change "virsa/ccappcomp" to "sap.com/grc~ccappcomp").
    Frank.

  • What data is stored in the CC Background Job Spool File?

    What information is stored in the location referenced in the CC Configuration/Miscellaneous setting of 'Background Job Spool File Location'?  Our test and production versions of this system are configured the same, with both pointing to the same location on their respective servers.  However the test location shows a virsa/bgJobSpool folder in it containing multiple files while our production system shows this location as empty.
    Both versions seem to be working OK.  We are running backgrounds jobs in each (risk analysis, management reviews, rule generation, etc.) and seeing results.
    We updated to the GRC 5.2 a few months ago and are currently on SP9.  This issue came up during a system audit, so we need to come up with an explanation for the differences.
    Thanks.

    I had reviewed that SAP note previously, but it does not seem to help any with our situation.  We are running ad hoc background risk analysis jobs frequently and can always see the results.  Everything seems to work fine from the application side, we just don't see the logs where we thought they should be over on the server.
    From the outside, it looks like maybe it is ignoring the configuration setting and is still using the default location for the log.  Does it need to be on the same drive as the application?  I believe our application and the default location are both on our E drive, but we want to put the location for this and the Alert Log on the D drive.
    Thanks.

  • ABAP report /VIRSA/ZVFATBAK run very long on backend

    Hello experts,
    For ABAP report /VIRSA/ZVFATBAK which runs in the backend system, normally how long would it take to finish? Because now the duration for the report is already 2k++ seconds and its still running in our test system, while the report scheduled in our development system only uses 1 or 2 secs to finish.
    Any idea why is it taking that long in a test system?
    Appreciate the replies, thank you in advance.

    Thank you for the note sabita! Its really helpful.
    One question regarding the sapnote, it mentioned STAT collector job, is this a standard job?
    If yes, below are the standard collector jobs which is scheduled in the system, which would it be?
    SAP_COLLECTOR_FOR_JOBSTATISTIC
    SAP_COLLECTOR_FOR_NONE_R3_STAT
    SAP_COLLECTOR_FOR_PERFMONITOR

Maybe you are looking for