Re: ILLEGAL USE OF LONG DATATYPE?

I have to admit to being a little disappointed by discovering this limitation. Theoretically at least the database should have been able to accept that simple SQL statement without a problem. The DBA I was working with said that all developers run into this eventually and the usual reaction is (What the???!!!)

You know how I worked around it? I performed the query in MS Access...(with linked tables)

Jay

"Stefan" <sroesch3_at_attbi.com> wrote in message news:otw_7.2815$aq.31133_at_rwcrnsc51.ops.asp.att.net...
> Hi,
>
> first of all it is not desupported. But there are limitations and
> this was the reason to add clob/blob datatypes.
>
> Depending how big the lobs are you can use copy table from sqlplus,
> otherwise do the insert as select without the long column and use a
> small prgram to copy the long contents.
>
> Hope this helps
> Stefan
>
>
>
>
> Jay Valdez wrote:
>
> > INSERT INTO TRAININGPROGRAMS_TEST SELECT * FROM TRAININGPROGRAMS
> >
> > Error-->ILLEGAL USE OF LONG DATATYPE.
> >
> > Oracle 8.1.7
> >
> > Hello, I was wondering why this would occur in this situation.
> >
> > This is the DDL
> >
> > CREATE TABLE TRAININGPROGRAMS (
> > TYPEID NUMBER NOT NULL,
> > PROGRAMNAME VARCHAR2 (255),
> > DESCRIPTION LONG,
> > TIMEINDEX DATE DEFAULT SYSDATE,
> > PRIMARY KEY ( TYPEID ) ) ;
> >
> > CREATE TABLE TRAININGPROGRAMS_TEST (
> > TYPEID NUMBER NOT NULL,
> > PROGRAMNAME VARCHAR2 (255),
> > DESCRIPTION LONG,
> > TIMEINDEX DATE DEFAULT SYSDATE,
> > PRIMARY KEY ( TYPEID ) ) ;
>
Received on Tue Jan 08 2002 - 01:28:20 CST