cancel
Showing results for 
Search instead for 
Did you mean: 

Brtools unable to extend the tablespace

Former Member
0 Kudos

Dear Experts.

I am trying to extend the tablespace but getting error, i have tried digging into the issue and checked the permissions and updated the brtools with latest available still the same error. The issue is arising after system refresh. Please find the screenshot attached.

Experts please help me to resolve the issue.

Thanks & Regards

Mohd

Accepted Solutions (1)

Accepted Solutions (1)

fidel_vales
Employee
Employee
0 Kudos

Probably it is a problem with the BR* authorizations.

Check the owner, group, and access authorizations as indicated on SAP Note 113747.

Former Member
0 Kudos

Dear Experts.

To set the right permissions i have stoped sap and run the ./saproot.sh SID script and login with ora<sid> user and got the below error.

Please Help.

Thanks in Advance.

Regards

Mohd

fidel_vales
Employee
Employee
0 Kudos

OK,

can you post the output of

<from the location of the BR*Tools>


ls -ls br*

ls -ls /oracle/Q01/

ls -ls /oracle/Q01/sapreorg/space*

Thanks

Former Member
0 Kudos

Dear Fidel.

The  output is as below:

development:oraq01 51> cd /sapmnt/Q01/exe

development:oraq01 52> ls -ls br*

9320 -rwsrwxr-- 1 oraq01 sapsys  9523638 Aug 30 04:24 brarchive

9320 -rwsrwxr-- 1 oraq01 dba     9523638 Oct 16 20:06 brarchive_old

9444 -rwsrwxr-- 1 oraq01 sapsys  9653882 Aug 30 04:24 brbackup

9444 -rwsrwxr-- 1 oraq01 dba     9653882 Oct 16 20:07 brbackup_old

11312 -rwsrwxr-- 1 oraq01 sapsys 11563819 Aug 30 04:27 brconnect

11312 -rwsrwxr-- 1 oraq01 dba    11563819 Oct 16 20:08 brconnect_old

9896 -rwxr-xr-x 1 q01adm sapsys 10116618 Aug 30 04:28 brrecover

9896 -rwsrwxr-- 1 oraq01 dba    10116618 Oct 16 20:08 brrecover_old

6188 -rwxr-xr-x 1 q01adm sapsys  6320328 Aug 30 04:28 brrestore

6188 -rwsrwxr-- 1 oraq01 dba     6320328 Oct 16 20:09 brrestore_old

11736 -rwxr-xr-x 1 q01adm sapsys 11998063 Aug 30 04:59 brspace

11736 -rwsrwxr-- 1 oraq01 dba    11998063 Oct 16 20:10 brspace_old

6752 -rwxr-xr-x 1 q01adm sapsys  6898218 Aug 30 04:59 brtools

6752 -rwsrwxr-- 1 oraq01 dba     6898218 Oct 16 20:11 brtools_old

development:oraq01 53>

development:oraq01 53> ls -ls /oracle/Q01/

total 288

4 drwxrwx---  3 oraq01 dba   4096 May  4  2013 102_32

4 drwxr-xr-x 61 oraq01 dba   4096 Jun 14  2013 102_64

8 -rw-r--r--  1 oraq01 dba   4823 Jun 15  2013 bkp.dbenv_development.csh

8 -rw-r--r--  1 oraq01 dba   4790 Jun 15  2013 bkp.dbenv_development.sh

4 -rw-r--r--  1 oraq01 dba     81 Jun 15 12:11 cocon.sql

12 -rw-r--r--  1 oraq01 dba  11552 Jun 15 00:42 controlfile.sql

12 -rwxrwxrwx  1 root   root  9516 May  4  2013 control.sql

4 -rw-r--r--  1 oraq01 dba    895 May 22  2013 LASVerify.pse

4 drwx------  2 root   root  4096 Jan  2  2014 lost+found

4 drwxr-xr-x  2 oraq01 dba   4096 Oct  3 03:46 mirrlogA

4 drwxr-xr-x  2 oraq01 dba   4096 Oct  3 03:46 mirrlogB

12 drwxrwxrwx  2 oraq01 dba   8192 Oct 27 19:01 oraarch

4 -rw-r--r--  1 oraq01 dba   1658 Jun 15 12:11 oradbusr.log

20 -rw-r--r--  1 oraq01 dba  19327 Feb  7  2006 ORADBUSR.SQL

4 drwxr-xr-x  3 oraq01 dba   4096 Oct  3 03:46 origlogA

4 drwxr-xr-x  3 oraq01 dba   4096 Oct  3 03:46 origlogB

4 drwxrwxrwx  2 oraq01 dba   4096 Oct 23 02:53 saparch

12 drwsrwxr-x  2 oraq01 dba  12288 Oct 23 02:48 sapbackup

12 drwxrwxrwx  2 oraq01 dba  12288 Oct 22 07:01 sapcheck

4 drwxr-xr-x 26 oraq01 dba   4096 Oct  3 20:42 sapdata1

4 drwxr-xr-x 36 oraq01 dba   4096 Oct  3 20:54 sapdata2

4 drwxrwxrwx 27 oraq01 dba   4096 Oct 27 18:28 sapdata3

4 drwxr-xr-x 28 oraq01 dba   4096 Oct  3 21:12 sapdata4

4 drwxr-xr-x 66 oraq01 dba   4096 Oct  3 21:30 sapdata5

4 drwxr-xr-x 25 oraq01 dba   4096 Oct  3 21:39 sapdata6

4 drwxr-xr-x 50 oraq01 dba   4096 Oct  3 21:54 sapdata7

4 drwxrwxrwx  8 oraq01 dba   4096 Oct 27 18:28 sapreorg

4 drwxrwxrwx  4 oraq01 dba   4096 Oct  3 01:28 saptrace

24 -rw-r-----  1 oraq01 dba  22065 May  4  2013 sqlnet.log

20 -rwxr-xr-x  1 oraq01 dba  16688 Apr 21  2011 startdb

4 -rw-r--r--  1 oraq01 dba    795 Jan  3  2014 startdb.log

4 -rw-r--r--  1 oraq01 dba    359 Sep 28 19:58 startsap.trc

12 -rwxr-xr-x  1 oraq01 dba  12049 Apr 21  2011 stopdb

4 -rw-r--r--  1 oraq01 dba    603 Jun 16  2013 stopdb.log

4 -rw-r--r--  1 oraq01 dba    193 Jun 22  2013 stopsap.trc

4 drwxr-xr-x  2 root   root  4096 Jun 14  2013 Suchit

12 -rw-r--r--  1 root   root  9605 May 23  2012 test1.sql

12 -rw-r--r--  1 root   root  9548 May  4  2013 test.sql

12 -rw-r--r--  1 oraq01 dba  10242 Oct 13 15:49 trans.log

development:oraq01 54>

development:oraq01 54> ls -ls /oracle/Q01/sapreorg/space*

8 -rw-r--r-- 1 q01adm sapsys 5460 Oct 27 18:28 /oracle/Q01/sapreorg/spaceQ01.log

development:oraq01 55>

Thanks alot for your valuable support.

Regards

Mohd

fidel_vales
Employee
Employee
0 Kudos

Hi,

if you do not see the issue, then you have a concept problem. I would recommend you to review how authorizations work in an UNIX system.

The tools have the correct authorizations. In particular brspace have the following ones:


11736  -rwxr-xr-x 1 q01adm sapsys 11998063 Aug 30 04:59 brspace

q01adm can execute it, any user belonging to sapsys can execute it and any user belonging to any other group can execute it. Nothing more (nothing less)

this tool tries to write the brspace log (your "authorization" problem)


-rw-r--r-- 1 q01adm sapsys 5460 Oct 27 18:28 /oracle/Q01/sapreorg/spaceQ01.log

This file can be read by q01adm, by any user belonging to sapsys and by any user belonging to any other group.

But what about writing it? only the user q01adm can write on this file, nobody else (except root, of course), therefore if you execute brspace with any user not q01adm it will give you an error trying to open the mentioned file for writing.

I assume brspace was executed with wrong authorizations (with the user q01adm) and was left with this authorizations.

What you have to do is to change the authorizations for this file so anyone form group sapsys can write it (please, do not change it so anyone can write it)

I leave you to find out how to do it.

also check the main group for the user q01adm as I see a lot of files belonging to this user but group dba so I also assume this is wrong

Former Member
0 Kudos

Dear Fidel.

The Issue got resolved by changing the owner to ora<sid>, dba group and changing the file access permissions to 644.

Thanks a lot for your valuable support.

I also thanks all others who have actively took part in resolving the Issue.

Regards

Mohd.

Answers (3)

Answers (3)

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

The screenshot says that BRSPACE is unable to create the directory. Under which user are you running the Brtools ? Check if the ownership and permissions are correct for the BR* files and also make sure that the ora<SID> and <SID>adm users are part of the Oracle and SAP groups.

Former Member
0 Kudos

Hello,

Create that folder manually (mkdir -p /oracle/Q01/sapdata5/q01701_30) and give a try.

regards,

pavan

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi,

Can you get me the log files ?

Regards,

Former Member
0 Kudos

Dear Divyanshu.

Thanks alot for your prompt reply, please find the logs files attached.

Thanks & Regards

Mohd

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi,


BR0252E Function mkdir() failed for '/oracle/Q01/sapdata7/q01701_30' at location

BrDirCreate-1

BR0253E errno 13: Permission denied

If you the above statement, the current user is not having permission to use the OS command 'mkdir', i.e., to make directory at above location.

1st check the user has access to these location and authorization for standard OS programs with the group assigned to user.

2nd, if permission problem is fixed, try using BR*tools so some different version.

Regards,

Former Member
0 Kudos

Hello

Please make sure the belwo

1.  check whether the sapdata filesystems and files under those are owned by oraq01 user.

2. check $ORACLE_HOME/bin/oracle file permission. should be 6751

3. check the Br* tools executable permissions.

(1)
ora<sid> belongs to the dba group,
<sid>adm belongs to the sapsys group,


(2)

The ops$<sid>adm Oracle user must be
created in the DB and must have the sapdba role (not DBA!) (refer to Note 134592
for more information about the role).


(3)

brrestore, brrecover, brspace, and brtools
belong to <sid>adm and have authorization 755:

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

Thanks ,Siva