2

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.

6
  • It's my understanding that what you are seeing is the buffer returned by the ODBC driver (sql server in this case) dumped into the err table. My guess, and I don't have an answer here, is that in order to shred this thing into human readable you would to treat this file as an odbc buffer using the ODBC standard and parse your way through the thing byte by byte. I don't know that a tool/library already exists so you don't have to dig through ODBC standards documentation and reinvent the wheel. Commented Mar 3, 2021 at 16:28
  • 1
    Check out the Error Table Extractor command twbertbl Commented Mar 3, 2021 at 19:39
  • btw - from the screenshot I would say this load used FORMATTED record format. Commented Mar 3, 2021 at 23:01
  • You pointed me in the right direction. I will explore more about twbertbl. Thanks @Fred. Commented Mar 5, 2021 at 0:56
  • @Fred, you can post it as an answer (add few details if you wanted to) so that I can choose it. :) Commented Mar 5, 2021 at 9:15

1 Answer 1

1

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).

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.