I prefer to seperate udump, bdump and cdump. Developers have a habit of putting in "ALTER SESSION SET SQL_TRACE=TRUE" for certain programs and I get lots of such trace files. They go the udump. I have a CRON job cleaning up the udump [compress files older than 5 days, delete files older than 30 days], leaving bdump untouched. One particular database with Intermedia in 8.1.7.2 core-dumps frequently updating Intermedia indexes. The core-dumps go to cdump and can be purged by another CRON job. Hemant At 02:51 PM 03-02-04 -0700, you wrote: >We are currently working installing a 9i db on a new box. The senior dba >wants to put all trace files into one directory on $ORACLE_HOME/rdbms/log. >I've suggested that this is not the best practice prescribed by OFA. Does >anyone see any major issues with keeping all trace files in one directory? > >Thanks, > >Mark >---------------------------------------------------------------- >Please see the official ORACLE-L FAQ: http://www.orafaq.com >---------------------------------------------------------------- >To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx >put 'unsubscribe' in the subject line. >-- >Archives are at //www.freelists.org/archives/oracle-l/ >FAQ is at //www.freelists.org/help/fom-serve/cache/1.html >----------------------------------------------------------------- Hemant K Chitale Oracle 9i Database Administrator Certified Professional http://hkchital.tripod.com {last updated 24-Jan-04} ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------