Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Ora-6502: character string buffer too small

Re: Ora-6502: character string buffer too small

From: andrew_webby at hotmail <spam_at_no.thanks.com>
Date: Mon, 26 Mar 2001 11:50:38 +0100
Message-ID: <985603894.15646.0.nnrp-07.c30bdde2@news.demon.co.uk>

Use NVL function where you need to handle NULLs.

It's not a bug by the sounds of it.

<raas.no_spam_at_interware.hu> wrote in message news:99mmb2$9ec$1_at_proxy.interware.hu...
> Martin Haltmayer <Martin.Haltmayer_at_0800-einwahl.de> wrote:
> > What is the structure of table z?
>
> hi,
>
> since then, after 3 hours, I was able to recognize that the function
> wanted VARCHAR input but the table column was of CHAR type. Modifying
> the function appropriately, it seemed to work.
>
> I replaced the 'BEGIN; return(1); END;' with the 'real' function body.
> But, if inside the function
>
> (that is, now:
>
> FUNCTION x (nnn in number, sss in char) RETURN NUMBER IS
>
> )
>
> I did
>
> IF sss LIKE 'some.thing%'
>
> then execution had failed again with the same error, on the first row
> that actually contained data.
>
> Workaround was to assing the value of sss to a VARCHAR type variable,
> then I was able to use LIKE.
>
> Think I found a bug or something? Or is it me?
>
> [actually, the original error DIDN'T show up for just any data in table
> z. The function worked well for months. Now it seems that it fails on
> tables that contain NULLs in theis VARCHAR columns, and it fails on the
> first row that is NOT NULL. Right now, I'm happy to live with the
> working function and tables but I will try to reproduce the error under
> laboratory conditions if some of you guys say it's a bug and not me :]
>
> regards
> r.
Received on Mon Mar 26 2001 - 04:50:38 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US