Re: ORA-01406 fetched column value was truncated

From: joel garry <joel-garry_at_home.com>
Date: Mon, 20 Apr 2009 15:30:10 -0700 (PDT)
Message-ID: <0f5a76a3-826d-4554-9b14-e48ab97d63b2_at_z8g2000prd.googlegroups.com>



On Apr 19, 11:42 pm, jodleren <sonn..._at_hot.ee> wrote:
> Just to clear up things and fir someone in the future:
>
> The problem was that I was reading from views, where in one there
> was:  field_a/field_b and sometimes field_b would be 0, causing a
> Division by 0 error.
>
> That resulted in this errors.
>
> WBR
> Sonnich
>
> On Apr 15, 5:53 pm, jodleren <sonn..._at_hot.ee> wrote:
>
>
>
> > Hello
>
> > When reading a double from a table, I get this error:
> > ORA-01406 fetched column value was truncated
>
> > The desciption is:
>
> > ORA-01406 fetched column value was truncated
> >     Cause: In a host language program, a FETCH operation was forced to
> > truncate a character string. The program buffer area for this column
> > was not large enough to contain the entire string. The cursor return
> > code from the fetch was +3.
> >     Action: Increase the column buffer area to hold the largest column
> > value or perform other appropriate processing.
>
> > The problem is that it is a working database in 3+ copies, so I cannot
> > really go an change things. And I cannot even see where it is wrong,
> > except that it is a numver of places.
>
> > The error occures when
> > select workingtime (double, size 15) from sdfgsdfgf where department =
> > 'CNCMILL'
>
> > When selecting other departments, the error might be there, it might
> > not. The error might also come when scrolling data.
>
> > I would apriciate to fix my SQL, not the database.... as I have no
> > idea what might happen elsewhere if I do so...
>
> > WBRSonnich

Sounds like you need a database constraint to disallow those zeros.

jg

--
_at_home.com is bogus.
xkcd in nyt: http://www.nytimes.com/2009/04/20/business/media/20link.html
Received on Mon Apr 20 2009 - 17:30:10 CDT

Original text of this message