Speaking off the cuff, I can't think of a technical reason. I wouldn't do it, as I like to keep the users trace files separate from the alert log and system trace files. Setting _trace_files_public may raise some issues when udump and bdump point to the same directory, though I have not tried it. How about cdump? Why not put them there as well? Jared Mark Moynahan <Mark.Moynahan@xxxxxxxxxxxxx> Sent by: oracle-l-bounce@xxxxxxxxxxxxx 02/03/2004 01:51 PM Please respond to oracle-l To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx> cc: Subject: OFA - dump destinations 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 ----------------------------------------------------------------- ---------------------------------------------------------------- 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 -----------------------------------------------------------------