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: Enable tracing.

Re: Enable tracing.

From: David Fitzjarrell <oratune_at_aol.com>
Date: Fri, 17 Nov 2000 19:32:19 GMT
Message-ID: <8v4144$1g6$1@nnrp1.deja.com>

In our last gripping episode vdolt_at_my-deja.com wrote:
> I am running 8.1.6 on Win2000.
> I am getting Oracle error message "Failed to retrive user
 credentials "
> Oracle manual suggests to enable tracing in order to find out exact
> source of error.
> What does it mean "to enable tracing" and how do I do that?
> Thanks.
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

There are two ways to enable tracing -- per instance and per session -- and since you cannot connect to the instance the per session tracing won't do much good. The only option, as I see it, is to set the following init<SID>.ora parameter to the value specified:

sql_trace = true

This parameter MAY already be in the init<SID>.ora file, disabled by a '#'. If that is the case simply remove the '#'. Once the init<SID>.ora file is edited you must shut down the instance and then start it up again (this is the only way to implement changes to the init<SID>.ora file). This will start dumping trc files in the user_dump_dest specified. Look through those to determine what is causing your error. A better error message (although not the best in many cases) usually appears in trace files.

--
David Fitzjarrell
Oracle Certified DBA


Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Fri Nov 17 2000 - 13:32:19 CST

Original text of this message

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