In accordance with Teradata internationalization plans, KANJI1 support is deprecated and is to be discontinued in the near future. KANJI1 is not allowed as a default character set; the system changes the KANJI1 default character set to the UNICODE character set. Creation of new KANJI1 objects is highly restricted. Although many KANJI1 queries and applications may continue to operate, sites using KANJI1 should convert to another character set as soon as possible. For more information, see KANJI1 Character Set in Teradata Vantage™ NewSQL Engine International Character Set Support, B035-1125.
When the server character set is KANJI1 and the client character set is KanjiEBCDIC, the offset count includes Shift-Out/Shift-In characters, but they are not matched. They are treated only as an indication of a transition from a single byte character and an multibyte character.
The nonzero position of the result is reported as follows:
|IF the character set is …||THEN the result is the …|
|KanjiEBCDIC||position of the first byte of the logical character offset (including Shift-Out/Shift-In in the offset count) within string_expression_1.|
|other than KanjiEBCDIC||logical character offset within string_expression_1.|