73 | 14 Jul 2016 @ 08:59 PDT | General | Reply | Converting Time stamp in UTC including Day light Saving | The query is not attached. In any case, it sounds like Teradata support needs to assist in the timezone rules configuation settings in DBSControl, tdlocaledef and the gettimezonedisplacement UDF.
... |
72 | 31 May 2016 @ 07:03 PDT | Database | Reply | CREATE TABLE Failed [3737] - NAME REQUIRES MORE THAN 30 bytes IN LATIN INTERNAL FORM | With the Teradata Database 14.10 Extended Object Names feature, name lengths have been increased to 128. However, this depends on the NameValidationRule setting in DBSControl. See the Extended Obje... |
71 | 11 Apr 2016 @ 08:40 PDT | Database | Reply | Will increasing block size help handle the error : The maximum possible Row length in the table is too large | Large objects only take up about 50 bytes in the base table row for the object identifier as the data is stored in subtable rows. This may avoid the 3933, but introduce other issues when processing... |
70 | 08 Apr 2016 @ 07:20 PDT | Database | Reply | Will increasing block size help handle the error : The maximum possible Row length in the table is too large | The 3933 error will not be removed by increasing the block size. Perm and response rows are currently limited to ~64KB. This is the limit which is exceeded. The source table must be split into... |
69 | 31 Mar 2016 @ 11:27 PDT | General | Reply | How to use bteq to import data contains Chinese characters into Teradata table on a Red Hat Enterprise Linux Server? | Note: Posting text has been obfuscated due to a formal request by the owner of the Intelectual Property.
On your Create Table, is the server character set UNICODE for the COULMN_NAME_OBFUSCATED Us... |
68 | 18 Mar 2016 @ 08:40 PDT | General | Reply | Error 6706 The string contains an untranslatable character | The advantage is that UNICODE_TO_LATIN WITH ERROR is a supported TRANSLATE routine by Teradata DBS engineering whereas udf_utf16to8 is supported by Teradata GSC (aka Tak Takahashi). This does... |
67 | 05 Mar 2016 @ 10:59 PST | Database | Reply | Teradata Table Naming | There is no separate limit for load utility table names. How are you determining that there is a limitation?
|
66 | 29 Feb 2016 @ 07:12 PST | Tools | Reply | Mload failing when trying to load file with þ (thorn) as delimiter | You can find the definition of Teradata Latin and Teradata ASCII in Appendix C of the International Character Set reference manual. Another good reference is the Orange Book: "Getting Started:... |
65 | 05 Feb 2016 @ 09:51 PST | Database | Reply | Equivalent sentence in Teradata for the Oracle "CONVERT"? | If I understand correctly, you want the Teradata equivalent of the Oracle CONVERT function. For starters, I was pointing out some of the differences in string literals between the two products. The... |
64 | 04 Feb 2016 @ 06:50 PST | Database | Reply | Equivalent sentence in Teradata for the Oracle "CONVERT"? | Hi Juan,
The data type of character literals is in Teradata is always UNICODE. There is no need to convert/translate them. You can verify the characters are in Latin with the _Latin prefix.&n... |
63 | 24 Nov 2015 @ 12:37 PST | Database | Reply | string contains an untranslatable | If you need support for Chinese in the Teradata Database, then the Unicode server character set with a Unicode Client character set like UTF8 is the correct approach. Teradata currently (TD15.10) o... |
62 | 30 Oct 2015 @ 12:03 PDT | Database | Reply | tablename > 30 characters | I believe you mean 'truncating' instead of 'not returning':
BTEQ -- Enter your SQL request or BTEQ command:
ct "this EON table name has more ... |
61 | 15 Oct 2015 @ 07:36 PDT | Database | Reply | Activating new character sets other than default | There are server and client character sets in Teradata. Unicode is the only server character set which will support czech,russian, and romanian. Your client character set needs to match the Oracle ... |
60 | 14 Oct 2015 @ 08:14 PDT | Database | Reply | Object names length for tablename col. in dbc.tables is still 30 char in TD 15 | Deiter is correct. For more details, refer to the Data Dictionary reference chapter on views, and the 14.10 Extended Object Names Orange Book. Our plans are to remove the compatibility vi... |
59 | 06 Oct 2015 @ 06:58 PDT | Database | Reply | "The string contains an untranslatable character" in table name | Always use the modern views to access objects in the data dictionary. These view names end with a suffix of "V", "VX", or "V_SZ". In your case, you want the Table... |
58 | 14 Sep 2015 @ 07:00 PDT | Database | Reply | Account id an Account string | The reference manuals cover these topics in detail.
|
57 | 04 Sep 2015 @ 08:51 PDT | General | Reply | to show the special character while selecting from table | What are the character set details on how the string is stored and displayed?
In the Teradata Unicode server character set:
Š is the U+0160 LATIN CAPITAL LETTER S WITH CARON
¸... |
56 | 02 Sep 2015 @ 09:37 PDT | Database | Reply | Need Column Name with Longer than 30 Characters | Titles of up to 60 characters are allowed in 13.10, but titles are not column names. There is no way around this. You need to use the 14.10 Extended Object Names feature.
-Dave
|
55 | 26 Aug 2015 @ 10:24 PDT | Database | Reply | trademark sign ™ not properly inserted. | The I agree with Fred and recommend the UTF8 client character set in this case. The Trade Mark Sign is not specificed in either the Latin1, or Latin9, ISO-8859 standards. We do support it less comm... |
54 | 10 Aug 2015 @ 06:40 PDT | Database | Reply | utf8TO16 : why is it Latin to unicode conversion function when utf8 itself is unicode encoding? | I can't recommend that approach as the Kanji1 server character set is no longer supported. What release of the Teradata database is in use?
|
53 | 07 Aug 2015 @ 12:12 PDT | Database | Reply | utf8TO16 : why is it Latin to unicode conversion function when utf8 itself is unicode encoding? | Hi vuyyuru,
There are a couple of options:
The Teradata Labs supported approach is to create a Distinct UDT from Unicode which represents ISO8859-1.
The other approach woul... |
52 | 05 Aug 2015 @ 09:40 PDT | Tools | Reply | TPT UTF8 Import of "no valid unicode character" - need help | An import of U+10002A is uncommon as it is a user-defined character in the Supplementary Private Use Area-B. It could also be a corrupted encoding. Private use has been used by Japanese ... |
51 | 29 Jul 2015 @ 02:20 PDT | Database | Reply | UNICODE to CHAR Translate - TRANSLATE doesnt work. | The Unicode (U+2122) TRADE MARK SIGN does not translate to Teradata Latin. 0x99 is a control character in Teradata Latin. See the international Character Set Support reference for more details.
&n... |
50 | 24 Jul 2015 @ 08:22 PDT | Database | Reply | 2620: The format or data contains a bad character | What is the system locale for the format string '$ZZZZ,ZZ'? If it is en-US, then ',' (comma) is not the typical radix separator and '.' (dot) should be used. Check the SDF s... |
49 | 08 Jun 2015 @ 06:56 PDT | UDA | Reply | VARCHAR fields | You will want to read the Database-level Capacity Planning Considerations chapter (14) of the Database Design reference. It will answer all of these questions and more.
-Dave
|