cancel
Showing results for 
Search instead for 
Did you mean: 

DB backup not started

former_member204080
Active Contributor
0 Kudos

Hi all,

The DB backup scheduled through DB13 is not runnning .There is no log available for this.when you click the date on which it is scheduled the status is showing as unknown.

Kindly Provide your suggestions

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello,

After you scheduled the job in DB13, do you see the same in SM37 with status "Scheduled"?

Thanks,

Siva Kumar

ashish_mishra2
Contributor
0 Kudos

Reschedule the same again from DB13 and see if it throws any error.

BTW what about other DBA jobs?? are you able to run them from DB13 without any issue?

Cheers !!!

Ashish

former_member204080
Active Contributor
0 Kudos

Hi,

DB:Oracle 10.2.0.5

Os:AIX 5.3

There are no logs at os level

Some scheduled through DB13 are running.While some like backup and checkdb are not running.

former_member227283
Active Contributor
0 Kudos

Hi Murali,

Kindly delete the task from DB13 calender and also check in SM37 and delete the job of the same.

Then replan the job in calender.

Thanks,

Anil Bhandary

Former Member
0 Kudos

Hi Murali,

Apart from the above posts, the other reason might be of SAP Login thru which backups or other jobs scheduled and if the same SAP login is in locked state or deleted then also a chance of failing backups. If that is the case delete all schedules from DB13 and re-schedule from your login freshly. For testing purpose initially you can schedule checkdb during lunch time/off peak period.

Rgds,

Durga.

former_member204080
Active Contributor
0 Kudos

Hi,

In some system all scheduled through DB13 are not running.

Error:Scheduling Failed.

Kindly provide inputs.

former_member189725
Active Contributor
0 Kudos

Can you please check in SM37 for failed jobs and paste the job log.

Former Member
0 Kudos

Hi Murali,

As i suggested in my previous post, delete all schedules at once in DB13 and reschedule manually checkdb once and similarly the same with backup (online/offline) as per the regular schedule.

Rgds,

Durga.

ashish_mishra2
Contributor
0 Kudos

Hi Murali,

One of the possibility might be, though the job is scheduled to run from DB13 but at the same time corresponding job is not present in SM37 or the user used for job scheduling is not valid of locked etc.

So for the safer side as suggested by other users above, delete the same from DB13 and schedule fresh jobs.

Make sure that the user, being used for DB13 scheduling is having enough authorization to run the job.

It should work.

Cheers !!!

Ashish

former_member204080
Active Contributor
0 Kudos

Hi all,

Thank You for your suggestions.

I will try those.

Former Member
0 Kudos

Hi,

First you should try to take backup using brtools on OS level. This will confirm if there is any issue with profile file. If it gets failed, you need to correct that. If it gets success, Schedule backup using some sap id which has proper authorization like super. It should work. Kindly share logs if issue still persist.

Former Member
0 Kudos

Hi Murali,

Check if any cron jobs are scheduled for backup, and please suggest the OS and DB you are using.

Regards,

Sandeep Singh

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

What is your OS and DB ? Have you checked logs at OS level ?

Thanks

Sunny