DB13, Error while backup

Question

Hello
I am trying to schedule Whole offline backup through DB13 in Solution Manager 4.
The backup kicks off at the schedule time but ends with error with in seconds.
When i go and check the background job in SM37, the Job DBA:ALLOFFLINE______@174008/4000 is with Finished successfully status
I check the JOB log in DB13,
21:00:00     Job started
21:00:00     Step 001 started (program RSDBAJOB, variant &0000000000000, user ID XYZ)
21:00:00     Execute logical command BRBACKUP On host DQESAP03
21:00:00     Parameters:-u / -jid ALLOF20090401210000 -c force -t offline_force -m all -p initDBI.sap -w use_dbv
21:00:01     Job finished
I go to Action log in DB13
Status is in Error
Return code is 003 Error during initialization.
when i go to detail action log:-
BRBACKUP Action Log for Database <DBSID>
From:   01.04.2009 20:40:09 
LogFile:   beagpiht.afd 
Return Code:   0003 Error during initialization 
No action log for this action found in the database 
  Check the detail log 
There are no logs created at OS level /oracle/SID/sapbackup
I then started the backup usning BRTOOLS at os level and Backup is successful.
Please suggest what could be the problem.
Thanks

Answer 1

>
Subhajit Sengupta wrote:
> I think you need to manitain the BRBACKUP command in table SDBAC to be able to run a backup from DB13.
OK, putting my 5cents
1) I do not think the recommendation is good.
Table SDBAC should only be "touched" if indicated by an SAP note.
2) at the same time, I think it may be part of the problem.
The OP states:
> I am trying to schedule Whole offline backup
also
> background job in SM37, the Job DBA:ALLOFFLINE___
and finaly, the command executed is:
> Parameters:-u / -jid ALLOF20090401210000 -c force -t offline_force -m all -p initDBI.sap -w use_dbv
That is an OFFLINE backup plus a verification.
AFAIK, that is not a standard SAP JOB.
I assume that someone has changed the entry in SDBAC introducing this "new" action.
DB13 does not have coded such action, therefore it is not able to find it on the "control" tables and also it is not able to find the log.
Advise
1) check if someone changed that entry
2) check if there any "beagpiht*" log file in your system
3) do not play with SDBAC
Another option would be that you are in a MCOD database. Is that the case?