Database Reference
In-Depth Information
OMS_HOME/sysman/install
by specifying the
-PluginLocation
flag to select the location where the downloaded
plug-ins are kept. In the case of a Software Only installation, all patches previously applied will have to be redone.
After restoring the software homes, the next step would be to restore or re-create the OMS. This is done by using
the
omsca
utility and specifying the path of the backup generated by the
emctl exportconfig
command.
omsca recover -as -ms -nostart -backup_file <exportconfig file>
The steps required to recover the OMS may vary depending on whether an SLB is in use or multiple management
services are configured as well as whether recovery is done on the same host or a different host. The following steps
are required for restoring a single OMS on the same host without an SLB. The OMS instance will be recovered by using
the OMS configuration backup taken by
emctl exportconfig
.
1.
Clean up the failed host.
2.
Verify that the Software Library is available.
3.
Restore the software home by restoring a backup of the filesystem or run the installer's
Software Only option. (See the
Oracle Enterprise Manager Cloud Control Advanced
Installation and Configuration Guide Release 2
).
4.
Execute
omsca
in recovery mode and specify the location of the backup file taken
previously.
5.
Recover agents if necessary.
6.
Start the OMS.
7.
Verify that the OMS is working.
See the
Oracle Enterprise Manager Cloud Control 12c Administrator's Guide
for details on other OMS recovery
scenarios.
Management Agent Recovery
The recovery of the management agent requires reinstalling it, preferably from a reference install, or performing a
filesystem restore from a previous backup. The agent should be cloned with the existing patches and customizations.
The agent should also be installed by using the same port. After it has been reinstalled, a resynchronization should be
performed from the Agent Resynchronization page in Enterprise Manager Cloud Control.
■
the agent is blocked by the oMS after reinstallation to prevent targets from overwriting data from previous
configurations. use the resynchronize agent button to resynchronize and unblock the agent.
Note
Agent recovery in a typical scenario usually follows these steps:
1.
Remove the existing agent Oracle home by using the Oracle Universal Installer (OUI) to
clean up the inventory.
2.
Install a new agent or clone from the reference install, using the same port and path. The
filesystem can also be restored from a previous backup.
3.
Perform Agent Resynchronization from the Enterprise Manager Cloud Control Agent
home page.
