on 11-21-2013 10:24 AM
Hi there,
I can go into DB13 and start a job say 'Check Database' to execute immediately
and it works fine.
However, if I schedule the same job to say run in ten minutes time nothing happens.
I click on the job and see the status has ' Not available'. The next day this will
be highlighted in red and the status changed to 'Scheduling Failed'. These isn't
any detail logs produced either so I cant see any errors if any!
I don't understand how the job runs ok when I run it immediately but fails when
I try to start in the future.
I have checked the permissions of BR*Tools against other systems(which work ok)
and they are the same.
Anybody have any ideas??
Thanks
Andy
Can you check the Target Server and the Executing Server in Tx SM37 for the job ?
You will need to change the layout in SM37 by using the change layout icon or using "Ctrl+F7" combination keys.
Also are you using server groups for background jobs ? Check Tx SM61
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the same problem. I fixed it by ntpdate and cleaning all jobs in DB13. I had a wrong time in my system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andy!
If you use RHEL for SAP here is the link about ntpdate:
2.2.2. Network Time Protocol Setup
Type date in console to find out that the date and time is correct or not.
If the time is correct you don't need to use ntpdate.
Many thanks guys for all your contributions I really appreciate your time.
This system(Solution manager) holds our SLD. I've just checked and the last time
the system was restarted was back in April.
All the DBA jobs are defined in exactly the same way as on the other systems.
So they should be working fine as they do on there.
I don't think I have any option but as RB suggests to restart the system.
So I will do this at the weekend and see what happens on Monday.
Many thanks again
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There is probably a disconnect between DB13 and SM37.
delete all your jobs in DB13, now go into SM37 anf delete all jobs DBA*.
when finished, re-create your jobs in DB13
BR,
Prabhakar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What does the job log say ? Tx DB14
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If there are no backgroung process and the jobs cant be submitted then i can think the below reason may be the cause of the jobs in red.
1705708 - Long running DB13 jobs displays Red status after 12 midnight
Thanks
Rishi Abrol
There was some known issue with DB13, while scheduling the jobs never executed with the log Scheduling failed. I am not sure what is your database but there are couple of notes which explains this errors.
166861 - Analysis of DB13 problems
564576 - Resetting the scheduling in transaction DB13
Regards,
Subhash
Hi,
Ok lets try to create a operation mode in you system and see if we can have 7 dialog process and 6 background process and then switch the server to that operation mode and see if the jobs still fails.
Also if there is an active job in sm37 try to check the status and see what happens.
Do you have any application server or only one Central instance.
Thanks
Rishi Abrol
Hello Andy,
Sometimes the BTC WPs hangs whereas it shows as available in SM50.
1. Restart the BTC WPs in SM50 [ Administration -> Process -> Cancel -> without Core ]
2. Schedule a dummy batch job to check eg. Report RSPARAM in background to check if it gets triggered properly.
3. If it works then schedule it again from DB13
Hope it works.
Regards,
Mudasir
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.