Job status is Job canceled while Executing Campaign

Hi,
i executed a campaign with target group(having 4 BP's).after executing campaign in messages assaignment Block it is showing execution successful.
But in segments the job status is showing Job canceled.in my scenario i am using Communication medium is Email.
presently i am working for CRM 7.0
can u please help me where this error is coming
Thanks in Advance
kishor Kumar

Hi Kishore,
As dipesh said check the following:
1- Tx- SCOT, check SMTP correct Mail Host and Supported address type of Internet
2- You can check for pending mails using Tx-SOST as well and analyse.
3- Check the errors if any with BPs.
Regds...
Arup

Similar Messages

  • Error while executing the Job for Objects :null  Batch Risk Analysis

    Hi All,
    We've recently upgraded Virsa to version  5.3_14 .  I'm encountering a problem when executing the Batch Risk Analysis job for users, roles and profiles.  The job does not complete for some objects and it seems to be sporadic and shows this error: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null                                                                               
    I've attached the log for your review.
    Thanks in advance for your help.                                                                               
    Linda Lewis                                                                               
    Feb 9, 2011 1:47:53 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 4ms, #singles=2141, #ranges=0, #super=0
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    WARNING:  Job ID:395 : Failed to run Risk Analysis
    java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1019)
    at com.virsa.cc.xsys.util.RuleLoader.getPermRule(RuleLoader.java:573)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1609)
    at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:321)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1166)
    at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1464)
    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:332)
    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:207)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    WARNING: Error: while executing BatchRiskAnalysis for JobId=395 and object(s):ABROWN: Skipping error to continue with next object: null Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=395, status=2, message=Error while executing the Job for Object(s) :ABROWN:null
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    FINEST: Lock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock unlock
    FINEST: Unlock:1004
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    INFO: --- BKG User Permission Analysis (System: P20:020) completed ---  elapsed time: 4522 ms
    Feb 9, 2011 1:47:54 PM com.virsa.cc.xsys.util.Lock lock
    Edited by: Linda Lewis on Feb 9, 2011 9:08 PM

    Hi,
    Was a solution found for this error?
    Thanks,
    Glen

  • Displaying Jobs Status and Logs without using SM37

    Hello All,
    First of all, thanks a lot for your time.
    We're being asked by the Audit Team to remove tcode SM37 from our Job Roles. Although I agree with them that users should not have "change" or broad display access for the tcode, some of them need to check other user's Jobs status, as well as their Job Logs (which I have managed to restrict using auth. object S_BTCH_JOB).
    My question is: do you know if there's any alternative way or a transaction different than SM37 to display other user's Jobs status and Job Logs?
    We're providing SMX for user's own jobs, but I have not been able to find an alternative way than using a restricted version of SM37 for displaying other people's Jobs status and Job Logs.
    Best regards,
    CMPT

    You can either create your own monitor locally ( see transaction RZ20) or develop it on your own (see FM BP_JOB_STATUS_GET).
    If you want to use SM37 then you can add SHOW to S_BTCH_JOB but this might be problematic in combination with RELE (of their own jobs).
    [SAP Note 568963|https://service.sap.com/sap/support/notes/568963] will be able to help you further.
    Cheers,
    Julius

  • Tidal Enterprise Scheduler - Get Job status using c#

    Is it possible to get the list of jobs scheduled and their status in Tidal Enterprise scheduler using a programming language like C# ?

    API depends on your version and you need to have the client installed from Server/DEsktop initiating the API
    the PDF document should have been included on you CD2 called Command Line Program Guide
    I will use 5.3.1 as an example:
    open a command prompt
    Browse to C:\Program Files (x86)\TIDAL\Scheduler\client
    type in set alias=DEV > example=DEV otherwise it defaults to Admiral
    type in SACMD
    type  HOST I always type in HOST so I can verify what master I am running against (nio need if only one connection)
    type in jobmon with your options I included below from doc
    [-d date] +display_options [filtering_options] [-b]
    It may be of limited use in 5.3.1 because to isolate you need to know Job ID or Alias or some other filter critiera... Job ID is in database jobmst.dbo.jobmst_id which is the unique identified and can be different from alias... depending on your  requirements (dashboard?) and how you have organized your jobs a SQL query would be the better option. 
    DISPLAY
    r
    Job rule ID
    i
    Job run ID
    p
    Parent job group ID
    j
    Job type (job or job group)
    c
    Occurrence number
    o
    Job or job group owner
    u
    Runtime user
    h
    Agent The Agent the job runs on
    z
    Scheduled vs. unscheduled job
    t
    Job start time
    s
    Job status
    v
    Job duration
    n
    Job name
    a
    Job alias
    q
    Queue
    x
    Exit code
    FILTER
    -r
    rule_id Job rule ID
    -p
    group_id Parent job group ID
    -j
    type Job type. You can choose: job group: group, or 1 job: Job, or 2
    -o
    owner Job or job group owner
    -u
    run_user Runtime user
    -h
    agent The Agent name the job runs on
    -s
    job Status ( Completed Abnormally=103, Normal=101)
    -a
    alias Job alias
    -x
    exit_code Exit code
    -b
    Suppresses the header information

  • Problems creating background job for program (job open, submit and close)

    Hi gurus,
    im trying to start a background job using the FM BP_START_DATE_EDITOR to show the start date to the job or if it's imediate. this FM it's working fine, after call it im opening a job, submiting it and call the job close FM and the job close FM creates me the job.
    The problem it's when i go to the sm37 to see the job status the job has been canceled, and the job log says that i have to give a start date to the job.
    What i dont understand it's either the job is imediate or i choose a date to start the job always gives me this error...
    Below goes my code,
    any ideas will be rewarded
      CLEAR: stdt_modify_type, stdt_output.
      CALL FUNCTION 'BP_START_DATE_EDITOR'
           EXPORTING
                stdt_dialog                    = 'Y'
                stdt_input                     = stdt_input
                stdt_opcode                    = 14
           IMPORTING
                stdt_modify_type               = stdt_modify_type
                stdt_output                    = stdt_output
           EXCEPTIONS
                fcal_id_not_defined            = 1
                incomplete_last_startdate      = 2
                incomplete_startdate           = 3
                invalid_dialog_type            = 4
                invalid_eventid                = 5
                invalid_opcode                 = 6
                invalid_opmode_name            = 7
                invalid_periodbehaviour        = 8
                invalid_predecessor_jobname    = 9
                last_startdate_in_the_past     = 10
                no_period_data_given           = 11
                no_startdate_given             = 12
                period_and_predjob_no_way      = 13
                period_too_small_for_limit     = 14
                predecessor_jobname_not_unique = 15
                startdate_interval_too_large   = 16
                startdate_in_the_past          = 17
                startdate_is_a_holiday         = 18
                startdate_out_of_fcal_range    = 19
                stdt_before_holiday_in_past    = 20
                unknown_fcal_error_occured     = 21
                no_workday_nr_given            = 22
                invalid_workday_countdir       = 23
                invalid_workday_nr             = 24
                notbefore_stdt_missing         = 25
                workday_starttime_missing      = 26
                no_eventid_given               = 27
                OTHERS                         = 28.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MOVE 'X' TO gv_flag.
      ENDIF.
      DATA jobname LIKE tbtcjob-jobname.
      DATA jobcount LIKE tbtcjob-jobcount.
      DATA job_release LIKE  btch0000-char1.
      DATA job_imediate TYPE c.
      CLEAR: jobname, jobcount, job_release.
      CONCATENATE 'MAPAEXEC' sy-uname sy-datum
                   INTO jobname SEPARATED BY space.
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = jobname
           IMPORTING
                jobcount         = jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ENDIF.
      SUBMIT z_mapa_execucao_orcamental
             VIA JOB jobname NUMBER jobcount
             WITH ano EQ ano
             WITH so_perio IN so_perio
             WITH so_date IN so_date
             WITH so_org EQ so_org
             WITH so_num IN so_num
             AND RETURN.
      IF stdt_output-startdttyp EQ 'I'.
        CLEAR job_imediate.
        job_imediate = 'X'.
      ENDIF.
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                calendar_id                 = stdt_output-calendarid
                event_id                    = stdt_output-eventid
                event_param                 = stdt_output-eventparm
                event_periodic              = stdt_output-periodic  "?
                jobcount                    = jobcount
                jobname                     = jobname
                laststrtdt                  = stdt_output-laststrtdt
                laststrttm                  = stdt_output-laststrttm
                prddays                     = stdt_output-prddays  "??
                prdhours                    = stdt_output-prdhours  "?
                prdmins                     = stdt_output-prdmins  "??
                prdmonths                   = stdt_output-prdmonths
                prdweeks                    = stdt_output-prdweeks  "?
                predjob_checkstat           = stdt_output-checkstat
                pred_jobcount               = stdt_output-predjobcnt
                pred_jobname                = stdt_output-predjob
                sdlstrtdt                   = stdt_output-sdlstrtdt
                sdlstrttm                   = stdt_output-sdlstrttm
                strtimmed                   = job_imediate
                targetsystem                = stdt_output-instname
                start_on_workday_not_before = stdt_output-notbefore
                start_on_workday_nr         = stdt_output-wdayno
                workday_count_direction     = stdt_output-wdaycdir
           IMPORTING
                job_was_released            = job_release
           EXCEPTIONS
                cant_start_immediate        = 1
                invalid_startdate           = 2
                jobname_missing             = 3
                job_close_failed            = 4
                job_nosteps                 = 5
                job_notex                   = 6
                lock_failed                 = 7
                OTHERS                      = 8.
      IF sy-subrc <> 0.
        MESSAGE i003(zmapas).
        EXIT.
      ELSE.
        MESSAGE i004(zmapas) WITH jobname.
      ENDIF.
    Thanks in advance,
    Best Regards
    João Martins

    Hello João.
    In debug mode, check the value of variables you passed to parameters sdlstrtdt and sdlstrttm.
    As aditional info, I usually achieve your goal without FM BP_START_DATE_EDITOR.
    Check this code:
    CALL FUNCTION 'JOB_OPEN'
          EXPORTING
               jobname          = w_jobname
          IMPORTING
               jobcount         = w_jobcount
          EXCEPTIONS
               cant_create_job  = 1
               invalid_job_data = 2
               jobname_missing  = 3
               OTHERS           = 4.
    CHECK sy-subrc = 0.
    CLEAR seltab_wa.
    MOVE: t_jobs-param TO seltab_wa-selname,
    t_processar-line+34 TO seltab_wa-low.
    APPEND seltab_wa TO seltab.
    seltab_wa-selname = 'P_LOJA'.
    seltab_wa-low = t_processar-ficheiro+7(4).
    APPEND seltab_wa TO seltab.
    *** Submete o programa para o JOB
    SUBMIT (t_jobs-repid)
      WITH  SELECTION-TABLE seltab
      USER sy-uname
       VIA JOB w_jobname NUMBER w_jobcount
       AND RETURN.
    *** Encerra o JOB
      l_hora = sy-uzeit.
      ADD 60 TO l_hora.
    CALL FUNCTION 'JOB_CLOSE'
       EXPORTING
          jobcount           = w_jobcount
          jobname           = w_jobname
          sdlstrtdt            = sy-datum
          sdlstrttm           = l_hora
          targetserver       = w_servidor
       IMPORTING
          job_was_released     = l_liberado
       EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          OTHERS               = 8.
    Regards.
    Valter Oliveira.

  • Error while executing Batch Risk Analysis job in full sync mode

    Hi Gurus,
    I am getting following error while executing Batch Risk Analysis job in full sync mode for the first time, please help me out.
    May 12, 2011 3:57:26 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
    INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
    May 12, 2011 3:59:53 AM com.virsa.cc.multi.node.dao.NodeDAO deleteMTGenObjTable
    INFO: In deleteMTGenObjTable() deleting from VIRSA_CC_MTGENOBJ for jobid = 100
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchSyncAndAnalysis
    INFO: --- Batch Sync/Analysis/Mgmt Report completed ---  elapsed time: 104907817 ms
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob setStatus
    INFO: Job ID: 100 Status: Error
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error Job not completed
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=100, status=2, message=Error Job not completed
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: -
    Complted Job =>100----
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
    INFO: Daemon idle time longer than RFC time out, terminating daemon [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0
    May 12, 2011 3:59:53 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 terminiated
    May 12, 2011 4:00:35 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:01:36 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:02:37 AM com.virsa.cc.xsys.bg.AnalysisDaemonThread run
    FINEST: Analysis Daemon Thread: Invoking (HTTP): http://10.66.218.68:52100/webdynpro/dispatcher/sap.com/grc~ccappcomp/BgJobStart?daemonId=[211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/.&threadId=0&daemonType=BG
    May 12, 2011 4:02:37 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    INFO: Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 started
    May 12, 2011 4:02:38 AM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob start
    FINEST: Another Analysis Daemon ID [211288050]/usr/sap/DAC/JC21/j2ee/cluster/server0/. Thread ID 0 is already running

    Hi,
    May be it worked in your case How the job names going to affect the execution of the job. The issue is purely because of RFC timeout (As per the logs). I recommend to change the parameter in the configuration tab as recommended by Sunny in the previous thread.
    Regards,
    Raghu

  • Campaign Element execution and job status

    Hello SAP Gurus,
    I have a requirement, where the Client wants to execute the Campaign Element. Is that possible?
    He also says, the end user should execute the Campaign element level.
    I tried doing that, but the Job status remains as "JOB NOT SCHEDULED".
    *Is it a technical error or settings to be done at the back end ?
    Kindly help me out.
    Thanks in advance.
    Regards,
    Srinivasan Raghavendran

    Hi Srinivasan,
    You can execute Campaign elements individually but you have to make sure that u r all uppel level marketing Plan, Campaign should be released first, Job remains not scheduled due to various reasons. if u r running mail campaign then check the target group which u r assigning to campaign has email id maintained also check for mail form maintained. 
    For job please check Start date if u r running periodic job then the condition must be fullfilled, for test try running job with  Start date as Immidiate
    Regards,
    DD's

  • Global Enqueue Services Deadlock detected while executing job

    Hi Gurus,
    Need your help in analying below situation.
    I got a Global Enqueue Services Deadlock in our 2-node RAC stating deadlock detected due to auto execute of job. But when I checked job status its was executed successfully. Also, the trace files gives some session id , client id which I am not able to mapped to any particular instance. trace files output as below. What would be the approach for such situtation and how to find the relevant sql which caused such deadlocks.
    ENV - 11gR2 RAC 2-node with ASM
    Linux RHEL 6.2
    Trace File output
    Trace file /diag/app/ora11g/diag/rdbms/remcorp/REMCORP1/trace/REMCORP1_j001_25571.trc
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Real Application Clusters and Automatic Storage Management options
    ORACLE_HOME = /u01/app/ora11g/product/11.2.0/db_1
    System name: Linux
    Node name: remedy-ebu-db1
    Release: 2.6.32-220.el6.x86_64
    Version: #1 SMP Wed Nov 9 08:03:13 EST 2011
    Machine: x86_64
    Instance name: REMCORP1
    Redo thread mounted by this instance: 1
    Oracle process number: 38
    Unix process pid: 25571, image: oracle@remedy-ebu-db1 (J001)
    *** 2013-05-17 02:00:34.174
    *** SESSION ID:(1785.23421) 2013-05-17 02:00:34.174
    *** CLIENT ID:() 2013-05-17 02:00:34.174
    *** SERVICE NAME:(SYS$USERS) 2013-05-17 02:00:34.174
    *** MODULE NAME:() 2013-05-17 02:00:34.174
    *** ACTION NAME:() 2013-05-17 02:00:34.174
    ORA-12012: error on auto execute of job 83
    ORA-00060: deadlock detected while waiting for resource
    ORA-06512: at "ARADMIN.CMS_CUSTOMER_DETAILS", line 3
    ORA-06512: at line 1
    Regards,
    Nikhil Mehta.

    Look at your alert.log, search for messages such as this:
    Wed Jun 16 15:05:58 2010
    Global Enqueue Services Deadlock detected. More info in fileSearch for the .trc file mentioned and opened it, it should have all the info you need.
    Even on the error you posted, you already have some very important information:
    ORA-06512: at "ARADMIN.CMS_CUSTOMER_DETAILS", line 3In short, you have another job, or a query that runs at the same time as your job which wants to do some DML on rows of that table and at the same time your Job wants to do some DML on another set of rows tha table the query has locked first.
    As in:
    a) Query/Job X Locks some rows of ARADMIN.CMS_CUSTOMER_DETAILS.
    b) Your job locks some rows of ARADMIN.CMS_CUSTOMER_DETAILS.
    c) Your job wants the lock on the rows that X has locked first.
    d) X wants the lock on the rows your job has locked first.
    e) Deadlock.
    So if I have something you want, and you have something I want, we are both "deadlocked" thus LMD comes in and kill one of us to resolve the impass. It's probably killing the X job/query and so that's why your job is still executing successfully.
    So you have two options:
    1) Identify the X Job/Query -- either stop it or change it's execution time
    2) Your job - either stop it or change it's execution time

  • Job cancelled While loading data from DSO to CUBE using DTP

    Hi All,
      while i am loading data frm DSO to CUBE the job load is getting cancelled.
    in the job overview i got the following messages
        SYST: Date 00/01/0000 not expected.
       Job cancelled after system exception ERROR_MESSAGE
    wt can be the reason for this error as i have successfully loaded data into 2 layers of DSO before loading the data into the CUBE

    hi,
    Are u loading the flat file to DSO?
    then check the data in the PSA in the date field and replace with the correct date.
    i think u r using write optimised DSO which is similar to PSA it will take all the data from PSA to DSO.
    so clear the data in PSA and then load to DSO and then to CUBE.
    If u dont need a date field in CUBE then remove the mapping in transformation in cube and activate and make DTP activate and trigger it it will work.

  • Short dump while executing job SM:EXEC SERVICES for EWA alert generation

    Hello All,
    I'm getting short dump error while executing job SM:EXEC SERVICES for EWA alert generation.I'm using EHP1@SP22 of Sol Man.
    Please find the logs
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "RDSVASCABAP_TRANS__________073
    " in include "RDSVASIABAP_TRANS__________073 " in
    line 1782:
    "Field "STATEMENT_SUMMARY001019" is unknown. It is neither in one of th"
    "e specified tables nor defined by a "DATA" statement. "DATA" statement"
    The include has been created and last changed by:
    Created by: "SAP "
    Last changed by: "SAP "
    Error in the ABAP Application Program
    The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    If anyone came across such kind of dump, please reply asap, due to this, i could not generate EWA report for R/3 system 6.04.
    Thanks,
    Anand.

    >
    Anand Tigadikar wrote:
    > Thx Paul, but i already did checked this note and its not solving my issue
    Dear Anand,
    Did you perform a complete service definition replacement for SDCC/SDCCN as described in the note?
    These are manual steps you need to perform on the system and are not code corrections.
    I would suggest you perform it, if you have not, and check the SDCCN logs to review the process ran cleanly.
    Note: Please make sure SDCC_OSS is functioning and a connection to SAP can be made before
    deleting the service definitions.
    If you have already replaced the service defintions on the Solution Manager system, then no point doing it again. However checking a note and applying it are not the same thing. So I am uncertain if you replaced the service definitions or not. The dump you are getting in SM:EXEC SERVICES suggests its due to a problem with the service definitons. The recommendation is to replace them according to the process described in SAP Note 727998. If you have not done so please do so.
    If you have successfully replaced the service definitions are you still getting the same dump, or has it possibly changed?
    Regards,
    Paul

  • Error while executing the Job:Cannot assign NULL to host variable 1

    Hello!
    I have the following issue:
    Error while executing the Job:Cannot assign NULL to host variable 1. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO "VIRSA_... (see log for details)
    Note 1362138 - Rule generation - null pointer exception virsa_cc_rtmap  doesn't me. After uploading files of ZCC_DOWNLOAD_SAPOBJ and ZCC_DOWNLOAD_DESC I got the same problem during job running...
    How can I find out where is the problem?

    Hi
    That looks like your fields are disabled but they could still be causing the problem edited ( nah - talking rubbish as you've put dummy " " in there) edited - the 'null' error caused many background jobs to fail but, once we had the evidence to show the space (somebody had pressed enter instead of delete/backspace to clear the entry) it stopped the problem - just a bit of learning on the job which we all go through for the GRC chaps in KL.
    A " " would be valid but a    (I know you can't see it but it's there wouldn't be      )
    edited.When you did an edit/replace did it say it had replaced anything please?edited
    The word doc option does sound good!
    Cheers
    David
    Edited by: David Berry on Nov 4, 2010 7:33 PM

  • While Executing a Javascript got RuntimeException - org.mozilla.javascript.EvaluatorException: uSetContextVar: Only valid for Provisioning jobs at line

    Hello Experts,
    I am receiving an error whenever i am executing a java script file. I am calling the script in the below fashion.
    MSKEYVALUE  - $FUNCTION.DP_getMskeyValueForUser(%ABCD01%)$$
    function DP_getMskeyValueForUser(Par){
    ---- Here we have written logic---
           var result = uSelect(query);
          result = DP_generateId("CREATE");// calling another script
        return result;
    function DP_generateId(Par){
    --------------Here Code Logic ----------------------
    --------At ending setting the output value and storing it in the context variable
        uSetContextVar("new_mskeyvalue", newMskeyValue);
        return newMskeyValue;
    While executing i am getting an error message at the above highlighted part stating that got RuntimeException - org.mozilla.javascript.EvaluatorException: uSetContextVar: Only valid for Provisioning jobs at the line
    Can you kindly please help me with this error.
    Regards,
    DP

    Hi DP,
    Hope this helps.
    context var is used if you want to pass values between tasks. If you are using in a job and you want to use values between passes, then you could use a job variable. Or if you want to calculate and use the values in same pass in the job, you can use a Hashmap.
    Kind regards,
    Jai

  • 5 error while checking job status

    Hi,
    We are getting the following error when we are trying to check the status of the process chain through FM 'RSPC_API_CHAIN_GET_STATUS':
    5 error while checking job status.
    The real scenario is we are using an abap screen with a button on it. when the user clicks on the button we call the FM 'BP_EVENT_RAISE' to trigger the process chain. once the chain is triggered we are having an endless loop to monitor the status of the chain with FM 'RSPC_API_CHAIN_GET_STATUS' untill the chain status turns green ie G.
    Now while monitoring the status it randomly throws me the above error. it seems to work sometimes and other times it gives the popup with the said error.
    Can anybody help why we get the error.
    Regards,
    Shashank

    Hi Shanshank,
    Try to Debug the FM.
    Rgds,
    Ravi

  • Canceled Status in Job Detail, Process Chain triggering w/event

    Hi All,
    I have created event, PC and trigger event with SM64 or with ABAP, everything is ok
    if I activate and Schedule PC, I see BI_PROCESS_TRIGGER job with released status, and when I trigger the event nothing  is happened but when I checked the Job detail I see canceled status job.
    I donu2019t understand why this problem occurs ?
    I can trigger the event but before event trigger the PC, scheduled job detail directly turn to the chancel status.
    if any one give me a clue to solve this problem I will appreciate
    Note : No Job log !!!
    Thanks
    Ali

    Ali,
    Check authorizations.
    Try to run process chain with out event(immediate) and check.
    Srini

  • Check Status of job step

    Hi,
    i have a job having 3 steps. table TBTCO gives u the status of the 3 steps together -- job as a whole.
    How can i come to know of the status of the job at every step. i mean how will i confirm if at every step the job is executed properly or not.??
    Untill the complete job is executed, the status of each job step is Scheduled.
    Only after complete job excution u can find out the status . either finished or aborted.
    What if i want to know status at each job step?
    Kindly help,its urgent.
    Answers will be rewarded,
    regards,
    Rohan

    Hi,
    Checking  your job status with SM50 (processor type BTC) is more accurate then SM37.  SAP updates the tables TBTCO wheneveryour background jobs status change.  If SAP is shutdown, the currentjobs might not be update ontime to the table. (e.g. a background job wasshown as Active (SM37), in fact it real status should be Cancelled.
    Look at the function module <b>GET_JOB_RUNTIME_INFO</b>
    Regards
    Sudheer

Maybe you are looking for