On the General tab, in the Data source definition: Database field, ensure that the

Setting Up Data Sources on Linux and UNIX 15-5 ■ If you choose not to use the entire connect string in the repository connection pool, ensure that the net service name in the tnsnames.ora file matches the Data Source Name used in the connection pool. For example, in the following example of a tnsnames.ora entry, the corresponding Oracle BI repository connection pool Data Source Name is ITQA2. ITQA2 = DESCRIPTION = ADDRESS_LIST = ADDRESS = PROTOCOL = TCPHOST = ITQALAB2PORT = 1521 CONNECT_DATA = SERVICE_NAME = ITQALAB2.corp The following procedure shows how to check repository database and connection pool settings against the Oracle tnsnames.ora settings. To check that the repository database and connection pool settings are correct: 1. Open your repository in the Administration Tool. 2. In the Physical layer, double-click the database you want to check to display the Database dialog.

3. On the General tab, in the Data source definition: Database field, ensure that the

appropriate Oracle Database version is selected. Then, click OK. 4. Open the Connection Pool dialog for this data source. You might need to expand the database object in the Physical layer to see the Connection Pool object. 5. In the Connection Pool dialog, check that the following is true: – The Call interface field displays the appropriate value for the release of the Oracle Database you are using. – The Data source name field displays the Oracle Database net service name that you defined in the tnsnames.ora entry. – The User name and password fields contain the correct values. Change the values if necessary, then click OK. 6. In the Oracle Business Intelligence environment, open the tnsnames.ora file located in the following directory: ORACLE_HOMEnetworkadmin 7. Check that a valid net service name exists with the following characteristics: – Matches the connection pool settings for the Data Source Name – Specifies the targeted Oracle physical database About Updating Row Counts in Native Databases This topic applies if both of the following are true: ■ You are using the Update Rowcount functionality in the Administration Tool in offline mode ■ You are running a heterogeneous environment, such as the Oracle BI Server on UNIX, while remote administrators run the Administration Tool on Windows computers. 15-6 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition When using the Update Rowcount functionality in offline mode, the Administration Tool uses local data sources on the client computer, not the server data sources. Therefore, Oracle Database or DB2 clients must be configured on the Windows computer running the Administration Tool so that the following conditions are true: ■ Data sources point to the same database identified in the Oracle Business Intelligence user.sh file on the UNIX server. ■ The name of the local data source must also match the name of the data source defined in the Connection Pool object in the physical layer of the Oracle BI repository .rpd file. If these conditions are not true, and if the server and client data sources are pointing at different databases, then erroneous updated row counts or incorrect results appear. Using DataDirect Connect ODBC Drivers on Linux and UNIX Oracle Business Intelligence provides DataDirect Connect ODBC drivers and driver managers for Linux and UNIX operating systems for connectivity to Microsoft SQL Server, Sybase ASE, and Informix databases. After Oracle Business Intelligence is installed, the DataDirect Connect ODBC 32-bit drivers are installed in ORACLE_HOMEodbclib. The 64-bit drivers are installed in ORACLE_HOMEodbclib64. Note that communication between database clients and servers is typically independent of the widths and data paths. In other words, the 32-bit database drivers can communicate with 64-bit database servers, and vice versa. You do not need to set the ODBCINI environment variable to set up the DataDirect Connect ODBC drivers. This variable is set automatically during installation. Refer to System Requirements and Certification for information about supported operating systems, databases, and driver versions for the DataDirect Connect ODBC drivers. This section contains the following topics: ■ Configuring the DataDirect Connect ODBC Driver for Microsoft SQL Server Database ■ Configuring the DataDirect Connect ODBC Driver for Sybase ASE Database ■ Configuring the DataDirect Connect ODBC Driver for Informix Database Configuring the DataDirect Connect ODBC Driver for Microsoft SQL Server Database The name of the DataDirect ODBC driver file to connect to a Microsoft SQL Server database is SEmsss23.so SEmsss23.sl on HP-UX PA-RISC. See System Requirements and Certification for supported versions of Microsoft SQL Server. To configure the DataDirect Connect ODBC Driver to connect to Microsoft SQL Server: 1. Open the user.sh file. You can find this file at: ORACLE_INSTANCE bifoundationOracleBIApplicationcoreapplicationsetupuser.sh 2. In the section for your operating system, include the appropriate library path environment variable for the DataDirect Connect libraries. Make sure to point to the appropriate library, depending on whether you are using a 32-bit or 64-bit database. Note the following: Setting Up Data Sources on Linux and UNIX 15-7 ■ For Solaris and Linux, the library path variable is LD_LIBRARY_PATH. ■ For HP-UX, the library path variable is SHLIB_PATH. ■ For AIX, the library path variable is LIBPATH. For example, to set the library path variable for the 32-bit driver on Linux: Linux: Oracle BI 32 bit mode SQLServer 2000 Parameters --------------------------------------- LD_LIBRARY_PATH=userlocalOracleBIodbclib: LD_LIBRARY_PATH export LD_LIBRARY_PATH 3. Save and close the file. 4. Open the odbc.ini file. You can find this file at: ORACLE_INSTANCE bifoundationOracleBIApplicationcoreapplicationsetupodbc.ini 5. Create an entry for your database, ensuring that the ODBC connection name is identical to the data source name specified in the connection pool defined in the repository. Be sure to set the Driver parameter to the file name and location of the DataDirect Connect driver for Microsoft SQL Server. In the following example, the Driver parameter is set to the 64-bit DataDirect Connect driver, and the data source name is SQLSERVER_DB. [SQLSERVER_DB] Driver=usrOracleBIodbclib64SEmsss23.so Description=DataDirect 5.1 SQL Server Wire Protocol Address=111.111.111.111,1433 AlternateServers= AnsiNPW=Yes ConnectionRetryCount=0 ConnectionRetryDelay=3 Database=dbschema_name LoadBalancing=0 LogonID= Password= QuoteID=No ReportCodePageConversionErrors=0 6. Save and close the odbc.ini file. 7. Open your repository in the Administration Tool on a Windows computer. 8. In the Physical layer, double-click the database object for the Microsoft SQL Server database. 9. Click the Features tab and scroll to the IDENTIFIER_QUOTE_CHAR parameter. Then, replace the value for this parameter with single quotes. The default value is double quotes .

10. Click OK.