Friday, 27 October 2017

Oracle Enterprise Manager Cloud Control 12c Post-Installation Setup Tasks

◉ Setup Software Library


Create a directory to use as the software library.

$ mkdir -p /u01/app/oracle/oms12cr2/software_library

Navigate to the "Software Library: Administration" screen using the menu at the top-right of the screen (Setup > Provisioning and Patching > Software Library).

Select the storage type of "OMS Agent Filesystem".

Click the "Add +" button.

Enter a name and use the lookup buttons to select the local agent and location on the file system for the software library. Once you've selected the appropriate values, click the "OK" button.

The software library is now configured.

◉ Set My Oracle Support (MOS) Credentials


Navigate to the "My Oracle Support Preferred Credentials" screen using the menu at the top-right of the screen (Setup > My Oracle Support > Set Credentials...).

Enter the credentials and click the "Apply" button.

◉ Download Additional Agents


Navigate to the "Self Update" screen using the menu at the top-right of the screen (Setup > Extensibility > Self Update).

Click on the "Check Updates" button and "OK" on the subsequent message dialog.

Click on the "Agent Software" link.

Highlight the agent of interest and click the "Download" button. Select the download schedule and click the "Select" button. Click the "OK" button on the confirmation dialog.

Click the refresh button on the top-right of the screen until the download is complete and the status changes to "Downloaded".

Highlight the newly downloaded software and click the "Apply" button, followed by the "OK" button on the two following message dialogs.

When the status changes to "Applied", the agent software is ready for installation on a target.

◉ Install an Agent on a Target Host


Navigate to the "Add Targets Manually" screen using the menu at the top-right of the screen (Setup > Add Target > Add Targets Manually).

Accept the "Add Host Targets" option by clicking the "Add Host..." button.

Click the "Add +" button.

Enter the host and platform, then click the "Next" button.

Enter the installation details and click the "Next" button.

Installation Base Directory  : /u01/app/oracle/agent12c
Instance Directory           : /u01/app/oracle/agent12c/agent_inst (default)
Named Credential      : (click the "+" button and add the credentials of the "oracle" user)
Privileged Delegation Setting: (leave blank)
Port                         : 3872

If you are installing the agent on a HP Service Guard package, remember to set the "Additional Parameters" to point at the package-specific inventory location and override the machine name with the package name. For example.

INVENTORY_LOCATION=/u07/app/oraInventory ORACLE_HOSTNAME=my-package.example.com

Check the information on the review screen and click the "Deploy Agent" button.

Wait while the installation takes place. The "Add Host Status" page refreshes every 30 seconds.

When the installation completes, run the specified "root.sh" script and click the "Done" button.

The host will now be visible on the "Targets > Hosts" screen.

◉ Discover Targets on Host


Navigate to the "Add Targets Manually" screen using the menu at the top-right of the screen (Setup > Add Target > Add Targets Manually).

Select the "Add Non-Host Targets Using Guided Process (Also Adds Related Targets)" option, select the target types to be discovered (eg. Oracle Database, Listener and Automatic Storage Manager) and click the "Add Using guided Discovery..." button.

Enter the host name and click the "Continue" button.

Click the "Configure" icon for any discovered targets and enter the required details. If you are using HP Service Guard, remember to only select and configure targets belonging to the package. By default, the agent will discover all targets on the physical machine.

When all the configuration steps are complete, click the "Finish" button, followed by the "Save" button, then finally the "OK" button.

The targets will now be listed on the relevant target screen (Targets > Databases).

◉ Add Administrator Users


Navigate to the "Administrators" screen using the menu at the top-right of the screen (Setup > Security > Administrators).

Click the "Create" button.

Enter the username/password details and check the "Super Administrator" checkbox, then click the "Review" button.

Click the "Finish" button.

◉ Notifications


Setup and maintenance of notifications has changed considerably in Cloud Control 12c compared to previous versions of Grid Control. There are several areas to consider when configuring and diagnosing notification issues.

Make sure the SMTP server is registered in the "Setup > Notifications > Notification Methods" screen.

Check the "Setup > Incidents > Incident Rules" screen. Make sure the relevant incident rules are enabled. Create any new rules you need.

Subscribe to any rules you want to be notified about. To do this, highlight the rule, then do "Actions > Email > Subscribe Me".

Make sure your email is setup in the "Enterprise Manager Password & Email" screen, from the menu below your username on the top right of the screen.

◉ Plugin Patches


The following is an overview of the process for applying the 12.1.0.7 plugin patch to Cloud Control 12c (12.1.0.4).

Backup up everything! Database and file system.

Setup > Extensibility > Self Update

Download the latest versions of the plugins. The minimum you can really get away with is "Oracle Database 12.1.0.7", "Oracle Cloud Framework 12.1.0.2" and "Oracle Fusion Middleware 12.1.0.7". The Cloud Framework plugin is a dependency for the FWM plugin. Obviously, grab the extra plugins if you need them.

Setup > Extensibility > Plugins

Do a "Deploy On > Management Server" for the plugins you’ve downloaded. These require OMS downtime, so you will be monitoring progress using "./emctl status oms -details" from the "$OMS_HOME/bin" directory.

Wait until it is all running again.

Do a "Deploy On > Management Agent" for the DB and FMW plugins on just the cloud control server. I wanted to know it was all fine on this server before pushing out the updates to the agents on the monitored hosts.

Convince yourself nothing weird is happening.

Do a "Deploy On > Management Agent" for the DB plugin on any monitored database severs. Where possible I did Dev environments in one pass. Test environments in a second pass, then Prod environments.

Do a "Deploy On > Management Agent" for the FMW plugin on any monitored WebLogic severs. Once again, Dev, Test, Prod.