Usually, installing the ODA Plug-in is quite easy. You just run a Self Update, then you deploy the ODA Plug-in on the Management Server, and afterwards on the Agents of your ODA Bases.
However, not every company allows the OEM to be connected to the internet, mainly for security reasons. In that case, you have to do it manually.
The general steps are:
- Get the ODA Plugin from Oracle
- Copy it to your Management Server
- Import the opar file into your OMS
- Deploy it on your Management Server
- Deploy it on your ODA Bases
I have tried to find the ODA Plug-in on https://edelivery.oracle.com , but it was impossible for me to find it there. The best resource, for downloading OEM Plug-ins is from my point of view the following page:
The latest available ODA Plug-in is in the moment the one from the February 2016 (Version 184.108.40.206.0). Ok. Once we got it, we can copy it over to the Management Server, and import it there via the emcli interface. Make sure that you specify the full qualified path to your opar file.
$ ls -l *odba* -rw-r--r-- 1 oracle oinstall 7207397 May 16 10:35 220.127.116.11.0_oracle.dba.odba_2000_0.opar $ emcli login -username=sysman Enter password : Login successful $ emcli import_update -file=18.104.22.168.0_oracle.dba.odba_2000_0.opar –omslocal Unable to read the file 22.214.171.124.0_oracle.dba.odba_2000_0.opar. Verify the file path, and make sure it is the absolute path. In a multi-OMS setup, the request can be processed by any OMS, so make sure the file is available in a shared location and is accessible from the OMS that is processing the request. $ pwd /u01/app/oracle/stage/CC13C/Plugin $ emcli import_update -file=/u01/app/oracle/stage/CC13C/Plugin/126.96.36.199.0_oracle.dba.odba_2000_0.opar -omslocal Processing update: Plug-in - Enterprise Manager for Oracle Database Appliance provides comprehensive monitoring and management for Oracle Database Appliance and related targets. Successfully uploaded the update to Enterprise Manager. Use the Self Update Console to manage this update.
After the import has finished, we can login to the Gui and do the final steps there. From the OEM home page, open the Setup menu, select Extensibility and then Plug-ins.
Under Engineered Systems, select the Oracle Database Appliance and Deploy On and choose Management Servers.
Oracle recommends that you take a backup of the repository, and export the first management server configuration using the command “emctl exportconfig oms”. Otherwise, ensure that appropriate recovery plan is in place prior to deploying the plug-in.
$ emctl exportconfig oms [-sysman_pwd <sysman password>] [-dir <backup dir>] Specify directory to store backup file [-oms_only] Specify OMS-only backup on Admin Server host [-keep_host] Specify to backup hostname if no slb defined (Use this option only if recovery will be done on machine that responds to this hostname) $ emctl exportconfig oms -dir /u01/app/oracle/admin/oms/backup/ Oracle Enterprise Manager Cloud Control 13c Release 2 Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : ExportConfig started... Backup directory is /u01/app/oracle/admin/oms/backup Machine is Admin Server host. Performing Admin Server backup... Exporting emoms properties... Exporting secure properties... Export has determined that the OMS is not fronted by an SLB. The local hostname was NOT exported. The exported data can be imported on any host but resecure of all agents will be required. Please see the EM Advanced Configuration Guide for more details. Exporting configuration for pluggable modules... Preparing archive file... Backup has been written to file: /u01/app/oracle/admin/oms/backup/opf_ADMIN_20170518_032956.bka The export file contains sensitive data. You must keep it secure. ExportConfig completed successfully!
Ok. After the backup was done, it is time to deploy the Plug-in on the Management Server. Please be aware, that a deployment of plug-in on the Management Server requires downtime. All currently connected users will get automatically disconnected from Enterprise Manager. During downtime, users will not be able to connect to Enterprise Manager, and Enterprise Manager will not be able to monitor any targets.
HINT: In case you have an OMS Active/Active configuration, it will shutdown both OMS servers. Wait until both OMS servers are up and running before you continue with the next steps.
Just follow the wizard to complete the deployment. This step takes about 5 minutes, including stopping and restarting the OMS server. During the deployment use emctl status oms -details to check OMS status, and please wait until the OMS is up and running again, before continuing with the next steps.
Now it’s time to deploy it on the 13cR2 Agents. For the ODA Plug-in, to work correctly, you have to deploy them on the Agents which are running on the ODA Bases, and not on the Hypervisor or any other VM, in case you have a ODA in virtualized mode.
Pick your Agents on the ODA Bases
Click on Status to monitor it, or use the emcli get_plugin_deployment_status command line to do it. After the successful deployment of the ODA Plug-in, you can add your ODA targets via the guided process.
Ready, that’s it.
When you found the place to download the ODA Plug-in, it is not so complicated to install it, even without any internet connect from Cloud Control to MOS. Only take care, that a rollout of the Plug-in onto the management servers requires a downtime.