| Raymond Mardle 2005-12-05, 11:24 am |
| I traced the problem to using hex values for the tab column
delimiter and the new line row delimiter. Changing them to
the actual characters TAB and new line (by having '
') I stopped getting the error. However, using individual
column delimeters gave a different error about the file with
an error like "(512) exceeding the ASA maximum (44) for file
size". Removing the individual delimeters and using
"delimited by '<TAB>'" solved that problem.
When I tried to use '\x0d\x0a' I got an error saying that
the delimeter had to be 1-4 characters. I must be missing
something obvious about using hex values or escaped
characters but I can't for the life of me think what it is.
Any ideas?
> I am using 64 bit IQ 12.6 ESD 4.1 on Solaris. I cannot get
> "load table" to work (oh the embaressment). I have ended
> up creating a single column table as follows
>
> create table t2 (a int)
> create lf index t2_a_lf on t2 (a)
>
> After trying to load one row into the table using the
> following
>
> load table t2 (
> a '\n'
> )
> from '/dsk/1/defrag/t2.txt'
> quotes off
> escapes off
> with checkpoint on
>
> the log file contains this
>
> I. 12/02 14:52:03. In table 't2', the full width insert of
> 1 columns will begin at record 1.
> I. 12/02 14:52:03. Portions of the insert/load will be
> single threaded.
> I. 12/02 14:52:03. Warning: Partial input record (2 bytes)
> skipped at EOF (O/S 0). 0 rows read.
> I. 12/02 14:52:03. Insert Pass 1 completed in 0 seconds.
> I. 12/02 14:52:03. Insert Pass 2 completed in 0 seconds.
> I. 12/02 14:52:03.
> I. 12/02 14:52:03. 0 records were inserted into 't2'.
> I. 12/02 14:52:03. Insert for 't2' completed in 0 seconds.
> 0 rows inserted.
>
> The file contains a single line with 1 on it. This is the
> dump of the data file
>
> $ od -c t2.txt
> 0000000 1 \n
> 0000002
>
> I can't work out what I'm doing wrong. I'm sure I never
> had these problems on Windows.
>
> This started becuase I have to load a 77 million row
> table into IQ. The table is BCPd out of ASE. It has date
> columns that are formatted like this "Jun 19 2004
> 10:47:34:916PM". I can't see how to persuade "load table"
> to recognise that format. Is it possible?
>
> Cheers
>
> Raymond
|