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: Getting Oracle to tell me why it's unhappy

Re: Getting Oracle to tell me why it's unhappy

From: Stan Brown <stanb_at_panix.com>
Date: 8 May 2001 06:51:22 -0400
Message-ID: <9d8j3a$6r5$1@panix3.panix.com>

In <3AF74024.332D2D79_at_more.net> Ricky Sanchez <rsanchez_at_more.net> writes:

>In you init<sid>.ora file, put the following event
>event = "1401 trace name processstate level 10"
 

>Then bounce the instance and recreate the problem.
 

>If you can recreate the evil sql statement at will from a user session, then
>you don't have to bounce the instance. You just do this from a sql prompt:
 

>alter session set events '1401 trace name processstate level 10';
 

>Then recreate the problem.
 

>This will create a trap for an error 1401, which will force a process state
>dump into a trace file for the session that encounters that error. Buried in
>the maze of details will be the current sql statement.
 

>When the whole deal is over, take out the event from the init file or just exit
>the user session, depending on how you set the event.

	Thnaks, I can't repproduce the statement (If I could I wouldn't need to
	sue Oracle to tell me what it is :-)), so your first sugestion will
	work for me.
Received on Tue May 08 2001 - 05:51:22 CDT

Original text of this message

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