Adaptive Server’s character set conversion reports conversion errors when a character exists in the client’s character set but not in the server’s character set, or vice versa. Adaptive Server must guarantee that data successfully converted on input to the server can be successfully converted back to the client’s character set when the client retrieves that data. To do this effectively, Adaptive Server must avoid putting suspect data into the database.
When Adaptive Server encounters a conversion error in the data being entered, it generates this message:
Msg 2402, Severity 16 (EX_USER): Error converting client characters into server’s character set. Some character(s) could not be converted.
A conversion error prevents query execution on insert and update statements. If this occurs, review your data for problem characters and replace them.
When Adaptive Server encounters a conversion error while sending data to the client, it replaces the bytes of the suspect characters with ASCII question marks (?). However, the query batch continues to completion. When the statement is complete, Adaptive Server sends the following message:
Msg 2403, Severity 16 (EX_INFO):
WARNING! Some character(s) could not be converted into client’s character set. Unconverted bytes were changed to question marks ('?').
