Re: SQL*LOADER CSV file problem

From: BobH <b-horton_at_worldnet.att.net>
Date: Thu, 23 Apr 1998 21:54:25 -0400
Message-ID: <6hore6$188@bgtnsc03.worldnet.att.net>

It is seeing the fourth " as the end of the second field but finds no delimiter
before getting the next ". If looks like whatever is creating your file is accepting
the " as data. So you might change it there to export the file using another
Text delimiter (say "@").

Jason Selby wrote:
>
> Hi
>
> I've got a problem, the following record is not loaded into the table
> when using SQL*LOADER :
> "1813.","""Bumping"" of
> heart","","","","00","","00","","00","**********","0","EN"
>
> The control file is as follows
>
> LOAD DATA
> INFILE 'c:\readcode\corev2.1'
> INFILE 'c:\readcode\corev2.2'
> INFILE 'c:\readcode\corev2.3'
> INFILE 'c:\readcode\corev2.4'
> INFILE 'c:\readcode\corev2.5'
> INFILE 'c:\readcode\corev2.6'
> INFILE 'c:\readcode\corev2.7'
> INFILE 'c:\readcode\std9v2.rc'
> INSERT
> INTO TABLE read_cross_ref_new

   TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'   (READ_CODE ,
  TERM,

  TERM_60 ,
  TERM_198 ,
  ICD9_CODE ,
  ICD9_CODE_DEF ,
  ICD9_CM_CODE,
  ICD9_CM_CODE_DEF ,
  OPCS_CODE,
  OPCS_CODE_DEF ,

  SPECIALTY_FLAGS ,
  STATUS_FLAG,
  LANGUAGE_CODE )
>
> The problem seems to occur when the field TERM begins with 2 double
> quotes although this is allowed in the normal CSV file spec. Is there a
> workaround or should I convert it to tab delimited or something other
> than CSV.
>
> TIA
>
> Jason
Received on Thu Apr 23 1998 - 20:54:25 CDT