Skip to Content

SAP Background jobs failing..

Hello All,

It's quite after a long time on SCN..!!!

SAP standard job is failing every week.

SAP Back ground job "SAP CCMS_<SID>_<SID>_Cleanup_Saplocks" on server SAPDB<SID> server fails to execute every week.

From where i get the log for troubleshooting..??

Please suggest..??

Regards, JUNAID AHMAD

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jul 19, 2017 at 07:57 AM

    Hi Junaid,


    please go to transaction SM37 and search for the job which is failing. Once you see the cancelled job you can double click on it. Now you are on the "job start page".


    In the job log (STRG+CTRL+F11 buttons) you see important information: when the job started, when it ended and what happens in between. Please check it and let us know your findings. You can also check the message class number on the right of the error (double-click on it) which is sometimes useful for searching for a solution in the SAP Network. Often the job log points to transaction ST22 to check the dump which occurs and leads to the broken job.



    In the job details (F7 button) you get some additional information. Check the Work Process number on the bottom of the page. Use this number to check the dev_w* trace in transcation ST11 or in the work folder of the instance to get some more information.

    Hope this helps a bit.


    Cheers,
    Andreas

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 19, 2017 at 01:19 PM

    Start with Tx's SM37, SM21 and SM50

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 19, 2017 at 09:17 PM

    Hi Junaid,

    It seems that you are not asking about batch jobs occurring in your ABAP system, but about SQL jobs occurring at the database level. Is that correct? If so, the job logs should be available in your DBMS management tool. Which DB platform are you using? The job name seems consistent with SQL Server, but I'm not sure whether other databases use this same format. Also, did something about the system change recently? Was this refreshed from another system via System Copy? Doing so without properly handling all the post-refresh cleanup tasks can leave these DB-level jobs orphaned, causing them to fail. Also, is this an ABAP system or a Java system? The database (or schema?) name seems slightly off for either one. Also, the "cleanup_saplocks" DB job (at least for SQL Server) was only relevant for some older NetWeaver ABAP releases.

    If this is an ABAP system, the quick way to resolve this might be to just delete all the "SAP CCMS_*" jobs at the database level, then recreate them from DBACOCKPIT via Configuration... Monitoring Environment... Execute SQL scripts (for a newer NetWeaver release), or Configuration... SQL Script Execution... Execute scripts (for an older release). These examples are for a SQL Server system; other DBMS platforms may be different.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 19, 2017 at 08:05 PM

    Hi,

    Please follow the below steps:

    1) SM37 -> identify the job

    2) Job details

    3) Job log

    4) SM21

    5) AL11 -> dev_w*

    Regards,
    Manjunath

    Add comment
    10|10000 characters needed characters exceeded