cancel
Showing results for 
Search instead for 
Did you mean: 

Error Messages for SM37.. Need Help

MaheshKumar
Contributor
0 Kudos

Hi,

Mine is ECC 6.0 , HP-UX with Oracle database

As per my regular monitoring i was monitoring SM37. It has given me following errors .. pls tell me how can i rectify it.

1. CODE_INSPECTOR_DELETION... cancelled job owner is a user name(SISL9) who doenst exists in my user list.

2. DBA:CHECKDB___@050000/5007 05:00AM Finished

DBA:CHECKDB___@050000/5007 05:30AM Cancelled

3. DBA:UPDATE STATS___@43000/5007 4:30AM Cancelled

DBA:UPDATE STATS___@43000/5007 7:30AM Finished

4. SAP_REORG_SPOOL Cancelled

5. SAP_WP_CACHE_RELOAD_FULL Cancelled

Please tell me about resolutions for above issues.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

"cancelled job owner is a user name(SISL9) who doenst exists in my user list."

If job is cancelled because of no user exist/deleted, then its a normal behaviour of SAP.

If only few of the jobs are getting failed, then suggest you to get into more details

*Job creator/owner is nothing in SAP but step owner executes the job always

Regards,

Nick Loy

markus_doehr2
Active Contributor
0 Kudos

Did you check the job logs for the errorneous jobs?

Markus

MaheshKumar
Contributor
0 Kudos

1. CODE_INSPECTOR_DELETION... cancelled job owner is a user name(SISL9) who doenst exists in my user list.

- SAP Note: 825245

2. DBA:CHECKDB___@050000/5007 05:00AM Finished

DBA:CHECKDB___@050000/5007 05:30AM Cancelled

3. DBA:UPDATE STATS___@43000/5007 4:30AM Cancelled

DBA:UPDATE STATS___@43000/5007 7:30AM Finished

4. SAP_REORG_SPOOL Cancelled

-This background job is rquired and should be done daily. SO that it will delete old spool request.Use T-Code: RSPO0041

http://help.sap.com/saphelp_45b/helpdata/en/c4/3a7ede505211d189550000e829fbbd/content.htm

5. SAP_WP_CACHE_RELOAD_FULL Cancelled

-According to SAP notes 1034532 & 16083 this background process must be deleted.

i dint find solutions for error 2 and 3

former_member185031
Active Contributor
0 Kudos

>>I dint find solutions for error 2 and 3

You have to check the correpondings logs on SM37 to know the details why it's been cancelled.

Regards,

Subhash

Former Member
0 Kudos

Hi Mahesh,

It seems that you have deleted the entries in DB13 in DBA planning calender and recreated it.

So one entry for each DBA* job is failing.

Can you check in DB13 : DBA planning calender, what is the status of the jobs update stats and check DB??

If it is showing in Green(Success) , then you can delete the subsequent released jobs of DBA* jobs which are failing.

Please let me know if you need any more info.

Thanks,

Jagadish.