cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot read detail log from DB12

ImtiazKaredia
Active Contributor
0 Kudos

Hi,

I am not able to read brbackup and brarchive detail logs in DB12, due to OS level permission problem.

I have brtools permission as below

-rwxrwxr-x 1 bd1adm sapsys 12506376 Feb 1 15:28 brarchive

-rwsrwxr-x 1 orabd1 dba 12937624 Feb 1 15:28 brbackup

-rwsrwxr-x 1 orabd1 dba 15947000 Feb 1 15:28 brconnect

-rwxrwxr-x 1 bd1adm sapsys 13316040 Feb 1 15:28 brrecover

-rwxrwxr-x 1 bd1adm sapsys 3724760 Jan 30 23:43 brrestore

-rwxrwxr-x 1 bd1adm sapsys 16401928 Feb 1 15:28 brspace

-rwsrwxr-x 1 orabd1 dba 5546936 Feb 1 15:28 brtools

Now the logs generated by brbackup and brarchive on OS is like below

-rw------- 1 orabd1 dba 1404 Jun 3 16:00 aeasjsgu.svd

To read file from SAP system we need <sid>adm permission for the file on OS or we need read permission for group sapsys. But above file does not have that permissions and it is controlled by brbackup and brarchive programs.

I run brbackup and brarchive as ora<sid>. These commands are scheduled on OS and not run from DB13.

what do i need to do so that the logs are created such that detail log can be readable from SAP, like DB12

Thanks

Imtiaz

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Imtiaz,

If you want to see BRBACKUP & BRARCHIVE logs from AP Level you can use tcode DB14. I dont think it requires any permission to see the logs from SAP level.

If your SAP CI & DB instance are on different host & if you do not maintain sapxpg rfc destination then you cant see the BRBACKUP or BRARCHIVE logs from DB12 or DB14

Note 108777 - CCMS: Message 'SAPXPG failed for BRTOOLS'

Note 980266 - RFC destination SAPXPG_DBDEST_<DB-HOST> does not work

Check your SAPXPG destination & correct it.

Thanks,

Sushil

Answers (1)

Answers (1)

fidel_vales
Employee
Employee
0 Kudos

for starters, the authorizations of your br* are not correct. check note 113747 for more information.

nevertheless, that will not solve the issue as the file only has authorizations for the owner not for the group.

probably the umask of your user is not correct.

check it (do a "man umask" for information or ask your system administrator)

finally, execute/schedule the commands as <sid>adm not ora<sid>