Message Language Problems

You can configure Replication Servers to print messages to the error log and to clients in English, and other foreign languages. This allows server programs in your replication system, including Replication Servers, and Adaptive Servers, to write messages to their error logs in the configured language. Depending on the server, they may or may not send messages to a client in the client’s language.

For example, Adaptive Server checks for the language setting of its client (Replication Server) and returns messages in that language. Replication Server, however, does not check for a client’s language; instead, it returns messages to a client in its own language. This can result in error logs with messages in different languages if the servers are configured in different languages.

Stored procedures use the language of their Adaptive Server connection. Therefore, if you have a mixed-language environment, Adaptive Server stored procedure messages may be in a different language from the Replication Server.

For example, if you log in to Adaptive Server using French and execute a stored procedure, the stored procedure generates messages in French, even if the language setting of Replication Server is English or Japanese. If you log in to Adaptive Server with a language that is not installed at the Adaptive Server, Adaptive Server returns stored procedure messages in English.

Sybase may not always translate new or changed messages into French, German, Spanish, Chinese, Korean, or Japanese. In this case, the Replication Server, or rs_subcmp messages use the English version of the message.

Misplaced message localization files can also cause message language problems. Verify that the files are in the correct directories.

To avoid the confusion that can result from a mixed-language error log, Sybase recommends that you configure the Replication Server so that all languages are the same.