Re: ORA-12899: value too large for column with Oracle Patch 10.2.0.4
Date: Tue, 07 Oct 2008 06:38:50 -0700
Arne Ortlinghaus wrote:
> After having upgraded from 10.2.0.3 to 10.2.0.4 in our programs on
> different sites we have sporadic errors of the following type:
> ORA-12899: value too large for column
> (actual: 13, maximum: 7)
> In all cases the code for filling the fields is in Update triggers, the
> field lengths are correct. In this case in the update trigger there is
> the row
> :NEW.adcabrrzdatumstornierung := SYSDATE;
> and adcabrrzdatumstornierung is a date field.
> The error is rarely but be had it in different parts of the program. It
> has happened also to a char(14) field.
> Before upgrading we had not this type of error. Does anybody has a
> similar problem?
> Arne Ortlinghaus
> ACS Data Systems
What database product are you actually working with? I can't think, though I haven't had coffee yet, of any case in Oracle where one would refer to a field as <name>.<name>.<name>. Nor do I understand what actual: 13, maximum 7 indicates. Again this doesn't sound like Oracle.
If what you are saying is that occasionally your trigger is trying to stuff 13 bytes into a 7 byte bucket this issue is more likely something other than the patch you applied. Put in exception handling and write the offending values to a table so you can view them.
-- Daniel A. Morgan Oracle Ace Director & Instructor University of Washington damorgan_at_x.washington.edu (replace x with u to respond) Puget Sound Oracle Users Group www.psoug.orgReceived on Tue Oct 07 2008 - 08:38:50 CDT