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

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.

• 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:38:51 CDT