on 04-02-2009 1:42 PM
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
Hello,
The first thing to check is that the 'brbackup' executable has ownership "orasid" (not "sidadm") and has the set user ID bit set
ls -l /sapmnt/SID/exe/brbackup
-rwsrwxr-x 1 ora<sid> sapsys ... brbackup
The ownership access mask must be "rws", not "rwx"
When brbackup runs out of DB13 it is launched by the sidadm user. If the SUID bit is not set or the ownership is incorrect, then the program itself will run under the sidadm identity instead of orasid, and this will always cause problems. For example, the fact that no file appears in /oracle/SID/brbackup might be due to a permission problem.
Check this out and let us know.
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Mark,
I changed the ownership access mask as suggested by you and the problem got resolved.
Points awarded.
Thanks everybody for your time..
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Basis Team,
Did you chech the log showing that ERROR DURING INITIALIZATION return code 3.
Are you taking bakup in new tape.
If yes, Please initialize the first and take backup.
If you are taking in old tape also, it might not be correct one(sequence).
Just initalize the tape and let us know the result.
Regards
Nick Loy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think you need to manitain the BRBACKUP command in table SDBAC to be able to run a backup from DB13.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>
> 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?
Hi,
did you check beagpiht.afd file in sapbackup directory?
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
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.