Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: ORACLE USER TRACE FILE PERMISSION

Re: ORACLE USER TRACE FILE PERMISSION

From: MarkP28665 <markp28665_at_aol.com>
Date: 1998/01/27
Message-ID: <19980127232601.SAA18800@ladder02.news.aol.com>#1/1

From: azaman <azaman_at_ibm.net> >>
Under unix, the user trace files are generated in RBMS/udump directory. Oracle recomends that this directory should have 660 permission which precludes any developers from viewing those files. <<

If it is really necessary that a developer be able to view trace files and run tkprof against trace files then you may request that the DBA group change the directory premissions and set up a cron job that changes the file premissions every 15 minutes or so.

I have found that most developers are better off just to run explain plans against the problem code. You can monitor the sql being executed by a process as it runs to see where a process spends most of its time, but I always encourage developers to explain every sql statement in their program against the production environment before it runs for the first time.

Trace output is pretty well useless unless you run tkprof against it and tkprof output requires serious study to really be able to use it.

Good Luck.

Mark Powell -- Oracle 7 Certified DBA
- The only advice that counts is the advice that you follow so follow your own advice - Received on Tue Jan 27 1998 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US