Each client character set and each server character set includes an error character.
For information about how error characters are used and handled in sessions with Unicode Pass Through enabled, see UNICODE PASS THROUGH.
Client Error Characters
The following table lists the error characters associated with each client character set.
| Client Character Set | Error Character |
|---|---|
|
0x1A |
|
0x3F |
Server Error Characters
The following table lists the error characters for the server character sets.
| Form-of-Use | Error Character |
|---|---|
| LATIN server character set | 0x1A |
| KANJISJIS server character set | 0x1A |
| UNICODE server character set | U+FFFD |
| GRAPHIC server character set | U+FFFD |
| GRAPHIC server character set, VARGRAPHIC function | U+F8FF |
Conversion of Error Characters
Internal conversion between the server character sets preserves the error character.
For example, when translating from LATIN to UNICODE to KANJISJIS, 0x1A translates to U+FFFD which translates to 0x1A.
Example: Character Cannot Be Represented in a Character Set
Suppose that a column declared as CHAR(2) CHARACTER SET UNICODE stores CAPITAL LETTER A WITH MACRON ( ).
The VantageCloud Lake representation is as follows.
| 01 | 00 | 00 | 20 |
| Ā | |||
The export width for the session is set to the expected defaults and the conversion options are set to ignore conversion.
The character cannot be represented in ASCII, and is therefore converted to the ASCII error character 0x1A, represented is as follows.
| 1A | 20 |
| not valid |