on 11-27-2007 1:59 AM
Hi Experts
While checking DB13 , the BRCONNECT action log return an error :
BR0252E Function stat() failed for '/oracle/PM1/sapdata5/btabd_19/btabd.data19' at location BrFileStatGet-1
BR0253E errno 13: Permission denied
BR0273E Determination of file status for /oracle/PM1/sapdata5/btabd_19/btabd.data19 failed
I suspected the reason was yesterday , I had extended the tablespace PSAPBTABD by adding a datafile " /btabd_19/btabd.data19" using BRTOOLS. After adding this datafile , the backup last night returned this error when I checked this morning.
While looking at previous datafiles , I discovered , example: btabd.data18 ( -rw-r-- ) , btabd.data17 ( -rw-rw) , and the new datafile btabd.data19 is only ( -rw--
) .
Any suggestions guys? Hope someone can help me on this. Thanks in advance.
1st, as orapm1 do this:
chmod g+rw '/oracle/PM1/sapdata5/btabd_19/btabd.data19'
This will fix the file permission issue and your backup will run fine next run.
2nd, if you used BRTOOLS as orapm1 to extend the file system, check umask as other users suggested, it seems your umask is likely to be 066. try make it 026 or 006 before you run brtools.
Explainations:
The backup failed as you observed because pm1adm does not have read access to the datafile you newly added. (When you schedule backup in DB13, the backup run as pm1adm). It is also because your br* in /sapmnt/PM1/exe does not have the sticky bit on, so brbackup cannot access the file.
The files is created with default unix settings, so likely umask is here to play causing the newly created datafile has no read permission for the dba group.
Usually you should alow dba group to read the datafile (unless you have special security requirements). which means the permission should look like "-rw-r-----"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guys
Thanks Somckit , Eric and Alan for your contribution.
I think I posted the wrong permission of my Brtools.
The correct permission I found in production is currently:
root@HRPRD [/sapmnt/PM1/exe]
ll br*
-rwxr-xr-x 1 orapm1 sapsys 10817352 Sep 11 2006 brarchive
-rwxr-xr-x 1 orapm1 sapsys 11209344 Sep 11 2006 brbackup
-rwxr-xr-x 1 orapm1 sapsys 14262128 Sep 11 2006 brconnect
-rwxr-xr-x 1 pm1adm sapsys 11570704 Sep 11 2006 brrecover
-rwxr-xr-x 1 pm1adm sapsys 3302568 Sep 9 2006 brrestore
-rwxr-xr-x 1 pm1adm sapsys 14549992 Sep 11 2006 brspace
-rwxr-xr-x 1 orapm1 sapsys 4794304 Sep 11 2006 brtools
1.I already change btabd.data19 to chmod g+rw btabd.data19 resulting : -rw-rw----
Hopefully the backup tonight will return with no errors with brconnect when I run DB13 tomorrow.
This solves the datafile issue.
2.
a. Should I set chmod should I set all my br* to? 4755? except brrestore ( recommended by OSS 8523)
Hope this will solve all issues , should I use BRtools to extend tablespace again.
b. Should I chown orapm1:sapsys for brspace and brrecover ?
Thanks everyone for your help .
consider running scripts saproot.sh
more info about this at http://help.sap.com/saphelp_nw2004s/helpdata/en/43/3753c4b87b6025e10000000a422035/content.htm
If you are on NetWeaver 2004s, do as Eric suggested. If you are on an older version, do this:
brarchive, brbackup, brconnect, brtools have permission 4775:
-rwsrwxr-x orapm1 sapsys ...
These can be started by the orapm1 or the pm1adm OS user.
brrestore, brrecover, brspace, and sapdba have permission 755:
-rwxr-xr-x pm1adm sapsys ...
These can only be started by the orapm1 OS user.
You still need to check your umask for your orapm1, it still has an impact on how the datafile permissions are set when you create them. If you umask (just type "umask" before you run brtools/brspace as orapm1) is 066 or bigger, you will have this issue again next time you add a datafile.
If you umask is 026 or lower, you should be fine next time adding datafile with brspace/brtools.
Hi Guys
Sorry for the late reply. Thank you all for your contributions.
I had successfully chmod the br* to the suggested modes and from sap , DB13 runs without error.
However , like all has suggested , the issue will resurface when I add datafile again.
From orapm1 , umask is 077. How do I change to the correct one.
Thanks.
Are you asking for the root cause or an immediate fix?
The " /btabd_19/btabd.data19" datafile you added looks very suspicious here..
The immediate fix would be something like:
chown orapm1:dba /sapmnt/PM1/exe/br*
chmod 4755 /sapmnt/PM1/exe/br*
You basically want the setuid bit enabled for the br* executables.
Or maybe you can post the existing permissions for your br* executables?
Another fix would be to:
chmod 755 /path_to/btabd.data19
That would only fix this file's issue though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys
Heres what I found in/sapmnt/SID/exe :
-rwxr-x--- 1 oradm1 sapsys 10817352 Sep 14 2006 brarchive
-rwxr-x--- 1 oradm1 sapsys 11209344 Sep 14 2006 brbackup
-rwxr-x--- 1 oradm1 sapsys 14262128 Sep 14 2006 brconnect
-rwxr-x--- 1 oradm1 sapsys 11570704 Sep 14 2006 brrecover
-rwxr-x--- 1 oradm1 sapsys 3302568 Sep 14 2006 brrestore
-rwxr-x--- 1 oradm1 sapsys 14549992 Sep 14 2006 brspace
-rwxr-x--- 1 oradm1 sapsys 4794304 Sep 14 2006 brtools
Seems outdated. Any ideal permission should be changed?
Thanks.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
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.