SAP CCMS MONI BATCH STARTUP DP: Failed to reschedule a periodic job

You have completed a system refresh and encountering below error in transaction code SM21,

Failed to reschedule a periodic job
> Job SAP_CCMS_MONI_BATCH_STARTUP_DP
< Job count 15264800'
Failed to reschedule a periodic job
> Job SAP_CCMS_MONI_BATCH_STARTUP_DP
< Job count 15264800'

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.

In transaction code SM37, the SAP_CCMS_MONI_BATCH_STARTUP_DP job is in finished status and you did not found any cancelled, released, scheduled status.