Re: Tracing Question

Sybrand Bakker wrote:
> On 13 Dec 2004 12:09:12 -0800, amerar_at_iwc.net wrote:
>
> >
> >Hi All,
> >
> >I'm not sure this is really a tracing question, but here is the
> >problem:
> >
> >We have a department that runs Oracle 8.1.7.3. The application is
400+
> >Microfocus COBOL programs, poorly written. Anyhow, when an error
> >occurs, the program spits out a unique error message so you know
where
> >in the program it went down, but you have no idea on which record
was
> >being processed at that time.
> >
> >My company does not want to change the programs, as when new relases
> >come out, we would have to retrofit.
> >
> >I'm looking for a creative was to basically trap the error when it
> >happens, and log all the info on the SQL statement, including bind
> >variable values.....
> >I am at a loss now and I'm looking for some help.
> >
> >Thanks,
> >
> >Arthur
>
> alter session set event = '<error number> errorstack context forever,
> level 3' will accomplish this. You can also set this in init.ora and
> using alter system.
> You'll need to set an event for every individual error.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA

Thanks for the reply. Once I get one of these trace files, how can I read it? I do not want to call Oracle support each and every time I need to understand a file.....are there scripts out there to disect this massive file?

Arthur Received on Tue Dec 14 2004 - 10:34:40 CST