Introduction
When you install for the first time the OAS (Oracle Analytic Servers), you start by setuping a response file : for example oracle_analytics_server.rsp
Then you install for example :
java -jar
/home/logiciel/..../OASOracle_Analytics_Server_Linux_6.4.0.jar -silent -responseFile /home/.../oracle_analytics_server.rsp -invPtrLoc /home/logiciel/..../oraInst.loc
The second step constists of configuring the OAS by using an other response file, for example oas_configuration.rsp
This file contains the connection string : CONNECT_STRING that allows the OAS to connect to the OMR database (OEM Repository).
We suppose that the OMR is setuped to be a standalone database hosted by the server SRERVE_A ==> CONNECT_STRING = SRERVE_A:1521:oem_sysman_service
Problem
If one day you :
case 1 : move your OMR to an other server SERVER_B
case 2 : or you convert OMR to a dataguard database between SERVER_A and SERVERB and switch you primary database to SERVER_B
At this moment : You can not connect with OAS to the OMR database.
For the case1, you have to change the connection to SERVER_B
For the case 2, the problem is that OAS can not connect to a database with a connection with failover mode :
(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=SERVER_A)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)
(HOST=SERVER_B)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=oem_sysman_service))(FAILOVER_MODE=(TYPE=select)(METHOD=basic)))
Solution
To solve the 2 problems :
- use the MOS note : How To Change Your Oracle Analytics Connections When You Have Moved Your RCU Database To A New Host (Doc ID 2802991.1)
- use a VIP or DNS address to connect to the server where the OMR database is UP (Primary) in case of dataguard.
For example in the case of dataguard, we suppose that the DNS is DNS_A_B
we can change the file /home/.../oasmw/BI/config/fmwconfig/jps-config.xml as :
<property name="jdbc.url" value="jdbc:oracle:thin:@//DNS_A_B:1521/oem_sysman_service"/>
...
