unloaded Date value issue by tpt script

Tools & Utilities
Enthusiast

Re: unloaded Date value issue by tpt script

for your information-

load script-

USING CHARACTER SET UTF8

DEFINE JOB dc_load

DESCRIPTION 'Load a Teradata table from a file'

(

  APPLY $INSERT TO OPERATOR( $UPDATE()[@LoadInstances] )

  SELECT * FROM OPERATOR( $DATACONNECTOR_PRODUCER()[@DCPInstances] );

);

unload script-

USING CHARACTER SET UTF8

DEFINE JOB delimited_file_unload

DESCRIPTION 'Export rows from a Teradata table to a delimited file'

(

  APPLY TO OPERATOR ($DATACONNECTOR_CONSUMER())

  SELECT * FROM OPERATOR ($EXPORT()); 

);

Teradata Employee

Re: unloaded Date value issue by tpt script

Thank you! I will let you know when we find something out.

-- SteveF
Teradata Employee

Re: unloaded Date value issue by tpt script

Possible workaround:

Add another atribute to the DC operator:

AppendDelimiter='Y'

(check to see if it is in the DC operator template file for your version of TPT)

This will force a delimiter to be placed at the end of every record.

And will hopefully get around the bug in which a delimiter followed by end-of-record is not being treated as a NUILL field.

-- SteveF
Not applicable

Re: unloaded Date value issue by tpt script

Hi Steve,

May I know is there any update on the fix to export '0001-01-01' date when we are using DEFINE SCHEMA <name> FROM TABLE <tname>; ?

Since we are trying to export all the tables in an entire database and transfer the exported data file to another region's server, and then load to DB, the DEFINE SCHEMA <name> FROM TABLE <tname>; method sounds much more convenient to us.

We are using TTU 14.10. So when will it be fixed?

Thanks,

Leo

Teradata Employee

Re: unloaded Date value issue by tpt script

I will check the development schedule tomorrow if I have a chance (if not Tuesday, then Wednesday). I imagine it will be a few months. We do not release an efix for every release in each month (we currently support releases 13.10, 14.0, 14.10, 15.0, 15.10 and are currently working on release 16.0).

The only other option (when it becomes available) is to offer you a D2D (a developer-to-developer) copy of the software, which is an engineering copy (not an official release). However, we do not allow D2Ds to be used in production environments. And I cannot commit to when a D2D would become available, but it (obviously) be sooner than the official release.

-- SteveF

Re: unloaded Date value issue by tpt script

I am facing an issue while loading data using SSIS to Teradata.

I am having an XML file to load and as destination object am using "Teradata Destination" so the XML parser being source return 21 tags to be loaded.

So, if am trying to load all 21 in parallel it return an error and when am tryint to load only 13 out of those 21 it works fine.

 

SSIS is internally using TPT load to load the data.

 

Error Message:

 

"Error 5584: TPT Import error encountered during Initiate phase. CLI2: SESSOVER(301): Exceeded max number of sessions allowed."

 

Please Suggest!!!!

Enthusiast

Re: unloaded Date value issue by tpt script

Hi Steve, I got one new issue. I have one field with timestamp(6) and value in source table is NULL. But while unloading and then loading records are getting rejected with error 6706.

I tried in format binary,formatted ,with quote ,without quote. But same error.

Teradata Employee

Re: unloaded Date value issue by tpt script

What does the output file for that row look like?

Also, have you tried Export-to-Load without writing the data to a file to see the results?

-- SteveF
Enthusiast

Re: unloaded Date value issue by tpt script

Hi Steve , I am loading with tpt table to table. But got a new issue.

The column name in my table is with space.

Column names are as-

"Daily Total" INTEGER,

Teradata is allowing to create the column name with space. But while loading table to table. it is failing for schema issue.

Teradata Employee

Re: unloaded Date value issue by tpt script

I will need more information that this.

I will need the script, version of TPT, exact error message, etc.

-- SteveF