CODEWITHSUNDEEP
teradata
Teja Goud Kandula
Teja Goud Kandula

Reputation: 1574

How to interpret or decode the Hostdata column from Teradata error table

The use case is that, there is an Informatica Cloud mapping which loads from SQL Server to Teradata database. If there any failures during the run time of the mapping then that mappings writes all the failed rows to a table in Teradata database. The key column in this error table is HOSTDATA which I assume. I am trying to decode the HOSTDATA column so that if a similar ETL failure happens in the production then it would be helpful in identifying the root cause much quickly. By default HOSTDATA is a column of type VARBYTES.

To decode the HOSTDATA column, converted the column to ASCII and Base 16 format. None of them made any use.

Then tried the below from the Teradata forum.

Then tried to extract the data from the error table using a BTEQ script. For that the data is being exported into a .err file and it is being loaded back into the Teradata database using a fastload script. Fastload is unable to load the data because there is no specific delimiter for the data. There data in the .err file looks gibberish. Snapshot of the data from the .err file: enter image description here

My end goal is to interpret the Hostdata column in a more human readable way. Any suggestions in this direction are also welcome.

Upvotes: 2

Views: 407

Answers (1)

Fred
Fred

Reputation: 2080

The Error Table Extractor command twbertbl which is part of "Teradata Parallel Transporter Base" software is designed to extract and format HOSTDATA from the error table VARBYTE column.

Based on the screenshot in your question, I suspect you will need to specify FORMATTED as the record format option for twbertbl (default is DELIMITED).

Upvotes: 1

Related Questions