Re: truly odd problem

[Quoted] In article <pJes3.3682$3X5.28573_at_insync>,   "Joet Singh" <jsingh_at_bigfoot.com> wrote:
> I had been trying to deploy a internal web site using oracle 8.1 and
> webdb2.0 and intermedia(context), for our client. One of the tables
> contains a Long datatype (CLOB). When I would test this table and
context
> from SQL*PLUS by trying to insert, update and query the long datatype
table
> I had no problems. When I would try to do same using webdb I ran
into
> several problems:
> 1) I could not insert more then 2000 characters in the long
datatype, if I
> try to insert over 2000 characters I would get:
>
> ORA-02005 implicit (-1) length not valid for this bind or define
datatype
> Cause: A negative length for the define variable was passed to a
define
> function.
> Action: An explicit, non-negative, length parameter must be passed.
>
> 2) When I would query the long datatype via webdb it will spit out
all rows
> within the table regardless of the words used(does not matter if
words are
> in the field or not) for query.
>
> Now the odd part, since I was not getting anyplace with solving this
problem
> I set up oracle 8.0 and webdb2.0 on my personal computer, as almost
all the
> books I have are on oracle 8.0. I was hoping I maybe be able to go
and
> atleast read up on this problem. Now, I have established the same
tables in
> oracle 8.0 and have started up context and can get the results I want
using
> SQL*PLUS when I query, insert, update. But I am still having
problems with
> webdb but I am *getting different errors*. 3)When I go to insert
data, I
> still can not insert more then 2000 characters in the long datatype
field,
> if I try to insert more then 2000 characters I get following error
now:
> ORA-06502: PL/SQL: numeric or value error
> ORA-06512: at "WEBDB.WWV_ARRAY_UTIL", line 134
> ORA-06512: at "JSINGH.INSERT_RESUME_FORM", line 234
> ORA-06512: at line 1
>
> 4) When I query this column via webdb, as before I am getting all
rows
> returned regardless of query words.
>
> Anybody have ideas what I should look at, the above errors
descriptions are
> not truly helpful when I went and looked them up? ANY and ALL help
is truly
> appreciated :-)
>
>

From your post it would appear that the problem is in WEBDB. Try talking to the product vendor. Does WEDDB support LOB's. You could try replacing your long field with a lob if it does and see if this gets you around the problem.

--
Mark D. Powell  -- The only advice that counts is the advice that
 you follow so follow your own advice --


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.