tdload a table with auto increment primary key

Tools
N/A

tdload a table with auto increment primary key

Hi, I'm trying load a txt file into a table with auto increment primary key. Don't know why even though i defined my 2nd column as varchar (18), tdload thinks max length for it is 11. Can anybody please help? Thanks!

CREATE TABLE sandbox.coffee_ga (c_id INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 1 INCREMENT BY 1 MINVALUE 0 MAXVALUE 100000000 NO CYCLE), press_date INT, account_id VARCHAR(18)) unique primary index (c_id);



$ /opt/teradata/client/13.10/tbuild/bin/tdload -h tdwa --TargetWorkingDatabase sandbox -t coffee_ga -f coffee_ga.txt -u yizi -d ',' yizi_coffee_ga

Teradata Load Utility Version 13.10.00.04

Teradata Parallel Transporter Version 13.10.00.04

Job log: /opt/teradata/client/13.10/tbuild/logs/yizi_coffee_ga-3379.out

Job id is yizi_coffee_ga-3379, running on pit-adhoc1

Teradata Parallel Transporter DataConnector Version 13.10.00.04

$FILE_READER Instance 1 directing private log report to 'FileReaderLog-1'.

Teradata Parallel Transporter Load Operator Version 13.10.00.03

$LOAD: private log specified: LoadLog

$FILE_READER: TPT19008 DataConnector Producer operator Instances: 1

$FILE_READER: TPT19003 ECI operator ID: $FILE_READER-8754

$FILE_READER: TPT19222 Operator instance 1 processing file '/home/yizi/coffee_ga.txt'.

$LOAD: connecting sessions

$LOAD: preparing target table

$LOAD: entering Acquisition Phase

$FILE_READER: TPT19104 VARCHAR field length error in column 2 .  Received 15 (max 11) on record 1.

$FILE_READER: TPT19350 I/O error on file '/home/yizi/coffee_ga.txt'.

$LOAD: disconnecting sessions

$FILE_READER: TPT19221 Total files processed: 0.

$LOAD: Total processor time used = '0.16 Second(s)'

$LOAD: Start : Tue Jan 29 20:24:23 2013

$LOAD: End   : Tue Jan 29 20:24:43 2013

Job step MAIN_STEP terminated (status 8)

Job yizi_coffee_ga terminated (status 8)

Tags (1)
1 REPLY
Teradata Employee

Re: tdload a table with auto increment primary key

Please re-run the job with the command line option:

    --SourceTraceLevel 'Y'

and then send the log to steven.feinholz@teradata.com.

The log will be in the "logs" directory under where TPT is installed, and the file name will be <job-id>.out.

The job-id will be on the console when you run the job.

We cannot reproduce the problem inhouse and thus need to see the trace.

The .out file is a binary file, so if you are FTP-ing it, make sure to do so properly.

-- SteveF