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

or ALTER SYSTEM SET SQL_TRACE=TRUE;

That should work w/o bouncing the db.

--

Syltrem
http://pages.infinit.net/syltrem (OpenVMS related web site)
To reply to myself directly, remove .spammenot from my address

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> a écrit dans le message news:
tfe28d7mjasg04_at_beta-news.demon.nl...


> sql_trace = true in init.ora

> will produce trace files in the directory pointed to by the user_dump_dest

> parameter.

> The trace file will contain the erroneous statement preceded by err=1041

> You need to bounce the database to enable tracing.

>

> Hth,

>

> Sybrand Bakker, Oracle DBA

>

> "Stan Brown" <stanb_at_panix.com> wrote in message

> news:9d6pt5$7jl$1_at_panix6.panix.com...

> > 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.

> >

>

>