Has anyone experienced issues with using Easyloader to transfer data between servers?
When attempting to copy data from one server to another (on the same version of Teradata) to Arctic a column with data type Decimal(38,20) through up an error relating to field length. Below is a log of the commands / responses: -
$ export LANG
$ export PATH=$PATH:/opt/teradata/client/14.00/tbuild/bin:
$ tdload --TargetTable CUSTOMER_SUMMARY_HS_INTL \
> --TargetWorkingDatabase U_D_BCBMI_H02333511DB \
> --TargetUserName H02333511 \
> --TargetTdpId dwsoat \
> --TargetUserPassword xxxxxxxxx \
> --SourceUserName H02333511 \
> --SourceTdpId dwsana \
> --SourceUserPassword xxxxxxxxx \
> --SourceWorkingDatabase UD_BCBMI_METRICSDB \
> --SourceTable CUST_SUM_HS_INTL
Teradata Load Utility Version 14.00.00.10
Teradata Parallel Transporter Version 14.00.00.10
Job log: /opt/teradata/client/14.00/tbuild/logs/bwatjf7-276
Job id is bwatjf7-2769, running on atv00135
Teradata Parallel Transporter Export Operator Version 14.00.00.10
$EXPORT: private log specified: ExportLog
Teradata Parallel Transporter Load Operator Version 14.00.00.10
$LOAD: private log specified: LoadLog
$LOAD: connecting sessions
$EXPORT: connecting sessions
TPT_INFRA: TPT02638: Error: Conflicting data length for column(41) - CUSTOMER_LGD_DT. Source column's data length (16) Target column
's data length (8).
$EXPORT: TPT12108: Output Schema does not match data from SELECT statement
$EXPORT: disconnecting sessions
$EXPORT: Total processor time used = '0.066628 Second(s)'
$EXPORT: Start : Thu May 22 11:45:02 2014
$EXPORT: End : Thu May 22 11:45:03 2014
$LOAD: preparing target table
$LOAD: entering Acquisition Phase
$LOAD: disconnecting sessions
$LOAD: Total processor time used = '1.00399 Second(s)'
$LOAD: Start : Thu May 22 11:45:02 2014
$LOAD: End : Thu May 22 11:45:20 2014
Job step MAIN_STEP terminated (status 12)
Job bwatjf7 terminated (status 12)
It looks like a data issue.
You can check the source and target data and data type, comparing source and target.
The error Conflicting data length for column(41) - CUSTOMER_LGD_DT. Source column's data length (16) Target column 's data length (8).
Thanks for the post. I have checked the source / target tables and they are identical, i.e. DECIMAL(38,20). I have also been able to complete the data copy using Teradata Parallel Transporter Wizard - Any ideas?
Strange!!!! Maybe you ran easy loader in unix environment and session settings could be different. Whereas you ran TPT wizard you choose Character set etc as something else, that is right? It is just my thought.
Is it a bug? I also encounter this problem. i use tbuild to run a TPT script to copy data from one server to another:
Source and target table are identical:
CREATE MULTISET TABLE TST_DEC
DEC_2 DECIMAL(2,1) NOT NULL DEFAULT 0.0 ,
DEC_4 DECIMAL(4,0) NOT NULL DEFAULT 0. ,
DEC_9 DECIMAL(9,0) NOT NULL DEFAULT 0. ,
DEC_18 DECIMAL(18,0) NOT NULL DEFAULT 0. ,
DEC_38 DECIMAL(38,0) NOT NULL DEFAULT 0.
PRIMARY INDEX ( DEC_2 );
DEFINE SCHEMA Table_Schema
TPT_INFRA: TPT02638: Error: Conflicting data length for column(5) - DEC_38. Source column's data length (16) Target column's data length (8).
I have tried: USING CHARACTER SET UTF8, USING CHARACTER SET UTF16,USING CHARACTER SET ASCII for the TPT script, all the error are same as above.
Anyone has idea?
I am not pretty sure. My guess is the length behaviour of tpt. Did you try increasing the length in schema, maybe 3 times. I m not sure.
I remember vaguely about this discussion. It maybe wrong.