Learn about the environment variable settings that you must configure for Oracle Database and DB2 using native gateways.
For Oracle Database:
The Oracle BI Server uses the Oracle Call Interface (OCI) to connect to the database. OCI is installed by default with Oracle BI EE. You must use the bundled version to connect.
In the tnsnames.ora file, the Oracle Database alias, the defined entry name, must match the Data Source Name used in the repository connection pools of all physical Oracle databases.
When connecting to an Oracle Database data source, you can include the entire connect string, or you can use the net service name defined in the tnsnames.ora file. If you choose to enter only the net service name, you must set up a tnsnames.ora file in the following location within the Oracle BI EE environment, so that the Oracle BI Server can locate the entry:
BI_DOMAIN/config/fmwconfig/bienv/core
Edit the obis.properties file to set environment variables for the database client.
For DB2, you must do the following:
Install the appropriate database client on the computer running the Oracle BI Server, then edit the obis.properties file to set environment variables for the database client.
For Windows, you can set environment variables for DB2 in the obis.properties file. For example, if configuring DB2 CLI, then you must modify obis.properties to include the DB2 executable path.
You need to create a catalog associated with each database so that the client connects to the database by catalog name. To create a catalog associated with each database, enter and run the following command:
db2 catalog tcpip node <DB2 database> remote <hostname> server <port number>; db2 catalog database <DB2 database> as <DB2 database> at node <DB2 database>; connect to <DB2 database> user db2admin using welcome1
For an example, see Sample obis.properties Entries for Oracle Database and DB2 (32-Bit).