When Adaptive Server communicates with ECDA Option for Oracle, client language and the default character set are passed as thread properties. ECDA Option for Oracle interacts with Oracle, conveying the client language and Open Server character set. As a result, Adaptive Server receives the character data and error messages in the correct language and character set.
ECDA Option for Oracle has multiple settings that correspond to the character set and language setting, which you can set in many different ways. You must designate the character set to be consistent with the charset settings. If the configuration parameter charset is set to Sybase iso_1, the mapping coded in the “charsets” stanza must be mapped to the equivalent Oracle character set, which is we8iso8859p1. In addition, this setting must also be reflected in the “languages” stanza by including the we8iso8859p1 in the Oracle charset setting. If these are not set consistently and a character is used that is contained in either the Sybase or Oracle character set and not in the other, you may receive an ORA-00911: invalid character message.
ECDA Option for Oracle converts the incoming client characters to the charset setting. When characters are returned to the ECDA Option for Oracle client, they are then converted back to the character set setting of the client. The language setting corresponds to the language in which the local ECDA Option for Oracle error messages are returned. The setting for Oracle Language and Territory coded in the languages stanza is the language in which the Oracle-defined error messages are returned to the client. All attempts must be made to make sure the language settings match.
If the default character set for ECDA Option for Oracle does not match that of Adaptive Server/CIS and a writetext is issued to insert text, the text field is not converted as expected. For the us_english language, this is not a problem, because the normal printing characters are the same in the supported character sets. However, for other languages, this may be a problem for which the solution is to make sure that Adaptive Server/CIS has the same default character set as ECDA Option for Oracle.