6734 error
The new 6734 error has the following remedies:
- Change the source characters in your SQL literals, object names, or data to US-ASCII characters in the 0x00 to 0x7F range.
- Change the client set from TD-ASCII to a standard supported client character set (for example, UTF8). If the source data contains characters not supported by the Latin server character set (for example, Latin-1 and Latin-9), also change the destination server character set to Unicode and the client character set to match the data (UTF8).
- Request a change to this error handling by contacting your Teradata Customer Support representative.
To match the current behavior for the US-ASCII 0x1A substitution character:
- Import to the Latin server character set preserves the character and does not return an error.
- Import to the Unicode server character set returns the new 6734 error (previously 6706 error).
Do not use US-ASCII if you use TD-ASCII to store MBCs in Latin columns.
6734 errors appears when importing characters from Western European languages from any external source. Data, object names, and literals may also cause the error.
6701 error
The 6701 error has the following remedies:
- Change the client character set from the proprietary TD-ASCII to a standard supported client character set (for example, UTF8). Note that the input characters must be proper UTF8 to be input into the system and there are differences in how data is exported, see Working with Export Widths.
- Request a change to this error handling by contacting your customer support representative.
5602 error
See the remedy for the 6734 error.