Link to home
Start Free TrialLog in
Avatar of evevea
evevea

asked on

Trace files written to $ORACLE_HOME/rdbms/log direcory

Even though  background_dump_dest, user_dump_dest       and core_dump_dest are defined in the parameter file,  some trace files still get written to default destination $ORACLE_HOME/rdbms/log . Permissions on the OS-Level are set up too. What makes oracle to write to all these destinations ?
ASKER CERTIFIED SOLUTION
Avatar of sathyagiri
sathyagiri
Flag of United States of America image
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of MohanKNair
MohanKNair
Check the server for initilization parameters

SQL>
SQL> show parameter dump_dest
SQL>
Avatar of evevea
evevea

ASKER

It shows the right folders
background_dump_dest             string      /u01/app/oracle/admin/PROD/bdump
core_dump_dest                       string      /u01/app/oracle/admin/PROD/cdump
user_dump_dest                       string      /u01/app/oracle/admin/PROD/udump

I also checked some dates and found out that originally after db was cloned and brought up successufully it did  write into proper folders but after the next shutdown started using the default one $ORACLE_HOME/rdbms/log
SOLUTION
Avatar of MohanKNair
MohanKNair
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of evevea
evevea

ASKER

Thanks for the hints but I checked permissions again and both of the folders whether
/u01/app/oracle/admin/PROD/bdump or $ORACLE_HOME/rdbms/log have the same permissions, both owned by oracle user who have read, write, execute. Also there is enough space.  We are using Oracle 9.2.06. I cannot afford to turn trace on right now because it will create major slowdown in production environment.