Restarting an aborted background job in CC

One of our CC Static Text Upload daily jobs is showing as being in a current state of 'abort'.  I'm not sure how it got that way as I did not abort it.  I can only assume it ran into a problem when it last tried to run, maybe while server maintenance was being done and the SAP Adaptor was turned off.
Anyway, need to know how to restart this job and get it running again on schedule.  I tried doing a 'disable' and then 'enable', but it still shows as 'abort' and is not running.
We are using GRC 5.2 SP14.
Thanks.

Hi Bob,
Normally you get "Abort" message when J2ee engine stops.
Server restart will stop all jobs currently running and will not be effect any of your jobs that were scheduled to run in future.
To get the aborted job re-run, just reschedule it again with "Immediate" option.
Best Regards,
Sirish Gullapalli.

Similar Messages

  • Regarding Background Job Abort using

    Hi ,
    I am using FM BP_JOB_ABORT to abort background jobs through program,but it taking longtime to cancel background jobs in SM37 after exectuing FM BP_JOB_ABORT in program..
    will i have to write  any statement in program after this  FM BP_JOB_ABORT to cancel the background job immediately through program..
    Awaiting for valuable suggestion..
    Regards
    Anil

    Hi,
    I looking for FM to cancel background jobs quikly through program..
    Regards
    Anil

  • Background job ABORTED in ECC

    Hi,
    I am working for an upgrade project. We have a program in 4.7 which start background job using the FM: JOB_OPEN and submit7 standard programs with variant using FM: JOB_SUBMIT. Please find the program details below.
    1. RMCP6FLS
    2. RMCP6RES
    3. RMCA9026
    4. RMCP6BIN
    5. RMCP6RES
    6. RMCA9026
    7. RMCP6BIN
    After this close the job using FM: JOB_CLOSE and find the job status using the FM SHOW_JOBSTATE.
    For the same variant it is working fine in 4.7 but in ECC FM SHOW_JOBSTATE aborted = 'X'.
    Thanks and Regards
    Joby Jacob

    Please investigate yourself first, if you are still stuck, open another thread describing what you have analysed so far, providing all necessary details right away.
    Thread locked.
    Thomas

  • Is there any way to restart Cancled Background job

    Dears,
    Now we have a very important background job need to run everyday, but sometime it will be canceled due to memory is not enough.
    Is there any way to restart Cancled Background job automatically ?
    Thanks,
    Michael

    Hi Michael,
    To start the cancelled job manually
    At SM37 just mark the job then click   Job -> Change and just reschedule.
    For auto
    Create another job with same program name and variant , then create background processing event which gets trigger only when your job gets failed.
    For Event Creation kindly reach out to ABAPers and for Event based Scheduling you can contact basis team.
    BR Vaibhav

  • How to restart canceled background job

    Hi,
    I scheduled a background job but because of database is down, When I hit SM37 it gives me list of canceled jobs.
    What should I do to restart this jobs?
    Regards,
    Rajesh

    Hi Rajesh,
    Click on the job and click menu Job - Repeat Scheduling.
    You can't repeat all, your should do it one-by-one.
    Regards,
    Fendi Suyanto

  • Trigger Workflow for Background Job Abort

    Hi,
    I want to start a workflow when a Background Job fails.
    I could find the BOs BPJOB & BPJOB_SMAN and the event BPJobSchedMan.Aborted, but it is not getting triggered when a background job cancelled.
    Let me know if any specific settings need to be made.
    Appreciate your help. Thanks in advance.
    Rgds,
    Kumar

    Hi,
    Did  you manage to get this working?  i am also using BPJOB abort even but its not getting triggered.
    Thanks.
    Rgds,
    Pankaj

  • Different result when running as background job

    Hi,
    We got a program which has a selection screen with a couple of select-options.
    When we start this programm with a specified variant, it proceeds to a result screen. If we click back now (to the selection-screen) and run the programm with the exactly same settings again, one select-option is getting ignored and therefore we get incorrect results.
    This happens only, if you go back from the result screen and  excecute it again from the selection screen or if we start it as a background job.
    If you exit the programm completely and restart it, the results are correct again.
    It makes no sense to post any code snippets here, since the program is very complex. I just can't imagine any reason, why the select-option is sometimes getting ignored.
    Does anyone have an idea?
    Thanks in advance.
    Regards,
    Tobi

    oh well it DOES explain it.
    just think of following select:
    Select *
    from   vbap
    into    ls_vbap
    where vbeln not in lr_vbeln.
    if lr_vbeln is not cleard you will run into problems maybe.
    anyway, may it be that somewhere in coding you are manually modifying your select option?
    It´s just an internal table of type range, so have a look there.

  • Certain Maintenance Plan not getting scheduled in the background job

    Hi Gurus,
    I am facing an issue here.
    A weekly background job (RISTRA20) runs every weekend and schedules the maintenance plans.
    But we have noticed that some maintenance plans are not getting scheduled. i.e no orders or schedule is getting generated.
    When I run IP30 manually for these plans then the schedule gets generated and orders get called.
    I have checked up the background job and it is running fine.
    Also, i have noticed a similarity in all these plans which are not getting scheduled. There schedule has been restarted (through IP10) at somepoint or the other.
    But i don't see any direct impact of this?
    Can any of you provide some help on this?? Points will be rewarded.
    Thanks and regards,
    Nitin Saini

    Hi Narender,
    Thanks for replying.
    The message number for 'Groups don't match' is ME303.
    I think this does not have anything to do with the restart as i have done further investigation.
    Whenever I run IP30 with sortfield input as AS02*, i get the error as mentioned above for a certain number of maintenance plans while the remaining plans get scheduled.
    If i run IP30 for any other sort fields, it runs fine and i don't encounter the error
    mentioned above.
    If you send me ur email address, i could forward you screen-shots of the issue.

  • Sending of email triggered in a background job ends with error.

    Hello all,
    I have created a API which triggers mail to a distribution list using class CL_BCS. When i execute this API in foreground it works fine and the mails are triggered.
    However i am calling this API in a report which will scheduled as a  background job in my application and this job executes for some 5 to 6 hours and after that i trigger the mail. However at this point the job gets cancelled due to an abort message raised in
    one of the CL_BCS methods.
    The method is cl_cam_address_bcs=>create_internet_address which is called in my API and internally this calls many other methods. The abort meessage is thrown from the method instantiate_imp_class of class CL_EXIT_MASTER.
    The ST22 log reads like this:
    Runtime Errors:  LOAD_SWITCHSTATES_MISMATCH
    Short text:  Current switch statuses are incompatible with program switch statuses.
    What happened?
        The current switch statuses that are read for the execution of the
        program "CL_IM_CVI_ADDRESS_UPD_IMPL====CP" are incompatible with the switch
         statuses with which the
        program "CL_IM_CVI_ADDRESS_UPD_IMPL====CP" was generated at the time
         20090902114544.
    Any advice would be greatly helpful.
    Warm Regards,
    Naveen M

    Hi!
    How you determine sender (method set_sender) ? if you use current user, when it runs on background use a backgorund user and it maybe can not determine an email.
    Try force a sender (harcode your user for test when sy-batch eq 'X')
    If it works, you need to determine the user to be used on jobs to solve this problem.
    I hope it helps
    Regards!!!!

  • Background Job  running long time.

    Hello All,
    One of customer background job running for long time more than 11 hours, but usually this jobs get completed within 4 hrs.
    I have checked in WP trace file, it shows "WP has reached abap/heaplimit=40000000".
    This is the Value I can see in RZ11. Now it is not possible to change the value.
    Frequently facing this problem, please guide me to solve this issue.
    Regards
    Vinay.

    Hi
    First of all, abap/heaplimit is the limit of memory usage by a WP.
    Follwing is the documentation from help.sap.com
    The value of the parameter should be between 10000000 (10 MB) and 2000000000 (2GB), the recommended default setting is 40000000 (40 MB).
    The objective is to have the least number of work process restarts as possible, without a swap space bottleneck occurring.  The heap memory allocated by the work processes has to be released again.
    As shown in the graphic, the value of abap/heaplimit should be smaller than abap/heap_area_dia or abap/heap_area_nondia, so that the dialog step that is running can still be executed. This prevents the work process from working against the operating systemu2019s swap space limit if there is a programmed termination of the work process.
    So,Do the above checks. And importantly check the memory utilizations at the time of running your job and check whether any other job was also running at the sametime.
    Increasing the parametes is not a good idea.. If you continuously face this issue then only think of parametes. As u said ,this problem is not happenng too often.
    Hope this is useful

  • Periodic background job scheduling

    Hello fellow SDNers,
    I have a background job which has to run periodically. So I schedule it in SM36 to run after every 10 minutes and it executes without a problem. However, I have a scenario which requires that the next execution of the job should happen only after ensuring that the first one is not active (either it should have finished execution or aborted with error).
    I need to understand the options available to handle this. Of course there is an option of writing another program to handle these jobs dynamically using JOB_OPEN, JOB_SUBMIT etc. or to create an event and trigerring it through another program and setting the job to run after this.
    Is there any other option/setting available which can save me from the programming effort (which i wish to keep as my last resort to handle this)?
    Any pointers are appreciated!!
    -Priyank

    `hi,
      u hav after event in dat select--> sap_end_of_job
    in job start conditons or esle u can check start condition in extended job selection.
    read the usage tip there..

  • Background Job is not running in KW

    Hi All,
    I have problem with background job.
    I am working on Knowledge warehouse server.
    And I am scheduling background job to upload contents.
    But background job is not finishing at proper time.
    And while displaying trace it is giving following error.
    ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1251]
    Please help me to resolve this.
    Regards,
    Payal patel

    Hi Juan,
    I have tried with process as well as instance restart.
    It didn't help me.
    Hi Santosh,
    Following is the part of trace file (level -2).
    First line shows error.
    Tell me if you need any other log file.
    L  *** ERROR => BtcCleanUp: BtcLgAp-call failed (rc = 4) [btcjcntl.c   1251]
    M  read msgserver-list from MBUF
    M  ThSemRq (4, 1, 0, 0)
    M  ThSemRel (4, 1)
    M  ThSetBtcName: found batch server sapbl4_KW7_00                          
    M  ThScheduler2: server name: sapbl4_KW7_00                          
    M  ThISendMsg: send message (5) to server (wp) with name >sapbl4_KW7_00                           <
    M  ThISndName: send to name: >sapbl4_KW7_00                           <
    M  ThISend: (tm/type/info = 10/0x2000/0x0, mode_deleted=0)
    M  ThRqOutCheck: o.k.
    M  abap strategy ROLL / O.K.
    M  ThNewWpStat (type=0x2000, task_switch=0, inline_hold=0, hand_shake=0, debug=0, ..)
    M  ThNewWpStat: new state of T10/M0 = 0x3c
    M  ThISend: new wp stat: 0x0
    M  Adresse   Offset  Message by name (one way)
    M  -
    M  06C60600  000000  00000000 05000000 255f4556 454e545f |........%_EVENT_|
    M  06C60610  000016  53434845 44554c45 52202020 20202020 |SCHEDULER       |
    M  -
    M  ThMkReq: send output to canceled mode
    M  make DISP owner of wp_ca_blk 180
    M  DpRqPutIntoQueue: put request into queue (reqtype 0, prio LOW, rq_id 19358)
    M  -OUT- sender_id WORK_PROCESS      tid  10    wp_ca_blk   180     wp_id 10
    M  -OUT- action    SEND_MSG_ONEWAY   uid  11    appc_ca_blk -1      type  NOWP
    M  -OUT- new_stat  NO_CHANGE         mode 0     len         268     rq_id 19358
    M  -OUT- forward   DIA              
    M  -OUT- req_info  CANCELMODE MSG_WITH_REQ_BUF MSG_WITH_OH
    M  nihsl-getHostAddr: got hostname 'localhost' from operation system
    M  nihsi-getHostAddr: hostname 'localhost' = addr 127.0.0.1
    M  nihsl-getServNo: got servicename 'sapdp00' from operation system
    M  nihsi-getServNo: servicename 'sapdp00' = port 0C.80/3200
    M  NiIInitSocket: set default settings for socket 1196
    M  NiCreateHandle: state hdl 1 / socket 1196 NI_INITIAL
    M  NiIDgSend: init datagram send hdl 1 / socket 1196
    M  CPU byte order: little endian, reverse network, low val .. high val
    M  NiIDgSend: connect dgram to: host 127.0.0.1, port 0C.80/3200, fam 2 (low adr..high adr)
    M  NiIDgsend: sending on connected datagram-handle
    M  LOCK WP ca_blk 181
    M  ThResFree: free resources of U11 M0 I2 (normal mode, complete free) at level 3, errno=23, db_action=TH_DB_NO_ACTION, pooling=1
    M  ThResFree: reset spa state for user T10/U11/M0
    M  ThCallHooks: call hook >RtmClearSession< for event BEFORE_SESSION_CANCEL
    M  ThCallHooks: call hook >HttpClearSession< for event BEFORE_SESSION_CANCEL
    M  ThCallHooks: call hook >SpoolHandleHook< for event BEFORE_SESSION_CANCEL
    M  SosSearchAnchor: search anchor for 2
    M  PfStatDisconnect: disconnect statistics
    M  ThDealComm: del 1 cpic conn(s) of T10/U11/M0 (errno/deal_r2/free_level = 23/1/3)
    M  ThCPICFree: send DEAL to U11/M0
    M  ThICMDEAL (14030609, ..)
    M  ThCPIC: execute cpic func DEALLOCATE
    M  ThCPIC: last_ftype/last_timeout/last_requested_length/last_receive_data 1/-1/-1/0
    M  ThCPIC: allowed rq_type of T10/M0 = TH_APPC_RC_RQ
    M  ThConnectToLocGw: connect to local gateway
    M  GwConnectSapWp: connect to gateway >localhost< >sapgw00<
    M  nihsl-getHostAddr: found hostname 'localhost' in cache
    M  nihsi-getHostAddr: hostname 'localhost' = addr 127.0.0.1
    M  nihsl-getServNo: got servicename 'sapgw00' from operation system
    M  nihsi-getServNo: servicename 'sapgw00' = port 0C.E4/3300
    M  NiCreateHandle: state hdl 2 / socket -1 NI_INITIAL
    M  NiIBlockMode: switch off block-mode for hdl 2 / socket -1
    M  NiLowLevCon: connect to: host 127.0.0.1, port 0C.E4/3300, fam 2 (low adr..high adr)
    M  NiIInitSocket: set default settings for socket 1140
    M  NiISocket: hdl 2 got socket 1140
    M  NiPConnect: connect in progress
    M  SiPeekPendConn: connection of socket 1140 established
    M  NiLowLevCon: took local port 0E.51/3665
    M  nilh-localCheck: using local address list
    M  NiSetStat: state hdl 2 NI_CONNECTED
    M  NiIWrite: write 64, 1 packs, MESG_IO, hdl 2, data complete
    M  NiIPeek: peek successful for hdl 2 / socket 1140 (r)
    M  NiIRead: read 64, 2 packs, MESG_IO, hdl 2, data complete
    M  GwConnectSapWp: connect to gateway localhost / sapgw00 (pid = 6184) o.k.
    M  ThISend: (tm/type/info = 10/0x80/0x0, mode_deleted=0)
    M  ThRqOutCheck: o.k.
    M  abap strategy ROLL / O.K.
    M  ThNewWpStat (type=0x80, task_switch=0, inline_hold=0, hand_shake=0, debug=0, ..)
    M  ThNewWpStat: new state of T10/M0 = 0x3c
    M  ThISend: new wp stat: 0x0
    Regards,
    Payal Patel
    Message was edited by:
            Payal Patel

  • F.13 - Background job

    Hi,
    I am trying to setup a background job to run F.13 to clear G/L accounts. In SM37 the job is displayed as 'run successfully'. however when i open the spool to see the messages it gives a message "No transaction code available; restart the program". There are many documents which meet the criteria for clearing but none of them get cleared. When I run the program using the same variant in the foreground all those documents get cleared without any problem
    Anyone came accross the same problem when running this job in the background. There is an OSS note(1376249) that details this problem. Please let me know if anyone has implemented this note or if there are any alternatives to solve this issue. Are there any affects on the system if this note is implemented.
    Any help will be greatly appreciated.
    Thanks
    Nick

    Stacy,
    Thanks for your reply. In the test environment - i created a variant and ran it myself both in background and in foreground. I am able to clear the documents in foreground. So it cannot be an authorization issue, and I am using the same variant for back ground and foreground so it cannot be variant issue.
    What exactly do you mean by job parameter?
    Thanks
    Nick

  • How to delete Background job

    hi all,
    i am working on ECC6.0.
    i am not able to find the path to delete background job completly.
    can any body give me the navigation for the same in ECC6.0
    Thanks in advance

    hi
    hopen ths wll help
    To delete a background job explicitly, use:
    BP_JOB_SELECT to obtain the jobname and job number of the job that you wish to delete.
    You can select jobs according to all of the criteria available in the interactive background processing management system:
    Jobname: Using a well-planned naming convention for your jobs will help you to select them precisely.
    Job number
    Name of the user who scheduled a job
    Specifications for the start-time window/no start time scheduled
    Start dependent upon predecessor jobs
    Start dependent upon an event and event argument
    Job status (preliminary, scheduled, ready, running, finished, aborted).
    BP_JOB_DELETE to delete the job. The job log is deleted as well, if the job has already been run.
    A job cannot delete itself. Also, a job that is currently running cannot be deleted. However, you can have it deleted automatically if it is completed successfully. See the DELANFREP parameter of JOB_OPEN.
    Sample Program: Deleting a Background Job
    Data declarations: BP_JOB_SELECT
    DATA JSELECT LIKE BTCSELECT.
    DATA SEL_JOBLIST LIKE TBTCJOB OCCURS 100 WITH HEADER LINE.
    Sample selection criteria
    JSELECT-JOBNAME = 'Name of job'.
    JSELECT-USERNAME = SY-UNAME.
    CALL FUNCTION 'BP_JOB_SELECT'
    EXPORTING
    JOBSELECT_DIALOG = BTC_NO
    JOBSEL_PARAM_IN = JSELECT
    IMPORTING
    JOBSEL_PARAM_OUT = JSELECT
    TABLES
    JOBSELECT_JOBLIST = SEL_JOBLIST
    EXCEPTIONS NO_JOBS_FOUND = 1
    SELECTION_CANCELED = 2
    OTHERS = 99.
    In this example, the program loops over the internal table
    SEL_JOBLIST and deletes each of the jobs that was selected.
    Alternative: Have the user select the job to be deleted
    with BP_JOBLIST_PROCESSOR. For an example, please see
    Sample Program: Wait for Predecessor Job with JOB_CLOSE.
    LOOP AT SEL_JOBLIST.
    CALL FUNCTION 'BP_JOB_DELETE'
    EXPORTING
    FORCEDMODE = 'X'
    JOBNAME = SEL_JOBLIST-JOBNAME
    JOBCOUNT = SEL_JOBLIST-JOBCOUNT
    EXCEPTIONS
    OTHERS = 99.
    ENDLOOP. *
    FORCEDMODE deletes the job header even if other portions of the
    job cannot be deleted from the TemSe facility, where they are
    held.
    FORCEDMODE can be used without fear of causing problems in the
    System. Any TemSe problem that affects background jobs can be
    resolved directly in the TemSe system and does not require the
    job header.
    regards
    navjot
    reward if helpfull

  • What to add to an program code in order to trigger an background job

    Hi there
    I wander what to add to an program code in order to trigger an event which consequently can trigger an background job
    thx in advance

    Check this code:
    DATA : v_jobhead LIKE tbtcjob.
    DATA : v_jobcount LIKE tbtcjob-jobcount.
    DATA : v_eventparm LIKE tbtcjob-eventparm.
    DATA : v_flg_released TYPE c.
    DATA: e_error.
    DATA: running LIKE tbtcv-run.
    TYPES: esp1_boolean LIKE boole-boole.
    CONSTANTS: esp1_false TYPE esp1_boolean VALUE ' ',
               esp1_true  TYPE esp1_boolean VALUE 'X'.
    CONSTANTS: true  TYPE boolean VALUE esp1_true,
                              false TYPE boolean VALUE esp1_false.
    PARAMETERS: v_jobnam LIKE tbtcjob-jobname,
                v_report LIKE sy-repid,
                v_varian LIKE  raldb-variant,
                v_uname  LIKE sy-uname.
    START-OF-SELECTION.
    * add the new job
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
    *            delanfrep        = 'X'
                jobname          = v_jobnam
           IMPORTING
                jobcount         = v_jobcount
           EXCEPTIONS
                cant_create_job  = 1
                invalid_job_data = 2
                jobname_missing  = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        e_error = true.
      ELSE.
        CALL FUNCTION 'JOB_SUBMIT'  " or you can use SUBMIT statement as well.
             EXPORTING
                  authcknam               = v_uname
                  jobcount                = v_jobcount
                  jobname                 = v_jobnam
                  report                  = v_report
                  variant                 = v_varian
             EXCEPTIONS
                  bad_priparams           = 1
                  bad_xpgflags            = 2
                  invalid_jobdata         = 3
                  jobname_missing         = 4
                  job_notex               = 5
                  job_submit_failed       = 6
                  lock_failed             = 7
                  program_missing         = 8
                  prog_abap_and_extpg_set = 9
                  OTHERS                  = 10.
        IF sy-subrc <> 0.
          e_error = true.
        ELSE.
          CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
    *               EVENT_ID                    = IC_WWI_WORKPROCESS_EVENT
    *               EVENT_PARAM                 = V_EVENTPARM
    *               EVENT_PERIODIC              = 'X'
                    jobcount                    = v_jobcount
                    jobname                     = v_jobnam
                    strtimmed                   = 'X'
               IMPORTING
                    job_was_released            = v_flg_released
               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.
            e_error = true.
          ELSE.
            DO.
              CALL FUNCTION 'SHOW_JOBSTATE'
                EXPORTING
                  jobcount               = v_jobcount
                  jobname                = v_jobnam
    *            IMPORTING
    *         ABORTED                =
    *         FINISHED               =
    *         PRELIMINARY            =
    *         READY                  =
    *              running                =
    *         SCHEDULED              =
               EXCEPTIONS
                 jobcount_missing       = 1
                 jobname_missing        = 2
                 job_notex              = 3
                 OTHERS                 = 4.
              IF sy-subrc <> 0.
                e_error = true.
                MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
              ENDIF.
              IF running = space.
                EXIT.
              ENDIF.
            ENDDO.
          ENDIF.
        ENDIF.
      ENDIF.

Maybe you are looking for