Home -> Usenet -> c.d.o.tools -> Re: Limitations of SQL loader?

Re: Limitations of SQL loader?

From: Bjarne <bjp_at_ssb.no>
Date: Wed, 9 Dec 1998 11:34:43 +0100
Message-ID: <74lnb7$bfp$1_at_elle.eunet.no> 













You must explicitly specify a maximum length for the column 
after a CHAR keyword or with a POSITION keyword. This is necessary even if the 
data is delimited or enclosed.



    
Erik Ulven skrev i meldingen <366E49AD.17BF5CFC_at_quasar.no>...
Hello 
    experts out there. 
    
I try to load som ascii files generated by Ocelot databaseengine. 
One 
    of the fields are varchar2(4000) which is not possible in Oracle, so the 
    oracle equivalent is Long. the control file looks like this: 
    
LOAD DATA 
INFILE 
    FREETEXT.TXT 
APPEND 
INTO TABLE FREETEXT 
FIELDS 
    TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' 
(SAFE_NO       NULLIF 
    SAFE_NO="", 
 CODE          
    NULLIF CODE="", 
 LANGUAGE      NULLIF 
    LANGUAGE="", 
 TEXT          
    NULLIF TEXT="" ) 
    
This seems to work fine, but in the log it says: 
    
Record 1: Rejected - Error on table FREETEXT, column TEXT. 
    
Field in data file exceeded maximum specified length 
    
etc.... 
    
Here is one of the rows that doesn't get loaded... 
    
12018,"HA",47,"Brukt olje kan inneholde 
    metallpartikler og nedbrytingsprodukter av olje, som medfører 
    større helserisiko enn det opprinnelige produkt. Sprut eller 
    avdamping fra arbeidsstykket p.g.a. høy temperatur eller andre 
    forhold ved arbeidsprosessen, representerer den største 
    helsefare." 
    
This shouldn't be too much to insert into a Long field or what? 
    
Can anyone please tell me what i have done wrong, or what i haven't done? 
    
I'm supposed to fix this for a customer NOW.... 
    
Thanks for you help. 
    
Erik 
  

Received on Wed Dec 09 1998 - 11:34:43 CET












Original text of this message