The sub-patches are intended for different sub-systems of a system that correspond with the OMS core and plug-in home organization.Ī typical System patch format is organized as follows:įor Enterprise Manager release 12.1.0.2 or below, OMSPatcher is not supported for the released one-off patches. Remote OMS: OMS instances on other machines (within the same OMS domain as the local OMS) where the administrator has not started any patching operations.īeginning with Enterprise Manager Release 12.1.0.3, Enterprise Manager patches have been converted to a System patch format in order to support patch automation.Ī System patch contains several sub-patches whose locations are determined by a file called bundle.xml in the top level directory of the patch. Local OMS: OMS instance on which the administrator runs OMSPatcher. The following terms are used:Īdministrator: Person installing patches to the OMS core and plug-in homes. The following figure illustrates a multi-OMS deployment.
Single Instance Database or Real Application Cluster - shared or Real Application Cluster (RAC) For both cases, administrator needs to follow the steps given by OMSPatcher.
For Windows, it only provides context-sensitive steps (text and HTML). OMSPatcher provides auto-generated bash scripts (one per OMS instance) for UNIX based systems. There is a one-to-one mapping between the managed servers and the separate OMS bits residing on a single machine. The OMSs are connected by the Oracle WebLogic domain and separate managed servers. Multiple OMS – OMS applications that run on two or more machines. OMSPatcher performs patching and deployment operations Single OMS – OMS application that runs from a single OMS instance of the system. 24.1.1 Supported OMS Configurations and OMSPatcher Patchability
0 kommentar(er)
