Announcement

Collapse

http://progeeking.com

See more
See less

How To Reconfigure the Enterprise Manager 13c Cloud Control OMS after Migrating Repository Database

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • How To Reconfigure the Enterprise Manager 13c Cloud Control OMS after Migrating Repository Database

    We had a task to move the OEM13c repo DB (12.1 on Windows server) to a new server, even though it looks like standard change and there is metalink note for 12c (Doc ID 1514319.1) there were some steps missing (most probably because the note is for 12c?!):

    So we began:
    1. Stop OMS and BIP , leave the Admin server up:

    Code:
    <OMS HOME>/bin>./emctl stop oms
    <OMS HOME>/bin>./emctl stop oms -bip_only
    2. Move the repo DB the a new server (we did clone it).

    3. Run the command below to update the connect descriptor in the OMS configuration (please note the double quotation marks, as the single ones did not work for us!!!):

    Code:
     <OMS_HOME>/bin>./emctl config oms -store_repos_details -repos_conndesc
     "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=new host .oracle.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDI CATED)(SERVICE_NAME=EMREP)))" -repos_user sysman
    Oracle Enterprise Manager Cloud Control 13c Release 1
    Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
    Enter Repository User's Password :
    Successfully updated datasources and stored repository details in Credential Store.
    If there are multiple OMSs in this environment, run this store_repos_details command on all of them.
    And finally, restart all the OMSs using 'emctl stop oms -all' and 'emctl start oms'.
    It is also necessary to restart the BI Publisher Managed Serve
    r.

    Code:
    E:\oracle\Middleware\bin>emctl config oms -list_repos_details
    Oracle Enterprise Manager Cloud Control 13c Release 1
    Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
    Repository Connect Descriptor : (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=newhost. oracle.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDIC ATED)(SERVICE_NAME=EMREP)))
    Repository User : sysman
    So far so good, but we had problems at the next step:

    5. Stop the Admin server and then start the OMS and check the status

    Code:
    <OMS HOME>/bin>./emctl stop oms -all -force
    <OMS HOME>/bin>./emctl start oms
    Oracle Enterprise Manager Cloud Control 13c Release 1
    Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
    Windows service OracleManagementServer_EMGC_OMS1_1 failed to be started
    Oracle Management Server is Down
    JVMD Engine is Down
    Please check E:/oracle/gc_inst/em/EMGC_OMS1\sysman\log\emctl.log for error details
    Starting BI Publisher Server ...
    BI Publisher Server Could Not Be Started. Check BIP Server log file for details.
    BI Publisher Server Logs: E:\oracle\gc_inst\user_projects\domains\GCDomain\s ervers\BIP/logs/
    AdminServer Could Not Be Started
    Check Admin Server log file for details: E:\oracle\gc_inst\user_projects\domains\GCDomain\s ervers\EMGC_ADMINSERVER\logs\EMGC_ADMINSERVER.out
    
    BI Publisher Server is Down
    It turned out that the admin server is still referring to the old DB?!
    So after some searching on the net the puzzle started to unravel:

    You need to go to E:\oracle\gc_inst\user_projects\domains\GCDomain\c onfig\fmwconfig
    and update the connect string in: jps-config.xml , jps-config-jse.xml, embi-policystoremerge-jpscfg.xml

    Also check if the data source xml files under E:\oracle\gc_inst\user_projects\domains\GCDomain\c onfig\jdbc have been updated!
    Next step is you go to E:\oracle\gc_inst\em\EMGC_OMS1\sysman\ocm and update the emoms.properties files with the new connect descriptor because the em app won`t start up!
    I have updated it at one more place E:\oracle\gc_inst\em\EMGC_OMS1\sysman\config\opss_ 2018_07_05_09_49_01_624 emgc-mergejps-oracle.sysman.empa-2018_07_05_09_49_01_624.xml (not sure if needed by the em)

    Once everything was completed we tried it again, but it turned out that the update on connect descriptor in OMS config is still pointing to the old DB server!!!
    So we had to update it again:
    Code:
    <OMS_HOME>/bin>./emctl config oms -store_repos_details -repos_conndesc
     "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=new host .oracle.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDI CATED)(SERVICE_NAME=EMREP)))" -repos_user sysman
    After that point everything worked out:
    Code:
    <OMS HOME>/bin>./emctl stop oms -all -force
    <OMS HOME>/bin>./emctl start oms
    <OMS HOME>/bin>./emctl status oms -details
    <OMS HOME>/bin>./emctl config oms -list_repos_details
    6. Login to OEM 13c
    Go to Setup -> Manage cloud control -> Repository -> Expand OMS and Repository -> Target Setup -> Monitoring configuration - update the connect descriptor


    Last edited by pepone; 30-10-2018, 15:25.
Working...
X