Extract data from ASW-POSTGRESQL to Teradata

Teradata Database on AWS

Extract data from ASW-POSTGRESQL to Teradata

Hi All,

 

I am trying to load data from POSTGRESQL mounted in AWS to teradata db(16.20) using an data integratin ETL tool(wherescape 6.8.5).

 

I have successfully established connecteion between AWS POSTGRE and my teradata DB using "Teradata 7.1 PostgreSQL Wire Protocol" driver. this connection is successful. 

 

When I try to load data from POSTGRE-AWS to my teradat DB, I am getting the below error.

"

TPT_INFRA: TPT01036: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) terminated due to the receipt of signal number 11
 
TPT_INFRA: TPT01037: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) core dumped"

 

Any help on this topic, would be more helpful.

 

I have given the detailed log below, for your reference.

 

Teradata Parallel Transporter Version 16.20.00.05 64-Bit
Job log: /opt/teradata/client/16.20/tbuild/logs/wsl-ST_BRO_CLM_MBR-24303239-959.out
Teradata Parallel Transporter SQL DDL Operator Version 16.20.00.05
Job step setup_tables completed successfully
Teradata Parallel Transporter ODBC Operator Version 16.20.00.05
Teradata Parallel Transporter Update Operator Version 16.20.00.05
UPDATE_OPERATOR: private log specified: ST_****_LOAD
ST_***_READ_OPERATOR: connecting sessions
UPDATE_OPERATOR: connecting sessions
TPT_INFRA: TPT01036: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) terminated due to the receipt of signal number 11

TPT_INFRA: TPT01037: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) core dumped
UPDATE_OPERATOR: preparing target table(s)
UPDATE_OPERATOR: entering DML Phase
UPDATE_OPERATOR: entering Acquisition Phase
UPDATE_OPERATOR: disconnecting sessions
UPDATE_OPERATOR: Performance metrics:
UPDATE_OPERATOR: MB/sec in Acquisition phase: 0
UPDATE_OPERATOR: Elapsed time from start to Acquisition phase: 2 second(s)
UPDATE_OPERATOR: Elapsed time in Acquisition phase: 0 second
UPDATE_OPERATOR: Elapsed time in Application phase: 0 second
UPDATE_OPERATOR: Elapsed time from Application phase to end: < 1 second
UPDATE_OPERATOR: Total processor time used = '0.191971 Second(s)'
UPDATE_OPERATOR: Start : Tue Jul 30 13:42:47 2019
UPDATE_OPERATOR: End : Tue Jul 30 13:42:49 2019
Job step load_tables terminated (status 8)
Job wsl-ST_BRO_CLM_MBR-24303239 terminated (status 8)
Job start: Tue Jul 30 13:42:46 2019
Job end: Tue Jul 30 13:42:49 2019
Using memory mapped file for IPC

TPT_INFRA: TPT04101: Warning: Teradata PT cannot connect to Unity EcoSystem Manager.
The job will continue without event messages being sent to Unity EcoSystem Manager.
TPT_INFRA: TPT04197: Warning: OMD API failed to initialize
Teradata Parallel Transporter PlanExecutor Version 16.20.00.05
Total Available Memory: 11538272
DSMemoryPercentage: 39
Using Message Size: 1048576

Teradata Parallel Transporter Coordinator Version 16.20.00.05
Teradata Parallel Transporter Executor Version 16.20.00.05
Teradata Parallel Transporter SQL DDL Operator Version 16.20.00.05
**** 13:42:47 Options in effect for this job:
OperatorType: Producer
Instances: 1
Character set: 'ASCII'
Checkpoint: No checkpoint in effect
DataBlockSize: 2048K bytes

===================================================================
= =
= SQL Session Connection =
= =
===================================================================

**** 13:42:47 Connecting to RDBMS: 'BRO***S'
**** 13:42:47 Connecting with UserId: 'OEA**_T'
ST_BRO_CLM_MBR_READ_OPERATOR: connecting sessions
UPDATE_OPERATOR: connecting sessions
TPT_INFRA: TPT01036: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) terminated due to the receipt of signal number 11

TPT_INFRA: TPT01037: Error: Task (TaskID: 7{delim} Task Name: SELECT_2[0001]) core dumped

UPDATE_OPERATOR: preparing target table(s)
UPDATE_OPERATOR: entering DML Phase
UPDATE_OPERATOR: entering Acquisition Phase
UPDATE_OPERATOR supports the max row size 1024KB.
Job step 'load_tables' uses the max row size 1024KB.
TPT_INFRA: TPT02255: Message Buffers Sent/Received = 0{delim} Total Rows Received = 0{delim} Total Rows Sent = 0
UPDATE_OPERATOR: disconnecting sessions
UPDATE_OPERATOR: Performance metrics:
UPDATE_OPERATOR: MB/sec in Acquisition phase: 0
UPDATE_OPERATOR: Elapsed time from start to Acquisition phase: 2 second(s)
UPDATE_OPERATOR: Elapsed time in Acquisition phase: 0 second
UPDATE_OPERATOR: Elapsed time in Application phase: 0 second
UPDATE_OPERATOR: Elapsed time from Application phase to end: < 1 second
UPDATE_OPERATOR: Total processor time used = '0.191971 Second(s)'
UPDATE_OPERATOR: Start : Tue Jul 30 13:42:47 2019
UPDATE_OPERATOR: End : Tue Jul 30 13:42:49 2019
Job step load_tables terminated (status 8)
Job wsl-ST_***_MBR-24303239 terminated (status 8)
Job start: Tue Jul 30 13:42:46 2019
Job end: Tue Jul 30 13:42:49 2019
Total available memory: 11538272
Largest allocable area: 11538272
Memory use high water mark: 106968
Free map size: 1024
Free map use high water mark: 15
Free list use high water mark: 0

 

 

 

Thanks,

Naveen

4 REPLIES 4
Teradata Employee

Re: Extract data from ASW-POSTGRESQL to Teradata

Signal 11 (SIGSEGV) is a segmentation violation. Your log does not show a successful ODBC connection; you may need to look at the private log and/or trace for the ODBC operator. 

 

Be sure you are using the 64-bit version of the branded ODBC driver

 

Re: Extract data from ASW-POSTGRESQL to Teradata

Thanks Fred.  We tried with 64-bit ODBC adminstartor. We tested the connection through 64-bit ODBC administartor- using the driver 'teradata 7.1 PostgreSQL Wire Protocol' and the connection was successful. But unfortunately, the data integartion tool- Wherescape 6.8.5 - which we are using for ETL(for data extraction and transformation) does not support 64-bit odbc administartor. 

 

Is there any other we can fix the 'signal 11' TPT error ?

Highlighted
Teradata Employee

Re: Extract data from ASW-POSTGRESQL to Teradata

You need to fix your ODBC ini file and/or PATH setting. 

On Linux, for example, you'd want TPT to use drivers from /opt/teradata/client/16.20/tbuild/odbc/lib64, not /opt/teradata/client/16.20/tbuild/odbc/lib.

 

Enthusiast

Re: Extract data from ASW-POSTGRESQL to Teradata

Binary log would help you get more clues on signal 11, use tlogview -l <binarylogfilename> -f "*" -g -o extractedoutfile.txt

Best regards,
Sandeep.

GANGA SANDEEP KUMAR