Re: SQL*Loader: Field termination

Could you be a little more specific about the problems caused by the "." on the end of the timestamp field?
In the control file, are you using the parameter OPTIONALLY ENCLOSED BY in the control file? What is the data type of the timestamp field? It seems to me that if you used the switches FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"' (terminated by a comma, strings enclosed by double quotes) the problem- whatever it is- might go away.

In addition, you might want to (or maybe you have to) specify the field as a DATE field and supply a valid NLS_DATE_FORMAT mask. For example:

   timestamp DATE(19) "DD-MON-YYYY HH:MI:SS"

If you do not supply a field width, SQL*Ldr will take if from the supplied mask.

Let us know if this helps, or if there is still a problem.

Henry

"Russell Smith" <rsmith_at_serck-controls.co.uk> wrote in message news:f191bfd4.0201100342.c98246f_at_posting.google.com...
> Hi,
> I have been importing a bunch of csv's into oracle using the
> sql*loader, and are having some problems.
>
> basically the timestamp field when the csv was generated was set to be
> a fixed length field, and therefore sometimes i get a date like this;
>
> 24-MAY-1998 00:00:10.
>
> the . on the end is causing errors;
> i need to know how to do an OPTIONALLY TERMINATED BY (i have just made
> this up but this is what i need to do).
>
> Any ideas?
>
> Russ
>
> p.s. unfortunatly the csv's can't be done again properly.
Received on Sat Jan 12 2002 - 13:00:18 CET