Character Set Definitions - Teradata Viewpoint

Teradata Viewpoint User Guide

Product

Teradata Viewpoint

Release Number

16.10

Published

June 2017

Language

English (United States)

Last Update

2018-03-29

dita:mapPath

hkd1478709580913.ditamap

dita:ditavalPath

2206_User_vp_1610.ditaval.ditaval

dita:id

B035-2206

lifecycle

Product Category

Analytical Ecosystem

When you configure the general setup of a Teradata Database system, the Character Set settings allow you to define the charset that the system uses to communicate with Teradata Viewpoint. The character set definitions are optional. If you do not define them, Teradata Viewpoint uses the Teradata Database system settings.

Character Set Fields	Character Set Definition Suggestions
Session	The UTF8 session character set is strongly recommended for the Teradata Viewpoint session to ensure end-to-end fidelity of character data by avoiding conversion between character sets.
Monitor	Teradata Database 14.10 and later: The UNICODE session character set is supported by Teradata Database 14.10 and later. Teradata Database 14.0: Use Non-Unicode session character sets, such as LATIN1252_0A, KANJISJIS_OS, and KANJIEUC_OU, to create Teradata Viewpoint object names that connect Monitor and Console Partitions.
JDBC Flag	The JDBC Flag setting is a legacy-support feature to assist the transition away from the unsupported use of Teradata Database to store non-Latin characters in a Latin column, and the unsupported access of non-ASCII in an ASCII session character set. The JDBC Flag option specifies the CLIENT_CHARSET connection parameter, which can be used to override the Teradata JDBC Driver fixed-mapping of the Teradata session character set to the Java character set. The valid values are the actual Java character set names. Here are two examples of valid JDBC Flag settings: Windows-936 from Chinese (PRC) Windows-950 for Chinese (Taiwan)

Character Set Fields

Character Set Definition Suggestions

Session

The UTF8 session character set is strongly recommended for the Teradata Viewpoint session to ensure end-to-end fidelity of character data by avoiding conversion between character sets.

Monitor

Teradata Database 14.10 and later: The UNICODE session character set is supported by Teradata Database 14.10 and later.

Teradata Database 14.0: Use Non-Unicode session character sets, such as LATIN1252_0A, KANJISJIS_OS, and KANJIEUC_OU, to create Teradata Viewpoint object names that connect Monitor and Console Partitions.

JDBC Flag

The JDBC Flag setting is a legacy-support feature to assist the transition away from the unsupported use of Teradata Database to store non-Latin characters in a Latin column, and the unsupported access of non-ASCII in an ASCII session character set. The JDBC Flag option specifies the CLIENT_CHARSET connection parameter, which can be used to override the Teradata JDBC Driver fixed-mapping of the Teradata session character set to the Java character set. The valid values are the actual Java character set names. Here are two examples of valid JDBC Flag settings:

Windows-936 from Chinese (PRC)
Windows-950 for Chinese (Taiwan)

The default Teradata Database system settings are listed below.

Teradata Database	Language Support Mode	Data Dictionary Charset	Teradata Viewpoint Session Charset	Teradata Viewpoint Monitor Charset	Limitations
14.10 and later	Standard	UNICODE	UTF8	UTF8
14.10 and later	Japanese	UNICODE	UTF8	UTF8
14.0	Standard	UNICODE	UTF8	ASCII or LATIN1252_0A	ASCII session only supports the limited 7-bit ASCII characters
14.0	Japanese	UNICODE	UTF8	KANJISJIS_OS	Unknown