Based on the language support mode, a compatibility view casts the object name to 30 fixed characters in the Latin or Kanji server character set. Whenever data is not accessed via direct reference, the view cannot be used to update the underlying table. Therefore, you cannot use compatibility views to update object names in the underlying tables. Instead, you must use Unicode views.
Processes that ran on Release 12.0 or earlier may attempt to make updates through the DBC.Collations, DBC.CharTranslations or DBC.HostsInfo views. These views are deprecated and have not been supported since Release 12.0. Teradata strongly recommends that you update such processes to reference the corresponding Unicode views (for example, CollationsV, CharTranslationsV, and HostsInfoV) instead of the compatibility views.