Re: ORA-01401: inserted value too large for column
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: Tony.Adolph@xxxxxx
- Date: Thu, 24 Feb 2005 20:22:58 +0000
Comments embedded
On Thu, 24 Feb 2005 14:30:18 +0100, Tony.Adolph@xxxxxx
<Tony.Adolph@xxxxxx> wrote:
> 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.
That would be normal, it should be thrown back to the offending
application. All this rather suggests that the app could do with
rather better exception handling, c'est la vie.
> 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.
If you set this at the instance level - which it rather sounds like
you did - I suggest you unset it before you fill the disk!
> I tried to grep for just the 1401 string, still nothing.
>
> How can find the culprit here folks?
A number of ways.
You can set a 1401 event in the init.ora/spfile
You can persuade the developer to set event 10046 at logon.
You could even persuade them to use DBMS_APPLICATION_INFO
You can use an after servererror trigger like the one I posted for the
temp tablespace error a couple of days ago.
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
