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

One minor additional point: this technique will only produce a trace file on the error event itself. It will not produce a voluminous spew of text for either other sql statements or other sessions. An obvious approach would be to use the sql trace trace facility, but then you have mountains of trace files and significant overhead until the actual offending event is encountered. This error trap technique is much simpler and can be done in a production environment.

• ricky

Stan Brown wrote:

> I have a third party application that logs to an Oracle 7.3.4 instance.
>
> I'm in the process of upgrading the app to a newer version, and I'm
> sudenly getting the follwoing in one of it's log fiels:
>
> ORA-01401: inserted value too large for column
>
> Now, since nothing about aht it's trying to log (data waise) _should_ have
> changed, I'm puzzled. It's definatley the application, as I can run the
> old version against the same new Oracle isntace and get the data loged,
> but if I run the new version of the application against it, I get this
> error.
>
> So (finally) here's the question. How can I configure Oracle to give me
> the gory details f what the appliaction is requestiong Oracle to do,
> preferably just when it fails, as the application ogs _a lot_ of data to
> Oracle.
>
> Thanks.
Received on Mon May 07 2001 - 19:44:20 CDT