Re: ORA-12899: value too large for column with Oracle Patch 10.2.0.4

From: joel garry <joel-garry_at_home.com>
Date: Tue, 7 Oct 2008 10:30:40 -0700 (PDT)
Message-ID: <1a0db944-e01b-46c3-a496-2ca0fb06bc46@n33g2000pri.googlegroups.com>


On Oct 6, 6:34am, "Arne Ortlinghaus" <Arne.Ortlingh..._at_acs.it> 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
> "ISC"."AUFTRAEGEDURCHLAEUFECHECKS"."ADCABRRZDATUMSTORNIERUNG"
> (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

I'm guessing you are relying on implicit date conversions, and you see this because it is converting the internal date representation of 7 characters into an external representation of some kind (which I would expect to be 9 or 11 actual). Check your date environment variables, and make your date conversions explicit in the trigger.

It also could be the characterset issue, where your abracadabrastring is now defined differently.

"This is seen when exporting from a database with a 8 bit NLS_CHARACTERSET (like WE8ISO8859P1, WE8MSWIN1252, WE8DEC ) or 16-bit NLS_CHARACTERSET (like JA16SJIS, ZHS16GBK, KO16MSWIN949) to a database with a NLS_CHARACTERSET set to AL32UTF8 or UTF8." (from a peoplesoft blog found by googling)

jg

--
@home.com is bogus.
"Download complete.  You may now disconnect from the Internet."
Received on Tue Oct 07 2008 - 12:30:40 CDT

Original text of this message