|446||06 May 2013 @ 10:57 PDT||Tools||Reply||bteq export and import for _ET dataparcel||The data in the varbyte does not have the delimiter. We do not send "delimited" data to Teradata. We process the delimited data and send the row to Teradata as a series of VARCHAR fields.... |
|445||06 May 2013 @ 03:47 PDT||Tools||Reply||bteq export and import for _ET dataparcel||Even though the data is in a binary format, the only reason why it is stored in a VARBYTE is so that the endianness character set encoding is preserved. The data itself is in the exact format that ... |
|444||06 May 2013 @ 10:39 PDT||Tools||Reply||bteq export and import for _ET dataparcel||The tool is still in development. There is no release date yet.
|443||23 Apr 2013 @ 02:15 PDT||Tools||Reply||TPT19350 I/O error on file||You should read the documentation to understand the various formats that we support, and then when creating that file, make sure to create it with one of the supported formats.
Our own tools (obvi... |
|442||22 Apr 2013 @ 02:39 PDT||Tools||Reply||TPT19350 I/O error on file||You have specified a record format of "formatted".
Are you sure your data file adheres to the required format?
|441||17 Apr 2013 @ 12:35 PDT||Tools||Reply||TPT + Named pipes||TPT requires the file names in the -f option be a physical disk file.
|440||08 Apr 2013 @ 06:26 PDT||Tools||Reply||Strange Errorcode in TPT error table||Did you really obtain that information from executing a SELECT statement against the error table? Normally, the content of the "DataParcel" field is not legible.
|439||08 Apr 2013 @ 01:21 PDT||Tools||Reply||Using name of Flat File in TPT Load ||Right now, the METADATA feature is only supported with a record format of DELIMITED.
|438||21 Mar 2013 @ 11:59 PDT||Tools||Reply||Improving Loading Mechanism using Fastload||Yes. TPT supports it.
Please refer to the TPT documentation (user guide).
|437||18 Mar 2013 @ 10:42 PDT||Tools||Reply||SQL_SELECTOR: TPT15105: Error 13 in finalizing the table schema definition||Well, without seeing the entire script, what you have shown me is a Selector operator retrieving 2 DECIMAL columns and a VARCHAR. Therefore, your schema must match.
|436||18 Mar 2013 @ 06:01 PDT||Tools||Reply||SQL_SELECTOR: TPT15105: Error 13 in finalizing the table schema definition||@ericsun2: the schema must match the data. Thus the Selector is retrieving 2 DECIMALs and a VARCHAR. Your schema does not match that.
And yes, if you are using a client session character set of UT... |
|435||18 Mar 2013 @ 11:20 PDT||Tools||Reply||Tpump Error, Invalid session mode||The user cannot change the session mode.
TPump will always run in Teradata mode.
|434||14 Mar 2013 @ 05:31 PDT||Tools||Reply||MLOAD Question||Sequential.
|433||12 Mar 2013 @ 10:14 PDT||Tools||Reply||MultiLoad instead of FastLoad||The Stream operator does NOT use ODBC.
The Update operator is part of TPT, so the answer to your first question is yes.
|432||11 Mar 2013 @ 10:39 PDT||Tools||Reply||Utilities to export data from Teradata to Oracle?||Our load/unload products are created to load data into Teradata.
|431||11 Mar 2013 @ 10:38 PDT||Tools||Reply||Teradata export to DB2 using TPT||Our load/unload products are created to load data into Teradata.
TPT only loads into Teradata.
|430||11 Mar 2013 @ 10:37 PDT||Tools||Reply||Error when loading table using OLE Load||Why would you use OLELoad to load data from a flat file into Teradata when we have our standard load/unload products that are much faster?
|429||08 Mar 2013 @ 03:35 PST||Tools||Reply||TPT return code 12 during INSERT||@gpolanch: it is not intuitive, but the WorkingDatabase dictates to which database context we switch after we connect. However, due to a backwards compatibility issue (we have to act the way MultiL... |
|428||27 Feb 2013 @ 07:02 PST||Tools||Reply||TPT export formatted/ timestamp schema mismatch||What version of 13.10 are you using?
The issue you are having was fixed in 13.10.00.07.
|427||27 Feb 2013 @ 04:51 PST||Tools||Reply||Teradata TPT Script||rku2013:
please post the entire script and entire schema file.
(you probably should have the entire "DEFINE SCHEMA" syntax in the external schema file)
|426||27 Feb 2013 @ 04:49 PST||Tools||Reply||Teradata TPT Script||Petlee: try
DEFINE SCHEMA S_SCHEMA DELIMITED FROM TABLE 'DBC.DBQLogTBL';
|425||13 Feb 2013 @ 11:55 PST||Tools||Reply||Using TPT to move Tables across Databases||The TPT User Guide will describe how to do that.
Also, there are sample scripts in the "samples" directory under the root install directory for TPT that should be able to provide the inf... |
|424||07 Feb 2013 @ 07:15 PST||Tools||Reply||Loading using Teradata Parallel Transporter Load utility.||The SELECT statement is not a Teradata SELECT statement. It is a TPT SELECT.
Thus, not all SQL is supported (please check the documentation).
We do not support the TRIM function in TPT.
Any &quo... |
|423||07 Feb 2013 @ 07:10 PST||Tools||Reply||How to get Character String Delimiter with TPT or FastExport||A TPT license does not cost any extra if you have a FastLoad/FastExport/MultiLoad license.
TPT is the load/unload tool going forward and thus it is the tool that will receive the new features and ... |
|422||30 Jan 2013 @ 06:36 PST||Tools||Reply||TPT error in loading from an external file||Is there an end-of-record marker after the last data item in the last record?