This post describes how to use a different codepage when the Oracle Transparent Gateway accesses an Attunity Connect datasource.
For the most part what you need to do is the same as for the previous thread, setting up the Oracle Transparent Gateway to access an Attunity Connect datasource. The only differences are in step (2). You must set the codepage in both the HS_FDS_CONNECT_STRING and Oracle environment.
The first thing you need to do is find the name(s) of the codepage in Oracle and Attunity. For example, the codepage that Oracle calls American_america.AL32UTF8, Attunity calls UTF-8.
Knowing the codepage name(s) you make two modifications to the Oracle init file, init(datasource_name).ora.
In the HS_FDS_CONNECT variable you add an environment object with the Attunity codepage name after the remotemachines object inside the binding object. For example:
where ... alludes to that part of the connect string that is the same as in the other thread. Remember that it is critical that the string inside the quotes is all on one line. The newlines in this document are for readability only.
At the end of the file add a line containing the Oracle environment name with the Oracle codepage name:
Note that the Oracle variable name HS_LANGUAGE is specific to Oracle version 10.1.0.4 on Sun Solaris and may be different depending on your specific Oracle version and the platform on which you are running Oracle.
For example, it is HS_NLS_LANGUAGE in version 18.104.22.168 on Windows. Please check with your Oracle documentation and verify the Oracle variable name.