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

Yes, it should be there. If you set the event in the init<sid>.ora file and bounced the instance and used the correct syntax, then you should expect the file to be there for whatever shadow process encountered the error. If you did the "alter session..." bit and some different, un-altered session encountered the error, then you won't have a trace file. The init<sid>.ora method applies the event setting to all sessions once the instance is bounced.

• ricky

Stan Brown wrote:
>
> 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.
>
> OK, I feel stupid here :-(
>
> I set up this trap, bounced the DB, waited for the event to happen (only
> happens once an hour), and now that it should have happened, I can't seem
> to find where this dump went :-(
>
> Would it be a .trc file? I did a find for such, and did not find one that
> seemed to have the correct timepstamp.
>
> I have the follwing setings in the init files for this isntance:
>
> background_dump_dest = /oracle_home/app/oracle/admin/pwhse/bdump
> core_dump_dest = /oracle_home/app/oracle/admin/pwhse/cdump
> user_dump_dest = /oracle_home/app/oracle/admin/pwhse/udump
>
> Would it be in one of these? If so, I must be overlooking it.
>
> And thanks again for the help.
Received on Sat May 12 2001 - 19:06:10 CDT