Tuesday 24 July 2012

OBIEE 11g6: Relocation of OBIEE MetaData Repository Database in Weblogic

There will be cases where you will have to relocate or point your OBIEE 11g Metadata repository to another system and update the appropriate OBIEE's settings so your BI and scheduler services are back in operation.

Here lets take a scenario where your current Metadata is stored in an Oracle 11g database on a Windows system with ip-address :10.0.0.3, we now have to relocate or point our existing OBIEE installation which exists on a linux system with ip-address 10.0.0.2 to the new Metadata repository location to a Windows system with ip-address: 10.0.0.4.

  1. First we would need to login into our Linux system where the OBIEE is installed and update the Oracle DB Client installation which contains the tnsnames.ora file and update it to point our OBIEE to 10.0.0.4 as show below:
    [srikanth]$ cd $TNS_ADMIN
    [srikanth]$ pwd

    /home/srikanth/app/srikanth/product/11.2.0/client_1/network/admin
    [srikanth]$ vi tnsnames.ora
  2. Make sure the below exists in tnsnames.ora which points to the new Metadata repository on 10.0.0.4 system:
    XE =    (DESCRIPTION =      (ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.0.4)(PORT = 1521))      (CONNECT_DATA =        (SERVER = DEDICATED)        (SERVICE_NAME = XE)      )    )  
  3. Now start the Weblogic Server and change JDBC connection strings as below:
  4. First start your nodemanager using startNodeManager.sh script
    [srikanth]$ pwd
    /home/srikanth/OracleFMW/wlserver_10.3/server/bin
    [srikanth]$ ./startNodeManager.sh &
  5. Then goto the startWeblogic.sh script location to start the weblogic server
    [srikanth]$ pwd
    /home/srikanth/OracleFMW/user_projects/domains/bifoundation_domain/bin
    [srikanth]$ ./startWebLogic.sh
  6. Open your web browser and enter the URL: http://localhost:7001/console and login is as "weblogic" user.



  7. Goto  the "Services" -> "Data Sources" in the left "Domain Structure" pane.
  8. click on the "bip_datasource" link under the "Data Souces" pane.



  9. Select the "Connection Pool" tab and then click on the "Lock & Edit" button under the "Change Center" pane.
  10. Change the ip-address from the old metadata repository location to the new metadata repository location that is : 10.0.0.4 and click the "Save" button.
  11. Click on the "Activate Changes" button once it is shown.



  12. Next goto the "Services" -> "Data Sources" -> "EPMSystemRegistry" link and select the "Connection Pool" tab.
  13. Click on the "Lock & Edit" button under the "Change Center" pane.
  14. Change the ip-address from the old metadata repository location to the new metadata repository location that is : 10.0.0.4 and click the "Save" button.
  15. Click on the "Activate Changes" button once it is shown.



  16. Next goto the "Services" -> "Data Sources" -> "mds-owsm" link and select the "Connection Pool" tab.
  17. Click on the "Lock & Edit" button under the "Change Center" pane.
  18. Change the ip-address from the old metadata repository location to the new metadata repository location that is : 10.0.0.4 and click the "Save" button.
  19. Click on the "Activate Changes" button once it is shown.



  20. We would now need to update the "coreapplication" settings through the EM.
  21. Open a web browser and enter the URL:  http://localhost:7001/em and login with user "weblogic".
  22. Goto the "Farm_bifoundation_domain" -> "Business Intelligence" -> "coreapplication" folder in the left pane.
  23. Select the "Scheduler" tab and update the ip-address to the new location i.e: 10.0.0.4.
  24. Click the "Apply" button.



  25. Then click the "Activate Changes" button.
  26. Then click the "Close" button on the "Confirmation" window.



  27. Now we would need to stop and restart all the "Admin Server" and "Managed Servers" in order the changes to take effect.
  28. To stop all the services use below:
    [srikanth]$ pwd
    /home/srikanth/OracleFMW/user_projects/domains/bifoundation_domain/bin
    [srikanth]$ ./stopManagedWebLogic.sh bi_server1
    [srikanth]$ pwd
    /home/srikanth/OracleFMW/user_projects/domains/bifoundation_domain/bin
    [srikanth]$ ./stopWebLogic.sh

  29. To start the services again user the below:
    [srikanth]$ pwd
    /home/srikanth/OracleFMW/user_projects/domains/bifoundation_domain/bin
    [srikanth]$ ./startWebLogic.sh
    [srikanth]$ pwd

    /home/srikanth/OracleFMW/user_projects/domains/bifoundation_domain/bin
    [srikanth]$ ./startManagedWebLogic.sh bi_server1
    [srikanth]$ pwd

    /home/srikanth/OracleFMW/instances/instance1/bin
    [srikanth]$ ./opmnctl startall
    opmnctl startall: starting opmn and all managed processes...

  30. We can check that all the services up and running by using the below command:
    [srikanth]$ ./opmnctl status


Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status 
---------------------------------+--------------------+---------+---------
coreapplication_obiccs1          | OracleBIClusterCo~ |    7289 | Alive  
coreapplication_obisch1          | OracleBIScheduler~ |    7287 | Alive  
coreapplication_obijh1           | OracleBIJavaHostC~ |    7288 | Alive  
coreapplication_obips1           | OracleBIPresentat~ |    7285 | Alive  
coreapplication_obis1            | OracleBIServerCom~ |    7286 | Alive

Note:
You may check the scheduler logs to figure out if a problem is there in bringing up the scheduler service at the location e.g:
/home/srikanth/OracleFMW/instances/instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1/console~coreapplication_obisch1~1.log

Search for "Exception" to figure out the problem.

Summary:
By making sure that where ever there is a mention of the old ip-address of the metadata repository location that would need to be updated in all the places.
Most of these exist by doing a little searching in both the Weblogic console and the Enterprise Manager console.

No comments:

Post a Comment