This article will show you how to use Teradata PT to copy data from one or more non-Teradata table(s) (e.g. Oracle table) to a Teradata table without using any intermediate disk storage. Teradata PT uses an ODBC operator as a producer to extract data from an Oracle table (as an example) and a Load operator as a consumer to load data into a Teradata table. You can modify the script to use other consumer operators such as Update, Stream or Inserter operator.

The best way to learn is by example. Let’s look at the following simple script, which is to copy data from an Oracle employee table to a Teradata table.

DEFINE JOB your_job_name
DESCRIPTION 'your comments'
(
            DEFINE SCHEMA Oracle_DataSource_Schema
            DESCRIPTION 'Schema of Oracle Data Source'
            (
                        EmpNo             DECIMAL (4,0),
                        EmpName         VARCHAR (10),
                        JobTitle             VARCHAR (9),
                        Mgr                   DECIMAL (4,0),
                        HireDate           VARCHAR (10),
                        Salary               DECIMAL (7,2),
                        Comm              DECIMAL (7,2),
                        DeptNo             DECIMAL (2,0)
            );
 
            DEFINE OPERATOR ODBC_Operator
DESCRIPTION 'TPT ODBC Operator'
TYPE ODBC
SCHEMA Oracle_DataSource_Schema
            ATTRIBUTES
            (
                        VARCHAR  PrivateLogName   = @ODBCPrivateLogName,
                        VARCHAR  DSNName             = @DSNName,
                        VARCHAR  UserName             = @ODBCUserName,
                        VARCHAR  UserPassword       = @ODBCPassword,
                        VARCHAR  SelectStmt             = @SelectStmt
            );
 
            APPLY
                ( 'INSERT INTO ' || @TargetTable || ' (
                                 :EmpNo, :EmpName, :JobTitle, :Mgr, :HireDate, :Salary, :Comm, :DeptNo);'
                 )
           TO OPERATOR (  $LOAD [@LoadInstances] )
 
       SELECT * FROM OPERATOR (  ODBC_Operator [@ODBCInstances]  );
        );              
);

The script has the following statements:

  • DEFINE JOB defines a Teradata PT job with a single APPLY statement not enclosed in the job STEP syntax.
  • DEFINE OPERATOR defines Teradata PT operators that will be used in a Teradata PT job.  In the example, the script uses the ODBC operator and Load operator.
  • DEFINE SCHEMA describes the structure of the data source or data target with an ordered set of column definitions.  In the example, it’s a table schema of an Oracle employee table.
  • APPLY statement defines the operations to be executed by a job.  In the example is to load data into an empty Teradata table.

If you wish to know more details on these statements, please refer to the Teradata Parallel Transporter Reference.  Only necessary information will be mentioned here to keep the article simple.

As you notice that there is only one DEFINE OPERATOR statement for the ODBC operator in the script example.  Where is the other DEFINE OPERATOR statement for the Load operator, you may ask.  Well, the definition of the Load operator is automatically imported into the job script by using a template name $LOAD in the APPLY statement.  The key word $LOAD is the template name of the standard Teradata PT-supplied Load operator.  The DEFINE OPERATOR statement for the Load operator is stored in the template file $LOAD.txt under the Teradata PT template directory ($TWB_ROOT/template).  This is an improvement in the Teradata PT 13.10 or later versions to simplify the Teradata PT script syntax.

You can find more information on the operator templates by referencing Chapter 13 in the Teradata Parallel Transporter User Guide.

Now, it’s time to examine the DEFINE SCHEMA statement in the script.  Assuming that an Oracle employee table has 8 columns defined as follows:

EmpNo             NUMBER (4,0),
EName             VARCHAR (10),
Job               VARCHAR (9),
Mgr               NUMBER (4.0),
HireDate          DATE,
Sal               NUMBER (7,2),
Comm              NUMBER (7,2),
DeptNo            NUMBER (2,0)

Since Teradata Database 13.10 and older versions do not support NUMBER data type, the Oracle NUMBER data type will be mapped to the equivalent Teradata DECIMAL data type as shown in the DEFINE SCHEMA statement.  Another thing you need to pay attention to is the Oracle DATE data type, which is very different from Teradata DATE data type.  You need to do some data conversion on Oracle DATE column to fit the Teradata DATE column. In the script example, the function TO_CHAR is used in the SELECT statement to convert the Oracle DATE values to Teradata date format.

Next is to mention the use of job variables in the script.  They are composed of the symbol @, followed by a unique identifier.  The value of these job variables can be specified in a file following the format:

job-variable-name = value [,]

The following job variables must be defined in the job variable file:

/**********************************/
/* Values for ODBC operator */
/**********************************/
ODBCInstances            = 1,
ODBCPrivateLogName       = 'odbclog',
DSNName                  = 'Oracle_DSNName',
ODBCUserName             = 'scott',
ODBCPassword             = 'tiger',
SelectStmt               = 'select EmpNo, EName, Job, Mgr,
                              TO_CHAR (HireDate, ''YYYY/MM/DD'') AS HireDate,
                              Sal, Comm, DeptNo from emp;'
/**********************************/
/* Values for LOAD operator */
/*********************************/
LoadInstances            = 1,
LoadPrivateLogName       = 'loadlog',
TargetTable              = 'Teradata_target_table_name',  
TargetTdpId              = 'Teradata_TdpId',
TargetUserName           = 'Teradata_User_Name',
TargetUserPassword       = 'Teradata_User_Password',
LogTable                 = 'Teradata_Log_Table_Name'

If the Teradata target table resides in a different database than the default database of the specified Teradata user, you must add the job variable TargetWorkingDatabase to the file, as follows:

TargetWorkingDatabase   = ‘targetWorkingDatabase’

Finally, at the command line, you can run the script as follows:

       tbuild -f script_file -v job_variable_file

Important notes:

  1. The Teradata target table must be defined before running the Teradata PT script.  For this exercise, the target table can be defined as follows:
    CREATE TABLE orcl_emp_tbl (
      EmpNo           integer,
      EmpName         varchar(10),
      JobTitle        varchar(9),
      Mgr             integer,       
      HireDate        date,
      Salary          decimal(7,2),
      Comm            decimal(7,2),   
      DeptNo          smallint
    );
  2. If you use TO_CHAR in the SELECT statement, the TPT script schema must have the VARCHAR data type for the column, as shown in the example.
  3. The date conversion format used in TO_CHAR must match with that of a Teradata DATE column. Otherwise, the load job will fail and all rows will be thrown in an error table (error 2665) due to invalid date values.
Discussion
cpkumarit 1 comment Joined 01/12
23 Jan 2012

Useful Article...Thanks.

arun9372 1 comment Joined 03/12
21 Mar 2012

Hi,
Can you please explain where to write this query?
Also can we do this using UNIX scripts?
Thanks in Advance..
Regards,
Arun

mvu 11 comments Joined 12/09
21 Mar 2012

Arun,
I assume that you're talking about Select query for the ODBC operator.
You can specify the query via the job variable 'SelectStmt' in the job variable file as mentioned in the article. You can use UNIX script to create the job variable file and
invoke the tbuild command with the job variable file.

vetriselvan 14 comments Joined 04/14
30 Apr 2014

Hi,
Thanks for the useful article. I am trying to load the data from Oracle to Teradata using TPT but getting this below ODBC error. Can you please help me to resolve this issue?
 
Teradata Parallel Transporter Version 14.00.00.08
Job log: /apps/teradata/client/14.00/tbuild/logs/<job id>.out
Job id is <job id>, running on <servername>
Found CheckPoint file: /apps/teradata/client/14.00/tbuild/checkpoint
This is a restart job; it restarts at step MAIN_STEP.
TPT_INFRA: TPT02192: Error: Cannot load shared library
           dlopen error: ld.so.1: executor: fatal: /apps/teradata/client/14.00/odbc_64/lib/libodbc.so: wrong ELF class: ELFCLASS64
TPT_INFRA: TPT02109: Cannot open shared library libodbcop.so, status = Open Error
TPT_INFRA: TPT02240: Error: Cannot create operator object, status = Operator Error
TPT_INFRA: TPT02103: Executor unable to set up its table object
Job step MAIN_STEP terminated (status 8)
 
 

mvu 11 comments Joined 12/09
30 Apr 2014

The TPT version 14.0 is 32-bit application and the TPT job picks up the 64-bit version of the library "libodbc.so" during the run.  You need to include the proper path to your 32-bit "libodbc.so" in the LD_LIBRARY_PATH or LIBPATH depending on your UNIX machine.  If you haven't done it, you also  need to set up the environment variable ODBCINI to point to the correct "odbc.ini" before running a TPT job.

vetriselvan 14 comments Joined 04/14
02 May 2014

Thanks for your quick response. Now I am getting this below error:
 

Teradata Parallel Transporter Version 14.00.00.08
Job log: /apps/teradata/client/14.00/tbuild/logs/infbiftp-107.out
Job id is <user_name>-107, running on <server_name>
Found CheckPoint file: /apps/teradata/client/14.00/tbuild/checkpoint/<user_name>LVCP
This is a restart job; it restarts at step MAIN_STEP.
Teradata Parallel Transporter Load Operator Version 14.00.00.08
LOAD_OPERATOR: private log specified: loadoper_privatelog
LOAD_OPERATOR: connecting sessions
TPT_INFRA: TPT01036: Error: Task (TaskID: 5, Task Name: SELECT_2[0001]) terminated due to the receipt of signal number 11
TPT_INFRA: TPT01037: Error: Task (TaskID: 5, Task Name: SELECT_2[0001]) core dumped
LOAD_OPERATOR: preparing target table
LOAD_OPERATOR: entering Acquisition Phase
LOAD_OPERATOR: disconnecting sessions
LOAD_OPERATOR: Total processor time used = '19.25 Second(s)'
LOAD_OPERATOR: Start : Fri May  2 13:07:24 2014
LOAD_OPERATOR: End   : Fri May  2 13:07:48 2014
Job step MAIN_STEP terminated (status 8)
Job <user_name> terminated (status 8)
 

mvu 11 comments Joined 12/09
02 May 2014

Do you happen to have the trace from the core file?   I also need the binary log file '/apps/teradata/client/14.00/tbuild/logs/infbiftp-107.out' to see what happens during the run.
We have seen this coredump before but not sure if it's the same one that we fixed in the latest version of 14.00.
 

vetriselvan 14 comments Joined 04/14
05 May 2014

Yes trace file is generated. But its not in readable format. Please let me know the details you required in this file I can share it with you.

mvu 11 comments Joined 12/09
06 May 2014

To extract the binary log in the readable format, submit the following command at the command line prompt:
    tlogivew -l infbiftp-107.out -f "*" -g -o <outputfilename>
The command will extracts all logs; but I only interests in the section belongs to the ODBC operator.  You can find it in the "outputfilename" starting with the banner "ODBC OPerator  Version ....".
However,based on the poseted console log,  I realized that the ODBC operator was not even started yet.   Maybe the follwoing command might get some useful information:
     tlogview -l infbiftp-107.out -w 'TASKNAME="SELECT_2[0001]"' > output.txt
And, give the last 50 lines of he output file.
My guess is that you might not set the environment correctly for ODBC driver to be loaded properly.   Do you have the system coredump file?  The information in the coredump file will verify  that.  We can get segmentation fault while the ODBC driver is  loaded and its dependent libraries are not in sync.  We, as TPT, has no control over that.
Is the environment ODBCINI set up correctly?

vetriselvan 14 comments Joined 04/14
08 May 2014

Yes I think issue with ODBC connection. Can you please give the format of Connection string which we can use in variable file? I will try with this option instead of DSN Name. Pls see the bingary log below :

Using memory mapped file for IPC

TPT_INFRA: TPT04101: Warning: TMSM failed to initialize
Teradata Parallel Transporter Coordinator Version 14.00.00.08
Teradata Parallel Transporter Executor Version 14.00.00.08
Teradata Parallel Transporter Executor Version 14.00.00.08
Teradata Parallel Transporter Load Operator Version 14.00.00.08
LOAD_OPERATOR: private log specified: loadoper_privatelog
LOAD_OPERATOR: connecting sessions
TPT_INFRA: TPT01036: Error: Task (TaskID: 5, Task Name: SELECT_2[0001]) terminated due to the receipt of signal number 11

TPT_INFRA: TPT01037: Error: Task (TaskID: 5, Task Name: SELECT_2[0001]) core dumped

LOAD_OPERATOR: preparing target table
LOAD_OPERATOR: entering Acquisition Phase
Job is running in Buffer Mode
TPT_INFRA: TPT02255: Message Buffers Sent/Received = 0, Total Rows Received = 0, Total Rows Sent = 0
LOAD_OPERATOR: disconnecting sessions
LOAD_OPERATOR: Total processor time used = '19.48 Second(s)'
LOAD_OPERATOR: Start : Thu May 8 11:21:01 2014
LOAD_OPERATOR: End : Thu May 8 11:21:27 2014
Job step MAIN_STEP terminated (status 8)
Job infbiftp terminated (status 8)
Total available memory: 10002340
Largest allocable area: 10002340
Memory use high water mark: 43004
Free map size: 1024
Free map use high water mark: 16
Free list use high water mark: 0

Private log PXCRM:

CheckPoint Resource Manager initialized.
Checking whether a valid CheckPoint exists for restart.

Private log TWB_SRCTGT:

MAIN_STEP APPLY_1[0001] LOAD_OPERATOR DBS TDPID_NAME database.tablename

Private log TWB_STATUS:

MAIN_STEP APPLY_1[0001] Success LOAD_OPERATOR 1 1 INITIATE-Started 11:21:01 0.0000 0.0000 65000 0 0 0 0 0 N Y
MAIN_STEP APPLY_1[0001] Success LOAD_OPERATOR 1 1 INITIATE-Ended 11:21:25 24.0000 19.4800 65000 0 0 0 0 0 N Y
MAIN_STEP APPLY_1[0001] Success LOAD_OPERATOR 1 1 TERMINATE-Started 11:21:25 0.0000 0.0000 65000 0 0 0 0 0 N Y
MAIN_STEP APPLY_1[0001] Success LOAD_OPERATOR 1 1 TERMINATE-Ended 11:21:27 2.0000 0.0200 65000 0 0 0 0 0 N Y

Private log TWB_EVENTS:

infbiftp-132,17,0,OperatorEnter,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,,1,0
infbiftp-132,116,5,UtilityName,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,TPT Load Operator,1,0
infbiftp-132,0,5,LoadVersionId,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,14.00.00.08,1,0
infbiftp-132,115,1,UtilityId,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,1,1,0
infbiftp-132,132,5,LoadTdpId,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,TDPID_NAME,1,0
infbiftp-132,1,5,LoadUserName,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,TERADATA_USER_NAME,1,0
infbiftp-132,128,5,LoadDbase,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,TERADATA_DB_NAME,1,0
infbiftp-132,21,1,LoadTableId,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,1,1,1
infbiftp-132,22,5,LoadTableName,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,database.tablename,1,1
infbiftp-132,19,0,LoadPhase1Begin,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,,1,1
infbiftp-132,135,0,LoadSessEnd,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,,1,0
infbiftp-132,18,1,OperatorExit,MAIN_STEP,LOAD_OPERATOR,1,2014-05-08,0,1,0

Private log loadoper_privatelog:

===================================================================
= =
= TERADATA PARALLEL TRANSPORTER =
= =
= LOAD OPERATOR VERSION 14.00.00.08 =
= =
= OPERATOR SUPPORT LIBRARY VERSION 14.00.00.08 =
= =
= COPYRIGHT 2001-2012, TERADATA CORPORATION. ALL RIGHTS RESERVED. =
= =
===================================================================

**** 11:21:01 Processing starting at: Thu May 8 11:21:01 2014

===================================================================
= =
= Module Identification =
= =
===================================================================

Load Operator for SunOS release 5.10 on HOST-NAME-XX.com
LoadMain : 14.00.00.10
LoadCLI : 14.00.00.07
LoadUtil : 14.00.00.02
PcomCLI : 14.00.00.24
PcomMBCS : 14.00.00.01
PcomMsgs : 14.00.00.04
PcomNtfy : 14.00.00.01
PcomPx : 14.00.00.11
PcomUtil : 14.00.00.09
PXICU : 14.00.00.08
TDICU : 14.00.00.02
CLIv2 : 14.00.00.04

===================================================================
= =
= Attribute Definitions =
= =
===================================================================

**** 11:21:02 Options in effect for this job:
OperatorType: Consumer
Instances: 1
Character set: Not specified; will use default
Checkpoint: No checkpoint in effect
Notify: Not enabled
Buffer size: Maximum allowable
Error limit: No limit in effect
Tenacity: 4 hour limit to successfully connect
Sleep: 6 minute(s) between connect retries
Pause Acq: Not in effect

===================================================================
= =
= Column/Field Definition =
= =
===================================================================

Column Name Offset Length Type
============================== ====== ====== ========================
COL_1 0 8 DECIMAL(15,0)
COL_2 8 30 VARCHAR
============================== ====== ====== ========================
INDICATOR BYTES NEEDED: 1
EXPECTED RECORD LENGTH: 41

===================================================================
= =
= Control Session Connection =
= =
===================================================================

**** 11:21:02 Connecting to RDBMS: 'TDPID_NAME'
**** 11:21:02 Connecting with UserId: 'TERADATA_USER_NAME'

===================================================================
= =
= Teradata Database Information =
= =
===================================================================

**** 11:21:04 Teradata Database Version: '14.00.04.10 '
**** 11:21:04 Teradata Database Release: '14.00.04.10 '
**** 11:21:04 Maximum request size supported: 1MB
**** 11:21:04 Session character set: 'ASCII'
**** 11:21:04 Total AMPs available: 60
**** 11:21:04 Data Encryption: supported
**** 11:21:04 Restart log table 'database.LOADOPER_LOGTABLE' exists from previous job
**** 11:21:04 This job is restarting

===================================================================
= =
= Special Session Connection =
= =
===================================================================

**** 11:21:25 Number of sessions adjusted due to TASM: 23

Instance Assigned Connected Result
======== ======== ========= ======================
1 23 23 Successful
======== ======== ========= ======================
Total 23 23 Successful

===================================================================
= =
= Target/Error Table Information =
= =
===================================================================

**** 11:21:25 This job will use the following tables:

Target Table: 'database.tablename'
Error Table 1: 'database.LOADOPER_ERRTABLE1'
Error Table 2: 'database.LOADOPER_ERRTABLE2'

**** 11:21:25 Number of rows sent, last job: 0
**** 11:21:25 Number of bytes sent, last job: 0

===================================================================
= =
= Acquisition Phase =
= =
===================================================================

**** 11:21:25 DML statement for DML Group: 1

INSERT INTO database.tablename ( :COL_1, :COL_2 );

**** 11:21:25 Number of records per buffer for this job: 1567

===================================================================
= =
= Logoff/Disconnect =
= =
===================================================================

**** 11:21:25 Logging off all sessions

Instance Cpu Time
======== ================
1 19.48 Seconds

**** 11:21:27 Total processor time used = '19.48 Second(s)'
. Start : Thu May 8 11:21:01 2014
. End : Thu May 8 11:21:27 2014
. Highest return code encountered = '0'.
**** 11:21:27 This job terminated

Hope this helps to figure out the issue.

vetriselvan 14 comments Joined 04/14
15 May 2014

Can you please help me to fix the issue?

mvu 11 comments Joined 12/09
15 May 2014

I assumed you're talking about the attribute "ConnectString".  You can refer to the Teradata PT manual for description.   Basically,  it is optional attribute that specifies an alternative method for connecting to the data source.  When it is used, the operator will ignore the values set in the following 3 attributes:  "DSNName", "UserName" and "UserPassword".
This string can contain any valid connect and/or driver information that is acceptable to the ODBC driver that you use.   The string specified in the attribute "ConnectString" will override the default setting in the ODBC initialization file.
We certify the product with Data Direct ODBC driver.  What is the ODBC driver that you are using? 
What is the OS of the machine you use? 
How do you define the DSN in the file "odbc.ini"?
Can I see you how you set up value for the attributes "DSNName", "UserName", "UserPassword" and "ConnectString" in the script or job variable file?
Can you give us the snap shot of all the environment variables prior to the run?
 

vetriselvan 14 comments Joined 04/14
16 May 2014

Yes correct. I mentioned about "ConnectString". I am using DataDirect odbc driver and Solaris.

TPT script
-----------

DEFINE OPERATOR EXPORT_OPERATOR
DESCRIPTION 'TPT ODBC Operator'
TYPE ODBC
SCHEMA TABLE_STRUCTURE
ATTRIBUTES
(
VARCHAR TraceLevel='ALL',
VARCHAR PrivateLogName = @ODBCPrivateLogName,
VARCHAR DSNname = @DSNname,
VARCHAR UserName = @ODBCUserName,
VARCHAR UserPassword = @ODBCPassword,
VARCHAR SelectStmt = @SelectStmt
);

Variable file:
--------------

/**********************************/
/* Values for ODBC operator */
/*********************************/
ODBCInstances = 1,
ODBCPrivateLogName = 'abc.txt',
DSNname = 'dsnname',
ConnectString ='ConnectString'
ODBCUserName = 'username',
ODBCPassword = 'password',
SelectStmt = 'select * from abc;'

Is there anyway to give all the log on information (for Oracle) in the variable file itself instead of referring to ODBC file? If yes please provide sample variable file.

Thanks !!!

mvu 11 comments Joined 12/09
16 May 2014

Based on what you gave, it looks like the ODBC operator will use 'dsnname', 'username' and 'userpassword' to connect an Oracle session.
Have you defined the 'dsnname' in the file odbc.ini, located under the directory where the Data Direct driver is installed?  You must define the 'dsnname' before you can use it in a TPT script.
Before you run TPT script, you must set and export the following environment variables: ODBCINI and LD_LIBRARY_PATH.
For example, if you install the Data Direct ODBC driver under the directory /home/DataDirect, then the environment variables will be set as follows:
        ODBCINI=/home/DataDirect/odbc.ini
        LD_LIBRARY_PATH=/home/DataDirect/lib:$LD_LIBRARY_PATH
 

vetriselvan 14 comments Joined 04/14
28 May 2014

I have defined the DSN name in the odbc.ini file and also assigned the environment variables ODBCINI and LD_LIBRARY_PATH.  I am using DataDirect 7.0 Oracle Wire Protocol driver and my OS is "SunOS 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5220". Now, When I execute the script am getting the below error:-

 

Teradata Parallel Transporter Load Operator Version 14.00.00.08

LOAD_OPERATOR: private log specified: loadoper_privatelog

LOAD_OPERATOR: connecting sessions

Teradata Parallel Transporter ODBC Operator Version 14.00.00.08

EXPORT_OPERATOR: private log specified: odbclog.txt-1

EXPORT_OPERATOR: connecting sessions

EXPORT_OPERATOR: TPT17122: Error: unable to connect to data source

EXPORT_OPERATOR: TPT17101: Fatal error received from ODBC driver:

              STATE=IM003, CODE=0,

              MSG='[DataDirect][ODBC lib] Specified driver could not be loaded'

EXPORT_OPERATOR: disconnecting sessions

EXPORT_OPERATOR: TPT17124: Error: unable to disconnect from data source

EXPORT_OPERATOR: TPT17101: Fatal error received from ODBC driver:

              STATE=08003, CODE=0,

              MSG='[DataDirect][ODBC lib] Connection not open'

EXPORT_OPERATOR: Total processor time used = '0.11 Second(s)'

EXPORT_OPERATOR: Start : Wed May 28 10:04:13 2014

EXPORT_OPERATOR: End   : Wed May 28 10:04:13 2014

LOAD_OPERATOR: preparing target table

LOAD_OPERATOR: entering Acquisition Phase

LOAD_OPERATOR: disconnecting sessions

LOAD_OPERATOR: Total processor time used = '19.33 Second(s)'

LOAD_OPERATOR: Start : Wed May 28 10:04:13 2014

LOAD_OPERATOR: End   : Wed May 28 10:04:41 2014

 

Could you please help me on this?

25 Aug 2014

Nice article.. can I use Tpt to transfer data from teradata to Oracle?

mvu 11 comments Joined 12/09
03 Sep 2014

Unfortunately, TPT cannot transfer data fromTeradata to Oracle.  

pyite 2 comments Joined 10/14
28 Oct 2014

Hello, could you help me with the error I am receiving?
 
Teradata Parallel Transporter Load Operator Version 15.00.00.00
W_1_o_other_odbc: private log not specified
Teradata Parallel Transporter ODBC Operator Version 15.00.00.00
W_0_o_other_odbc: private log not specified
W_0_o_other_odbc: connecting sessions
W_0_o_other_odbc: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5701,
MSG='[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'master'.'
W_0_o_other_odbc: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5703,
MSG='[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.'
W_0_o_other_odbc: TPT17175: Warning: Message received from ODBC driver:
STATE=S1092, CODE=0,
MSG='[Microsoft][ODBC SQL Server Driver]Invalid attribute/option identifier'W_1_o_other_odbc: connecting sessions
W_1_o_other_odbc: preparing target table
W_1_o_other_odbc: entering Acquisition Phase
W_0_o_other_odbc: sending SELECT request
W_0_o_other_odbc: data retrieval complete
W_0_o_other_odbc: Total Rows Exported:  0

 

 

mvu 11 comments Joined 12/09
28 Oct 2014

Based on what you showed me, the messages from driver are not errrors.  They are informative message and warning.   The first two are informative and the last one is a warning.  
A session is successfully logged on and the SELECT query seems to  perform successfully.
I'm not sure what the problem is that your are seeking help here.

pyite 2 comments Joined 10/14
29 Oct 2014

Thanks for your response.
The issue is that 0 rows were exported from the source table (the last line of the output)

TDThrottle 11 comments Joined 11/11
02 Dec 2015

Hi,
Can I used defult ODBC driver shipped along with Teradata Tbuilt client to move data from Oracle to Teradata. Or is it necessary to purchase/install DataDirect client to do it. Not sure additional wired protocal supported by TTU 15.10 can replace DataDirect.
Thanks!
TDThrottle
 

You must sign in to leave a comment.