Teradata PT 12.0 error output schema does not match

Tools & Utilities
Teradata Employee

Re: Teradata PT 12.0 error output schema does not match

TPT is a 32-bit application.

-- SteveF
Highlighted

Re: Teradata PT 12.0 error output schema does not match

I need help with the following issue.I am looking to extract data from Teradata into several files on unix nodes. Right now we are using TPT EXP to extract data which is in order of terabytes. The data is chunked into several gigabytes based on date. 3 to 4  export TPT jobs write chunked data into different files on one unix node. we need a window of 20 hours and multiple fexp on the server to achieve this. Now I would like to split the same TPT exp job(using one export operator) writing subset of resultset into different files on multiple unix nodes,so that more data can be extracted with one fexp utility slot (to overcome the i/o bottleneck of disk on unix nodes). How can I achieve this.

@feinholz In one of your replies "(There is a way (a bit more complex) to "fake out" TPT)"  I think you mentioned this kind of scenario. Could you please elaborate how to solve my issue.

Thanks in advance

Teradata Employee

Re: Teradata PT 12.0 error output schema does not match

Script-based TPT does not currently enable the user to write out data to files on different Unix nodes.

The "faking" out reference was an ability to read data with different schemas, and yet to load the data into separate tables. In other words, for example, reading data from 3 flat files, each one with a separate schema, and within a single load job load the data from the 3 files into 3 different tables.

We normally enforce all of the data to conform to a single schema, but there is a way to get around this by defining a "super-schema" (the union of all 3 schemas into 1). But like I said, it is a long explanation and may not be what you are looking for.

-- SteveF

Re: Teradata PT 12.0 error output schema does not match

All,

When I have the following query: CASE WHEN TOTAL_PASS = 1 THEN 1 ELSE  0 END as COMPLIANCE it seems to work when i do this: CASE WHEN TOTAL_PASS = 1 THEN 'Y' ELSE  'N' END as COMPLIANCE. I get the output schema error. I would think this would not happen because the 'Y' and 'N' data type would be varchar. am I missing something. Would I need to cast this to be something else? if so how would I do that in a case statement.

Thanks

Teradata Employee

Re: Teradata PT 12.0 error output schema does not match

What is the data type of COMPLIANCE?

In the future, try to provide more information (like a copy of the script?).

-- SteveF