RE: ORA-01401: inserted value too large for column

Hi Jeroen,
Thanks for the feedback.

The application is only loging the oracle error and not to which table / column it refers.

I thought the 10046 event is more approriate for tracing wait events etc... not the case? The application's session only runs for a few seconds before the error occurs. How would be the best way to alter the session? Code it into the app just for testing?

Tony

Jeroen van Sluisdam <jeroen.van.sluisdam_at_thomascook.nl> 02/24/2005 04:07 PM

To
"'Tony.Adolph_at_o2.com'" <Tony.Adolph_at_o2.com>, oracle-l_at_freelists.org cc
Jonas.Kilian_at_o2.com
Subject
RE: ORA-01401: inserted value too large for column

Hi,

Somne logging in the application?
When PL/SQL is involved this error might occur also when variables are defined too small.
extented trace like
execute immediate 'alter session SET EVENTS ''10046 trace name context forever, level 12''';

Check last-sql statement in tracefile
Regards,

Jeroen

-----Oorspronkelijk bericht-----

Van: Tony.Adolph_at_o2.com [mailto:Tony.Adolph_at_o2.com] Verzonden: Thursday, February 24, 2005 14:30 Aan: oracle-l_at_freelists.org
CC: Jonas.Kilian_at_o2.com
Onderwerp: ORA-01401: inserted value too large for column

Hi all,
A developer here is trying to find the source of the error "ORA-01401: inserted value too large for column". He want to know which table / column(s) are causing the problem.

The error is not logged in the alert log.

I set sql_trace = true and had him repeate his tests. Although we got bucket loads of trace files in both user_dump_dest and backfround_dump_dest
we did not get any trace files or errors relating to ORA-01401. I tried to
grep for just the 1401 string, still nothing.

How can find the culprit here folks?

Cheers
Tony

--

http://www.freelists.org/webpage/oracle-l

--

http://www.freelists.org/webpage/oracle-l Received on Thu Feb 24 2005 - 10:30:17 CST