Job: SAP_CCMS_MONI_BATCH_DP

Question

Basis jobs seem to error on Sunday morning, after the Cold backup system outage ??
The SAP_CCMS_MONI_BATCH_DP, but seems to error each week after the system is started up from the backup outage ??
This past Sunday morning, the system stopped at 3:25 am and started 3:30 am
Job scheudle to starts at : 04:15:59
It fails everytime after system restarts on Sunday after cold backup....other times it works fine.
Any help would be much appericated.
Kumar

Answer 1

Date       Time     Message text                                                                     Message class Message
09/23/2007 04:16:03 Job started                                                                           00           516
09/23/2007 04:16:03 Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID DANCHA)      00           550
09/23/2007 04:17:14 No alerts in configuration range                                                  ME_CCMS_NAK      030
09/23/2007 04:17:22 ABAP/4 processor: DBIF_RSQL_INVALID_CURSOR                                            00           671
09/23/2007 04:17:22 Job cancelled                                                                         00           518
ABAP Short dump:
Runtime Error          DBIF_RSQL_INVALID_CURSOR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          09/23/2007 04:17:22
Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
     neither
    caught nor passed along using a RAISING clause, in the procedure
     "SBOM_BUILD_SYSCHECK_TREE" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    One of the database selections included a database commit.
    The selection was then supposed to continue. Before a
    database commit, however, all outstanding database selections must be
    concluded.
    Possible causes in the application program:
    Within a loop (SELECT/LOOP/EXEC SQL), one of the following
    statements is used:
    - MESSAGE (apart from MESSAGE S...)
    - COMMIT WORK
    - ROLLBACK WORK
    - CALL SCREEN
    - CALL DIALOG
    - CALL TRANSACTION
    - SUBMIT
    - BREAK-POINT
    - WAIT
    In debugging mode, a program sometimes triggers
    a "COMMIT WORK" during the database selection. As a result
    this termination may also occur in debugging mode with a correct
    program.
    A "COMMIT WORK" during debugging may be due to the following reasons:
    1. A program or screen was regenerated
       and updated in the database.
    2. Each user needs a private process in debugging mode, but
       the number of available processes is restricted. If this
       limit is exceeded, each debugging step then requires a
       "COMMIT WORK".
    The error occurred in a statement that accesses the table "DBCHECKORA ".
see if that helps you.
Kumar