Skip to Content
avatar image
Former Member

Issue regarding job SAP_CCMS_MONI_BATCH_STARTUP_DP

Hi,

We are facing an issue regarding an event triggered job SAP_CCMS_MONI_BATCH_STARTUP_DP.

Details of the job

-


ABAP Program -> RSAL_BATCH_TOOL_STARTUPDISP

User -> DDIC

Job Frequency -> Event Periodic

Event -> SAP_MONITORING_STARTUP_DISPATCH

We performed Database Refresh and this job has come from Source System. We have deleted the job in Target System but after that also we are getting continuous error message in SM21.

Error message is as follows:

14:33:36 DIA 001 000 SAPSYS EA S Failed to reschedule a periodic job

14:33:36 DIA 001 000 SAPSYS EB C > Job SAP_CCMS_MONI_BATCH_STARTUP_DP

On digging down we got the below information in SM21 regarding the error:

Documentation for system log message EA S :

-


This message is output by one of the job schedulers active in the

system (e.g. time or event-based scheduler). It indicates a problem

related to the database. An attempt was made to reschedule a periodic

job and write the respective control data in the database. This error

occurred for one of the associated database operations (for example,

INSERT or UPDATE).

Another cause of the error is failure to generate a new job ID number.

A subsequent message will point this out.

The following courses of action are possible:

Check whether there are any other notes on this problem next to this

message in the system log, for example direct messages from the

database interface. These details generally bring you closer to the

actual cause of the problem.

The additional information for this message contains the name of the

database table for which the error occurred.

If you determine that the error occurred during the SELECT access to

table TBTCI, the internal report belonging to this background job has

been deleted. In this case, there is normally a background job in the

'terminated' status, which ended due to runtime error

'LOAD_PROGRAM_NOT_FOUND'. Delete this job to prevent further

unnecessary scheduling on the part of the background processing

scheduler. You must then reschedule the job concerned.

As rescheduling of the periodic job could not be completed

successfully, this job is not executed at first. The background

processing scheduler takes this job and attempts to schedule it again.

Depending on the repetition period, gaps in running the background jobs

can occur for successful scheduling (i.e. the background jobs that were

unsuccessfully scheduled will be missing in the job overview if their

execution date elapsed in the meantime).

Since the next start of the periodic job could not be scheduled

correctly, there is no entry in the job overview for the planned start

date.

If the system failed to generate the job ID number, you will find notes

on what to do next in the long text of the respective system log

message.

We have fixed also Background Object in SM61.

Kindly help to fix this issue. Looking forward for reply.

Thanks,

Soumya

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Nov 29, 2009 at 01:44 AM

    Hi Soumya

    Lets try to check into the problem with these questions :

    1. Is the job getting triggered in your System : I mean in SM37 are you able to see the CANCELLED version of the job . Then what is the Job Log entry there . Paste the Job Log.

    2. And have you tried restarting your System Once after the refresh ?

    THanks

    Rishi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 14, 2011 at 03:36 PM

    I am also facing similar issue . I found below SM21 entries daily . becoz of this my system performance becomes slows down. no idea which tables are getting filled up due to this .

    > Job SAP_CCMS_MONI_BATCH_STARTUP_DP

    Failed to reschedule a periodic job

    For temporary fix we have changed the below memory parameters when system performance is poor .

    EM/TOTAL_SIZE_MB = 16384

    ES/SHM_SEGS_VERSION = 2

    ES/TABLE = SHM_SEGS

    But we need to fix these system log entries as still we are getting these errors. If anybody knows the permanent fix of this error that will be great for us.

    Regards

    Krishna

    Add comment
    10|10000 characters needed characters exceeded