The Gen r8 CSE is certified for Oracle 11g and can connect to a 64-bit version of the database. However the CSE is 32-bit software and needs to connect using the 32-bit Oracle client.
- The Oracle 11g 32-bit client cannot connect to a Oracle 64-bit database using the local (Bequeath Protocol) connection i.e. the 32-bit client must connect via the Oracle Listener. This means that the CSE is subject to the same condition and the Oracle Net Service Name for the CSE database needs to be configured in the tnsnames.ora file for the 32-bit client installation. NOTE: this will be a different location than the 64-bit database installation.
- The recommendation is actually to set the Net Service Name in the tnsnames.ora file for both 32-bit and 64-bt Oracle software installations. This will ensure that both 32-bit and 64-bit Oracle clients (including SQL*Plus) can resolve the Net Service Name and are able connect to the database. SQL*Plus is used by the CSE configuration program to check the database connection and configuring both clients avoids any PATH order problems i.e. it will not matter if the 64-bit or 32-bit version of SQL*Plus is picked up first.
- There are 2 options to force the use of a Net Service Name to connect to the CSE database:
- On Windows set the system environment variable LOCAL to the Net Service Name. On Unix set the environment variable TWO_TASK to the Net Service Name. For example if the 32-bit client tnsnames.ora file has the Net Service Name DBCSE defined as follows then LOCAL or TWO_TASK should be set to the value DBCSE.
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(SERVER = DEDICATED)
(SERVICE_NAME = ORCL)
Setting LOCAL or TWO_TASK will ensure that any Oracle connection will default to using the Net Service Name defined and go via the Listener, instead of the bequeath connection. This is the cleanest option if the CSE is running on a dedicated server and connections to other Oracle databases are not a concern. The CSE configuration program should execute seamlessly and the resulting iefmd.ini file will contain standard connection parameters e.g.
"DBNAME=DBCSE DBUSER=ency DBPSWD=ency".
The environment variable (LOCAL or TWO_TASK) will need to remain in place for the iefmd to execute successfully.
- Do not set the environment variables from section "a". Instead use the syntax userid@<Net_Service_Name> for the Database User IDs in the CSE configuration program. This provides more flexibility if the CSE is sharing the machine with other Oracle databases and setting LOCAL or TWO_TASK is undesirable. The resulting iefmd.ini file will contain the Net Service Name syntax in the DBUSER field for the connection parameters. For example, referring to the same tnsnames.ora file as shown in section "a" where the Net Service Name is DBCSE, the connection parameters in the iefmd.ini file will then be:
"DBNAME=DBCSE DBUSER=ency@DBCSE DBPSWD=ency"