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@(protected)> 02/24/2005 04:07 PM
To "'Tony.Adolph@(protected)'" <Tony.Adolph@(protected)>, oracle-l@(protected) cc Jonas.Kilian@(protected) Subject RE: ORA-01401 (See ORA-01401.ora-code.com): 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@(protected) [mailto:Tony.Adolph@(protected)] Verzonden: Thursday, February 24, 2005 14:30 Aan: oracle-l@(protected) CC: Jonas.Kilian@(protected) Onderwerp: ORA-01401 (See ORA-01401.ora-code.com): inserted value too large for column
Hi all, A developer here is trying to find the source of the error "ORA-01401 (See ORA-01401.ora-code.com): 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 (See ORA-01401.ora-code.com). I tried to grep for just the 1401 string, still nothing.
