on 04-18-2007 7:51 AM
Hello Gurus,
In My Production Server there are few cancelled jobs
1. DBA:CLEANUPLOGS_____@050000/3007
2. DBA:CHECKDB_________@060000/3007
3. DBA:UPDATESTATS_____@020000/2007
These jobs are cancelled due to Action deleted in SDBAP at 20070324150315
Job cancelled after system exception ERROR_MESSAGE
Can any body suggest why they are cancelled and what is role of these jobs are they critical or non critical
For Your Reference the Source Code of the program
&----
*& Report RSDBAJOB *
*& *
&----
*& This report is started as a batch job from the DBA planning *
*& calendar. It then starts the special DBA action. *
&----
report rsdbajob message-id q2.
parameters: cretstmp like sdbap-cretstmp,
daye like sdbap-daye,
timee like sdbap-timee,
sysid like sdbap-sysid.
include rsalexti.
include rsjobdat. " Global data
include rsjobe01. " Events
include rsjobf01. " Forms
Hello Sunil
Here is The log
Job started
Step 001 started (program RSDBAJOB, variant &0000000000037, user ID CSCADMIN_BC)
Action deleted in SDBAP at 20070324150320
Job cancelled after system exception ERROR_MESSAGE
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
when you schedule a job in DB13, it created a job in SM37 associated with you DB13 job.
this association was lost (perhaps due to a system copy).
so, here's the plan, delete all DB13 jobs, all of them
delete all DBA* jobs in SM37
recreate DB13 jobs again.
This will fix your problem, I'm 100% positive.
Yeah Eric...You are right.
Recreating the DB13 jobs as fresh will solve the issue. My serious doubt is ,whether the user id used for scheduling the old DB13 job was deleted at the target system. The job will also fail if the scheduled user id is deleted in the target system.
Please make sure that or you can create a fresh new DB13 jobs again.
Hope this solves your problem.
Happy SAPing!
regards,
Vinodh.
Hello Vinod
many thanks for thr quick reply
I checked in DB13 and i found that
updatestats & checkdb are completed successfully but in SM37 these jobs are cancelled while investigation and found that there is a report - RSDBAJOB
runs in the background while these jobs run in DB13
output of the report
This report is started as a batch job from the DBA planning *
*& calendar. It then starts the special DBA action.
there is a variant which is not exist variant name - &0000000000041
Please suggest what to do ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shishir,
The jobs that you have mentioned are standard BASIS jobs. These jobs are very important for house keeping purpose in order to run the R3 system efficiently.
These jobs are triggered from DB13( DBA calander). Please check the Db13 transaction and you can see the scheduled jobs in red color.
To see the error logs...in DB13 select the Action logs option.
Please make sure that the user id which is used to schedule these jobs exist in the system.
regards,
VInodh.
Message was edited by:
Vinodh Kumar Narayanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.