Re: Trace Files(*.trc)

From: Tony Jambu <aaj_at_phantom.telecom.com.au>
Date: 1995/04/10
Message-ID: <3ma87t$nng_at_newsserver.trl.OZ.AU>#1/1


In article <D6B94D.6yA_at_uunet!aadt>, psingh_at_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.
> My problem is that neither I can allow every user in the development team
> to login as an oracle nor I can add them to DBA group. So what should I do
> so that developers in my team can use these trace files .
>

Are you using Oracle V6 or 7? It would be helpful also if you could tell us your version and release number.

If you are using Oracle7, there are few things to look out for.

  1. Use of the undocumented INIT.ORA parameter, _TRACE_FILES_PUBLIC=TRUE
  2. Use of UNIX's SUID on the sub-directory
  3. Oracle's umask itself. Should be something like 022.

If version 6, point 2 amd 3 applies.

Hope that helps

ta
tony

-- 
 _____       ________ / ___ |Tony Jambu, Database Consultant
  /_  _        /_ __ /      |Wizard Consulting,Aust (ACN 065934778)
 /(_)/ )(_/ \_/(///(/_)/_(  |CIS: 100250.2003_at_compuserve.com FAX: +61-3-4163559
 \_______/                  |EMAIL:TJambu_at_wizard.com.au PHONE: +61-3-4122905
Received on Mon Apr 10 1995 - 00:00:00 CEST

Original text of this message