Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!pd7cy2so!pd7cy1no!shaw.ca!pd7tw1no.POSTED!53ab2750!not-for-mail
X-Trace-PostClient-IP: 24.71.164.225
From: "Haximus" <666@444.1234>
Newsgroups: comp.databases.oracle.server
References: <Rw8Cb.664397$6C4.311032@pd7tw1no> <1071252079.66421@yasure>
Subject: Re: Perplexing ORA-01461
Lines: 65
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <3uoCb.675402$6C4.288381@pd7tw1no>
Date: Fri, 12 Dec 2003 19:16:15 GMT
NNTP-Posting-Host: 24.67.253.205
X-Complaints-To: abuse@shaw.ca
X-Trace: pd7tw1no 1071256575 24.67.253.205 (Fri, 12 Dec 2003 12:16:15 MST)
NNTP-Posting-Date: Fri, 12 Dec 2003 12:16:15 MST
Organization: Shaw Residential Internet
Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:250009

"Daniel Morgan" <damorgan@x.washington.edu> wrote in message
news:1071252079.66421@yasure...
> Haximus wrote:
>
> > I'm working on a Forms 9i application, the db used is Oracle9i
Enterprise
> > Edition 9.2.0.4.0 running on RedHat AS 3.0.  I keep getting an ORA-01461
> > error, which is defined as "can bind a LONG value only for insert into a
> > LONG column."  The perplexing part is none of the columns in the table
being
> > inserted are defined as LONG, nor are any of the variables I'm using.
I've
> > searched metalink and tried some of the suggested fixes but no joy.
>
> How about CLOB? BLOB? etc? What data types do you have?

This is the table definition itself:

--- snip ---
create global temporary table tree (
 id number not null primary key,
 parent_id number,
 rid rowid,
 seq number,
 selected char(1),
 type char(1),
 state number,
 label varchar(100),
 value number,
 block varchar(30),
 item varchar(30),
 branch varchar(100),
 options varchar(10),
 expr1 varchar(1000),
 expr2 varchar(1000),
 expr3 varchar(1000),
 check ( type in ('F','R') ),
 check ( state between -1 and 1 )
)
on commit preserve rows;
--- unsnip ---

The offending code looks something like this (edited for brevity);

--- snip ---
procedure insert_node(pnode tree%rowtype) is
    cnode tree%rowtype;
begin
    -- assign some values to pnode
    select seq.nextval into cnode.id;
    cnode.parent_id := pnode.id;
    cnode.type := 'F';
    cnode.selected := 'N';
    cnode.state := 0;
   ...
    insert into tree values (cnode); -- <<<< this is where the ORA-01461
occurs
    ...
end;
--- unsnip ---