Re: what determines the info sent to the alert log and trace files

"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message news:d4eien$jkn$1_at_nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com...
>
> "Oxnard" <shankeypNO_SPAM_at_comcast.net> wrote in message
> news:UcydneC9SNsb3PXfRVn-2g_at_comcast.com...
>> 9.2.0.5 Aix 5.2.0.0
>> What determines the messages put in the alert log and trace files?
>> Additionally if I wanted to ensure that if the temp tablespace fills up I
>> get a message in the alert log and if possible a trace file is created
>> with the session that had the event happen to them. It would also be good
>> if the SQL the session is running is also put in the trace file.
>>
>
> One option you have for trapping this information
> is to make your sessions resumable - which means
> they will suspend themselves for a while before failing
> if they hit a space management problem,
>
> You can then write an 'after suspend' trigger that checks
> what the problem was and get the trigger to write the
> SQL to the trace file and/or alert log. (Moreover,
> the session will resume automatically if the space
> problem happens to go away). Do a key word
> search on RESUMABLE at tahiti.oracle.com for
> more on resumable sessions.
>
>
> --
> Regards
>
> Jonathan Lewis
>
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
> The Co-operative Oracle Users' FAQ
>
> http://www.jlcomp.demon.co.uk/seminar.html
> Public Appearances - schedule updated April 5th 2005
>
>

That's an interesting idea. I will have to check it out. I will need to test it with the Java thin client as that is what the app uses to connect to the db. Received on Mon Apr 25 2005 - 09:38:18 CDT