Here is what I have that is causing the error........
CREATE MULTISET TABLE DLAB_MARKETING.Click,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT,
PRIMARY INDEX (AccountID);
Te problem is with the column name TriggeredSendDefinitionObjectID , this has more than 30 characters.
3737 - Name is longer than 30 characters.
Hi my table name is 26 characters and my column names are not more than 30 chars.
but I got this error :[Error 3737] [SQLState 42000] Name requires more than 30 bytes in LATIN
Your tablename is probably too long, when you check http://developer.teradata.com/doc/connectivity/jdbc/reference/current/jdbcug_chapter_2.html#BABIIEAG you'll findJDBC FastLoad creates two temporary error tables with the following naming convention: ._ERR_1 and ._ERR_2
andThe name of the destination table in the Teradata Database that is to be used by JDBC FastLoad CSV must not exceed 24 characters because of the name of the two error tables created by JDBC FastLoad CSV
If this was a standard FastLoad i would simply add ERRORTABLES and use my own error table names, but this seems not to be available in JDBC FastLoad. So your only option is to create the table with a shorter name, FastLoad it and thensubmit a RENAME TABLE.
My Largets column name is 29 char long. still i am facing the same error.
SELECT Failed 3737: Name requires more than 30 bytes in LATIN internal form.thanks.
Name requires more than 30 bytes in LATIN internal form.
Based on the error message this seems to be a SELECT, could you show it (or at least the column names/aliases used)?
I have a table named TN_ORDERLINE_DEPENDENCY_TYPE_LNDG. None of its columns are more than 30 characters. I am able to create the table in one environment while it;s failing in other. Both the environments have TD release of 14.10.03.06. Can you please suggest what might be different in two environments?
your tablename is more than 30 char.TN_ORDERLINE_DEPENDENCY_TYPE_LNDG .. please reduce below 30 and then create in both env. then let know if still issues
You should open a new discussion for a new topic.
On the different behaviour between two systems both on 14.10:
14.10 is long object name enabled - this means dbc tables and V views can store long object names - up to 128 chars.
But you can set dbc control fields to NOT allow this.
And this is disabled for systems which are upgraded from older releases but is enabled by default for new systems where a sysinit had been performed.
Could it be that one of your systems was upgraded (e.g. the production box) and one was delivered with 14.10?
Der Beginn aller Wissenschaften ist das Erstaunen, dass die Dinge sind, wie sie sind.-Aristoteles
The DBS Control settings referenced by Ulrich are: EnableEON, NameValidationRule, and LanguageSupportMode. It is possible to enable Globalization rule naming during an upgrade.
Please see the Orange book: 'Teradata Extended Object Names' which covers these areas in more detail.