Re: Trace Files(*.trc)

From: Rick Wessman <rwessman_at_rwessman.us.oracle.com>
Date: 1995/04/05
Message-ID: <RWESSMAN.95Apr5073429_at_rwessman.us.oracle.com>#1/1


Making trace files publicly readable is dangerous. Trace files can contain all sorts of information that a user should not see.

In general, trace files are only created when there is a problem that the DBA should address. That's why the permissions are set as they are.

                                Rick

In article <3lruko$4pu_at_athos.cc.bellcore.com> parris_at_walleye.esp.bellcore.com (Parris Geiser) writes:

>Path: dcsun4.us.oracle.com!gatekeeper.us.oracle.com!decwrl!pa.dec.com!decuac.dec.com!haven.umd.edu!cs.umd.edu!eff!usenet.ins.cwru.edu!howland.reston.ans.net!cs.utexas.edu!uunet!athos.cc.bellcore.com!walleye!parris
>From: parris_at_walleye.esp.bellcore.com (Parris Geiser)
>Newsgroups: comp.databases.oracle
>Date: 4 Apr 1995 17:11:52 GMT
>Organization: Bellcore
>Lines: 32
>References: <D6B94D.6yA_at_uunet!aadt>
>NNTP-Posting-Host: walleye.esp.bellcore.com
>X-Newsreader: TIN [version 1.2 PL2]
>
>Prabhinder Singh (psingh_at_aadt.com) wrote:
>> 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 .
 

>> Your help would be appreciated in resolving this issue.
>>
>> --
>> Prabhinder Singh SABRE Decision Technologies
>> (817)963-1112 (O) P. O. Box 619616, MD 4479
>> CP-IV: 3W5B-53 Dallas/Fort Worth Airport,
>> (817)967-9763 (FAX) Texas 75261-9616
>> e-mail: psingh_at_sdt.com
>
>Funny how everyone seems to have the same problems ...
>My solution was to write a simple C program (under UNIX) with the executable
>having mode u+s. The C program copied the existing file to /tmp so the user
>could look at it there. I put the executable in the directory specified
>by DUMP_DESTINATION. Hope that this helps.
> parris geiser
Received on Wed Apr 05 1995 - 00:00:00 CEST

Original text of this message