From: Tony@santen.demon.co.uk (Tony Rothwell)
Subject: Re: Trace Files(*.trc)
Date: 1995/04/04
Message-ID: <646826613wnr@santen.demon.co.uk>#1/1
sender: usenet@demon.co.uk
references: <D6B94D.6yA@uunet!aadt>
x-posting-host: santen.demon.co.uk
organization: Santen Limited
reply-to: Tony@santen.demon.co.uk
newsgroups: comp.databases.oracle


In article: <D6B94D.6yA@uunet!aadt>  psingh@aadt.com (Prabhinder Singh) 
writes:
> 
> Question: When we use the sql trace facility then corresponding to each
> sql statement executed thereafter the oracle generates a trace file 
 (*.trc)
> in the directory specified in DUMP_DESTINATION  variable of init ora.
> The default destination is oracle/rdbms/log. But when oracle creates this
> trace file it does not give  read permission to the user. The permissions 
 looks
> like
> 
> -rw-rw----   1 oracle   dba          412 Mar 18 15:57 ora_13206.trc
> 
> This shows that trace file created corresponding to  any "xyz" user's 
 query 
> cannot be accessed by that user itself. This trace file can either be 
 accessed by
> Oracle or any user having DBA group.

There's a little-known initialization parameter you can set
which causes trace files to be created with public access:

_TRACE_FILES_PUBLIC = TRUE

I think the name's right (if not, I'm sure someone will
correct me!); the leading underscore is intentional.

-Tony.