DB13 - Scheduling Jobs Failing

[Former Member]

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

[Reagan · Accepted solution]

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

[Former Member · Accepted solution]

Thanks RB,

SM37 now shows:

SM61 shows:

[Reagan · Accepted solution]

Try to restart the system and see if that helps.

Check Tx SM65 and see if everything is OK there.

Regards

RB

[manish_singh13 · Accepted solution]

Hi Andy,

Please check SAP Note 165084 - Why does my job not start? also.

Thanks,

Manish Singh

[Former Member]

I had the same problem. I fixed it by ntpdate and cleaning all jobs in DB13. I had a wrong time in my system.

[Former Member]

Hi Igor,

Thanks very much for the reply. If I just search for ntpdate will I find out what to do?

Is this a demon process running that needs resetting or something?

Thanks

Andy

[Former Member]

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.

[Former Member]

Cheers Igor, it must be something else in my case:

sap-t-ecc01-l:evaadm 52> date

Fri Oct  2 08:56:04 BST 2015

I just run the date command everything appears in order!

Many thanks anyway

Andy

[Former Member]

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

[Former Member]

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

[Reagan]

What does the job log say ? Tx DB14

Regards

RB

[Former Member]

Hello RB again,

I have just scheduled a job to run 9:30 this morning UK time.

When I go into DB14 and there are no jobs listed against this time.

But there are jobs listed for those I run immediately

Andy

[Former Member]

Hi,

Do your id has authorization to submit the job in backgroung.

Can you please post the job log.

Can you see if there are free backgroung process. Do you see that job cancelling in the system with delay.

Please past the job log.

Thanks

Rishi Abrol

[Former Member]

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

[Former Member]

Hi Rishi,

I have both SAP_ALL and SAP_NEW roles.

When I look in SM37 the job scheduled for 9:30 this morning is in a 'Released'

state. No log entries available for the job when I click on it.

[former_member185031]

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

[Reagan]

Hello Andy

Double click on the job in released status and check the job details.

One question: is this happening after some activity or has it been like this before ?

Regards

RB

[Former Member]

Hi RB,

I can pin point back to 23rd October. Everything was working up until that

day. Since then all the jobs scheduled are failed.

There has been no updates i.e. kernel upgrades or anything

[ashish_vikas]

I see a long delay in Job ? Do you have sufficient BTC workprocess ?

Alos check - the server maintained in Execution target.. is that available ?

bes tregards

ashish

[Former Member]

Hello Andy,

Looks like the batch job did not get triggered due to non-availability of BTC processes or some other system issue. Can you check the status of other jobs which might have been scheduled to run during  that time period.

Regards,

Mudasir

[Former Member]

Hi,

Yes as per the delay it looks like that the resources are waiting for backgroung process.

Thanks

Rishi Abrol

[Reagan]

And is the executing server the one you are connected to ?

Regards

RB

[Former Member]

Hi,

But those background processes are there and waiting:

[Former Member]

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

[Former Member]

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

[ashish_vikas]

check - the server maintained in Execution target.. is that available ?

Else change this to currently available server.

best regards

ashish

[Former Member]

Hi,

I have cancelled and restarted all three background processes. I then scheduled

RSPARAM to run. When I look now in SM37 they are at a 'Released' state with

the delay just increasing.

[Former Member]

Hi,

Check this.

1943027 - "Scheduling failed" status in DB13/DBACOCKPIT

Thanks

Rishi Abrol

[Former Member]

Hello,

Can you check if the background logon groups are maintained correctly in SM61.   Tcode SM61 --> Job-Servergruppen --> create the group and assign your servers. Makre sure the correct app servers are maintained in the created groups.

Regards,

Mudasir