brbackup fails when scheduled from DB13

[Former Member]

When we run any activity in DB13 that calls for brackup, the job fails with the below errors:

BR0278E Command output of 'LANG=C cd /oracle/B2Q/102_64/dbs && LANG=C cp initB2Q.ora spfileB2Q.ora /backupsap/B2Q':
cp: /backupsap/B2Q/initB2Q.ora: Permission denied
cp: /backupsap/B2Q/spfileB2Q.ora: Permission denied
BR0280I BRBACKUP time stamp: 2010-04-26 16.31.22
BR0279E Return code from 'LANG=C cd /oracle/B2Q/102_64/dbs && LANG=C cp initB2Q.ora spfileB2Q.ora /backupsap/B2Q': 1
BR0222E Copying init_ora to/from /backupsap/B2Q failed due to previous errors 

Upon further analysis, the problem is because b2qadm is trying to run the backup instead of orab2q. This job is normally executed at the OS level by orab2q. This system has been recently refreshed from production & all post refresh steps have been completed.

Interestingly, the redo log backup runs successfully. In this case the brarchive runs correctly as orab2q.

Upon further analysis, we see the following when we brbackup is trying to run:

backup_root_dir                /backupsap
compress                       no
disk_copy_cmd                  copy
cpio_disk_flags                -pdcu
exec_parallel                  0
system_info                   b2qadm/b2qadm jsapqab2q1e AIX 3 5 00CAD94B4C00
oracle_info                    B2Q 10.2.0.4.0 8192 220 18158716977 jsapqab2q1e WE8DEC UTF8 

If you notice next to system_info it shows b2qadm/b2qadm. Below is what we see when brarchive is successful:

archive_dupl_del               only
system_info                    b2qadm/orab2q jsapqab2q1e AIX 3 5 00CAD94B4C00
oracle_info                    B2Q 10.2.0.4.0 8192 220 18158716977

Here we have b2qadm/orab2q.

The permissions at the OS level are correct as shown below:

-rwsrwxr-x 1 orab2q sapsys 2187607 Apr 26 16:27 brtools

-rwxr-xr-x 1 b2qadm sapsys 5270478 Apr 26 16:27 brspace

-rwxr-xr-x 1 b2qadm sapsys 1883092 Apr 26 16:27 brrestore

-rwxr-xr-x 1 b2qadm sapsys 4239095 Apr 26 16:27 brrecover

-rwsrwxr-x 1 orab2q sapsys 5140465 Apr 26 16:27 brconnect

-rwsrwxr-x 1 orab2q sapsys 3777356 Apr 26 16:27 brbackup

-rwsrwxr-x 1 orab2q sapsys 3666112 Apr 26 16:27 brarchive

Can you please point out what we might have missed?

Edited by: Arshish Bodhanwala on Apr 27, 2010 4:17 PM

[Former Member · Accepted solution]

Hi All,

I have tried the following as per your recommendations:

1) Double checked permissions per note 113747. I set the permissions as per the note.

2) Checked & reassigned the DB roles assigned to OPS$B2QADM & OPS$ORAB2Q.

3) Copied the br* files from B2D (dev system which works) & repeated steps 1 & 2.

The backup still fails. Essentially, what it is trying to do is that it is running brbackup as b2qadm instead of orab2q. This was never a problem prior to the refresh. Below is the actual error from DB13.

BR0370I Directory /backupsap/beddsrdy created
BR0202I Saving init_ora
BR0203I to /backupsap/B2Q ...
BR0278E Command output of 'LANG=C cd /oracle/B2Q/102_64/dbs && LANG=C cp initB2Q.ora spfileB2Q.ora /backupsap/B2Q':
cp: /backupsap/B2Q/initB2Q.ora: Permission denied
cp: /backupsap/B2Q/spfileB2Q.ora: Permission denied
BR0280I BRBACKUP time stamp: 2010-05-04 16.48.49
BR0279E Return code from 'LANG=C cd /oracle/B2Q/102_64/dbs && LANG=C cp initB2Q.ora spfileB2Q.ora /backupsap/B2Q': 1
BR0222E Copying init_ora to/from /backupsap/B2Q failed due to previous errors

I am sure this runs as ora<sid> user usually as this is what is happening in the all the other dev & QA boxes. As an example below is the /backupsap dir listing of dev system B2D:

jsapdvb2d1e:b2dadm 28> cd /backupsap
jsapdvb2d1e:b2dadm 29> ls -lrt
total 56
drwxr-xr-x    2 root     system          256 Jul 25 2007  lost+found
drwxr-xr-x    2 root     system         4096 Jul 27 2007  wft
-rw-r--r--    1 orab2d   dba            9938 Nov 20 15:46 sapdba_role.log
drwxrwx---    2 orab2d   sapsys         4096 May 04 00:06 beddopss
drwxr-xr-x    2 orab2d   sapsys         8192 May 04 00:06 B2D
jsapdvb2d1e:b2dadm 30> cd B2D
jsapdvb2d1e:b2dadm 31> ls -l
total 1768
-rw-r--r--    1 orab2d   sapsys        73006 May 04 00:06 backB2D.log
-rw-r--r--    1 orab2d   sapsys        28763 Apr 04 00:03 becxxdjv.and
-rw-r--r--    1 orab2d   sapsys        28755 Apr 05 00:02 becycbez.and
-rw-r--r--    1 orab2d   sapsys        28857 Apr 07 00:10 becylwvh.and
-rw-r--r--    1 orab2d   sapsys        28771 Apr 07 23:59 becyquqo.and
-rw-r--r--    1 orab2d   sapsys        28784 Apr 09 23:57 beczaqgr.and
-rw-r--r--    1 orab2d   sapsys        28791 Apr 10 23:57 beczfoca.and
-rw-r--r--    1 orab2d   sapsys        28791 Apr 11 23:53 beczklxe.and
-rw-r--r--    1 orab2d   sapsys        28701 Apr 14 00:28 beczuhng.and
-rw-r--r--    1 orab2d   sapsys        28764 Apr 15 00:02 beczzfim.and
-rw-r--r--    1 orab2d   sapsys        28760 Apr 17 00:18 bedajayp.and
-rw-r--r--    1 orab2d   sapsys        28781 Apr 17 23:59 bedanytt.and
-rw-r--r--    1 orab2d   sapsys        28790 Apr 18 23:57 bedaswow.and
-rw-rw----    1 orab2d   sapsys        28760 Apr 21 00:02 bedbcscw.and
-rw-rw----    1 orab2d   sapsys        28760 Apr 22 00:11 bedbhpya.and
-rw-rw----    1 orab2d   sapsys        28760 Apr 24 00:07 bedbrloj.and

-rw-rw---- 1 orab2d sapsys 28767 Apr 24 23:59 bedbwjjn.and

-rw-rw---- 1 orab2d sapsys 28780 Apr 25 23:58 bedcbhet.and

-rw-rw---- 1 orab2d sapsys 28760 Apr 28 00:07 bedclcvm.and

-rw-rw---- 1 orab2d sapsys 28768 Apr 29 00:00 bedcqaqv.and

-rw-rw---- 1 orab2d sapsys 28760 Apr 30 00:08 bedcuyma.and

-rw-rw---- 1 orab2d sapsys 28760 May 01 00:29 bedczwhd.and

-rw-rw---- 1 orab2d sapsys 28761 May 02 00:03 beddeucm.and

-rw-rw---- 1 orab2d sapsys 28770 May 03 00:03 beddjrxq.and

-rw-rw---- 1 orab2d sapsys 28762 May 04 00:06 beddopss.and

-rw-r-xr-x 1 orab2d sapsys 2061 May 03 21:01 initB2D.ora

-rw-r-xr-x 1 orab2d sapsys 19429 May 03 21:01 initB2D.sap

-rw-rr 1 orab2d sapsys 213 May 04 00:06 paramB2D.log

-rw-rr 1 orab2d sapsys 364 May 04 00:06 spaceB2D.log

-rw-r----- 1 orab2d sapsys 4608 May 03 21:01 spfileB2D.ora

-rw-rr 1 orab2d sapsys 631 May 04 00:06 strucB2D.log

jsapdvb2d1e:b2dadm 32>

Edited by: Arshish Bodhanwala on May 4, 2010 7:01 PM

[Former Member · Accepted solution]

 Essentially, what it is trying to do is that it is running brbackup as b2qadm instead of orab2q.

Usually this will be due to a missing s-bit.

And maybe you are using a brbackup program different from the one you think you are using.

As user <sid>adm, what is the output of:

ls -l `which brbackup`

(NB: it's backticks, ` not ')

[Former Member · Accepted solution]

 ls -l `which brbackup`

Thank you , thank you!!!

This solved the problem. The br* files were temporarily stored in /home?b2qadm by the DBAs when they were performing Oracle upgrade. They had incorrect permissions which is why the backup was failing. I deleted those files & now the correct br* are being accessed from the exe dir.

Also thanks to everyone else who provided their insight.

Edited by: Arshish Bodhanwala on May 5, 2010 10:01 AM

[Former Member]

Dear Arshish,

Kindly check the permissiion for init<SID>.ora and spfile<SID>.ora.I think these two files have ora<SID> authorsation because of that <SID>adm not able to copy files to target location . check the permission for target folder as well .

Thanks and Regards,

Arun Kumar

[former_member227600]

Hi,

You have done system refresh . I hope you have completed call post activities of cloning.

Just for confirmation have you ran the below command after system refresh.

grant dba,resource,connect,sapdba to OPS$<SID>ADM OPS$ORA<SID>

And also please check the SAP note for right permission of BR tools.

Thanks & Regards

Karan

[JPReyes]

Just to put things together... You need to make sure that permissions for br* are set correctly for that check SAP Note 113747 as suggested by Rajesh then check that the user has enough rights to read and write to the target backup directory as suggested by Kishore.

Regards

Juan

[kishore_soma]

Dear Arshish,

This is not the brtools permission issue, but this is the permission issue with the backup folder - /backupsap/B2Q

Please change the permission of this folder and try taking the backup once again. Preferrably change it to 777 with any user and group. try to create file file with ora<sid> and <sid>adm user in this folder.

Regards,

Kishore Soma

[Former Member]

Hi Arshish,

-rwsrwxr-x 1 orab2q sapsys 2187607 Apr 26 16:27 brtools

Permission for the "brtools" is not correct... Please notice sticky bit

It should be 755

-rwxr-xr-x <sid>adm sapsys  brtools

Please have a close look at the below note:

[SAP Note 113747 - Permissions for DBA tools BR*Tools and SAPDBA|https://service.sap.com/sap/support/notes/113747]

Again, backup directory ( /backupsap ) should be writable for at least ora<sid>:sapsys user.

Then try once again...

Regards.

Rajesh Narkhede

[Former Member]

DB13 jobs always started as SIDADM.

Refer the note link below for details.

Link: [https://service.sap.com/sap/support/notes/437648]

In your case, it needs a write permission to the backup directory /backupsap/B2Q directory.

Simply execute "chmod 775 /backupsap/B2Q" since sidadm has the group dba.

[Former Member]

Hi Arshish,

Looks like you have done a complete analysis on this. Before going for any further analysis in this path, can you please check the permission for b2qadm in /backupsap/B2Q does it have write permission to the files inside the directory.

Regards,

Sanujit