Skip to Content
0
Former Member
Feb 27, 2009 at 08:00 AM

New data file permissions

169 Views

Hi all,

Recently we migrated our data centre to other loacation. Now while we are running checkdb on our production server we are getting some error, that related to file perission.

Root Cause: Existing all data files had 775 file permissions and previously it worked with proadm/orapro

But after migration, when we are adding a new data file it is taking 700 permission as default.

And checkdb is runnig with proadm/proadm, which havenot actual permissions.

And we find the temporary solution for this as we are changing new added datafiles to 755.

Then it is gettind executed with proadm/proadm.

But we want to fix this permanently. Here i am hiloghting one thing that umask for orapro is 077. should i change the umask to 022? Then with which permissions new data file be created?

Other wise we need to change the executor of checkdb as proadm/orapro. This was the exact one exixt with our old server. With BRTOOLS i am unable to change these executor.

Please find the start parameters of dbcheck

BR0801I BRCONNECT 6.40 (50)

BR0805I Start of BRCONNECT processing: ceaadfxb.chk 2009-02-27 13.00.11

BR0484I BRCONNECT log file: /oracle/PRO/sapcheck/ceaadfxb.chk

BR0101I Parameters

Name Value

oracle_sid PRO

oracle_home /oracle/PRO/920_64

oracle_profile /oracle/PRO/920_64/dbs/initPRO.ora

sapdata_home /oracle/PRO

sap_profile /oracle/PRO/920_64/dbs/initPRO.sap

system_info proadm/proadm phdb7127 HP-UX B.11.11 U 9000/800

oracle_info PRO 9.2.0.8.0 8192 2321 5052958522

sap_info 620 SAPR3 PRO L1907572054 R3_ORA 0020237303

make_info hp_64 OCI_920 Oct 11 2008

command_line brconnect -u / -jid CHECK20080215130000 -c -f check

alert_log /oracle/PRO/saptrace/background/alert_PRO.log

Regards

Nick Loy