This section contains solutions that are related to a highly available deployment:
Parent topic: Deploying Oracle Exalytics for High Availability
You might find that the BI Server cannot connect to Oracle TimesTen on either the first or the second node. To resolve this issue, check the following:
Verify that the DSNs for Oracle TimesTen are configured correctly in the odbc.ini and opmn.xml files, as described in the following list:
The odbc.ini file in the ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup directory has the proper DSNs defined to connect to both instances of Oracle TimesTen, as described in Configuring the ODBC Connection from Oracle Business Intelligence to Oracle TimesTen.
The opmn.xml file in the ORACLE_INSTANCE/config/OPMN/opmn/ directory has the LD_LIBRARY_PATH variable set correctly to point to the shared library folder for Oracle TimesTen. The TIMESTEN_DLL variable must also be defined correctly, as shown in the following example:
<variable id="TIMESTEN_DLL" value="u01/app/oracle/product/TimesTen/tt1122/lib/libttclient.so"/>
The BI Server must use the ODBC driver for Oracle TimesTen Version 3.5 for connection.
During deployment of a repository, ensure that you use the ODBC driver for Oracle TimesTen Version 3.5 for the database connection pool. Without the use of this driver version, the BI Server cannot connect to Oracle TimesTen.
Parent topic: Troubleshooting the Highly Available Deployment
After you use the Client Installer to install the Oracle BI Administration Tool on a Windows computer, you might notice that the Administration Tool displays an error message such as the following:
Unable to load Times Ten Driver ttclient.dll.
This error message indicates that you cannot use the ODBC drivers in Oracle TimesTen to import metadata from a physical table source for Oracle TimesTen. To resolve this issue, set the TIMESTEN_DLL environment variable to point explicitly to the driver location for Oracle TimesTen, as shown in the following example:
set TIMESTEN_DLL=C:\TimesTen\tt1122_32\bin\ttclient1122.dll
Parent topic: Troubleshooting the Highly Available Deployment
If the BI Server does not fail over to the second Oracle TimesTen instance on the scaled-out node, then ensure that the logical table source (LTS) for the repository has mapped both the physical data sources for Oracle TimesTen. This mapping ensures that at the logical table source level, a mapping exists to both instances of Oracle TimesTen. If one instance of Oracle TimesTen is not available, then failover logic for the BI Server at the DSN level tries to connect to the other instance of Oracle TimesTen.
Parent topic: Troubleshooting the Highly Available Deployment
You might notice that aggregates that were created on the first instance of Oracle TimesTen are not available on the second instance of Oracle TimesTen. Keep in mind that no automatic replication exists between the Oracle TimesTen instances in the scaled-out deployment. The two instances are distinct and run on different computers but have the same deployed data stores. If you create aggregates using SQL scripts from Oracle BI Summary Advisor or the Aggregate Persistence Wizard on one instance of Oracle TimesTen, then you must manually create the same aggregates on the second instance of Oracle TimesTen. You must ensure that you keep the two instances of Oracle TimesTen synchronized. For information, see "Life Cycle Use Cases for Aggregate Persistence" in Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
Parent topic: Troubleshooting the Highly Available Deployment