Oracle Management Service 13c Release 4 Update 2 (13.4.0.

2) System Patch
Patch for Bug# 31233849

Platform: Generic
Released: Jun 22 2020

This document describes how you can install a System patch on your Oracle
Mangement Service 13c Release 4 Update 2 (13.4.0.2). A System patch allows you to
patch complex systems (or) sub-systems in a more deterministic fashion with
proper automation. Technically, a System patch consists of sub-patches for
various sub-systems of a complex system. For OMS, the sub-systems are
represented as core and plugins. Starting with Enterprise Manager 13c, you can
use a single unified command called OMSPatcher for automating the process of
applying System patches on your OMS.

Sub Patches of the System Patch and the Bugs Fixed

------------------------------------------------------
The following sub-patches are installed as a part of the System patch:

31233849 - The connection to MOS/ARU no longer works

NOTE: It is a pre-requisite to apply Bug 31146297 on OMS before proceeding with

other steps.

Prerequisites
--------------
Before you install or deinstall the patch, ensure that you meet the following
requirements:

Note: In case of a multi-OMS environment, you need to perform steps 5 to 12 on

each of the OMS hosts.

1. Ensure that the Software Library is configured.

2. Ensure that the Oracle WebLogic Administration server that hosts the
OMS is up and running.
3. Ensure that the Oracle Database, which houses the Management
Repository and its listener are up and running.
4. Ensure that the Oracle Management Service (OMS) on which you are
installing the patch or from which you are rolling back the patch is Oracle
Management Service 13c Release 4 Update 2 (13.4.0.2).
5. Ensure that you have the latest version of OMSPatcher version 13.9.4.1.0
for Enterprise Manager 13.4.0.0.0 release. If you are not sure about the OMSPatcher
version you have, or to download the latest version, follow the instructions
outlined in the My Oracle Support note 2646080.1 available at:
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2646080.1
6. Ensure that you set the ORACLE_HOME environment variable to OMS core
home
7. Ensure that you set the PATH environment variable to include the
location of the unzip executable, and the <ORACLE_HOME>/bin and the
<ORACLE_HOME>/OMSPatcher directories present in the Oracle home of the OMS.
8. To use the OMSPatcher functionality, you must set the WebLogic
Administration Server credential access. To avoid setting the credentials
everytime, you can update the property file once with the necessary
information. To do so, see Section 9.1.
9. Maintain a location for storing the contents of the patch ZIP file. In
the rest of the document, this location (absolute path) is referred to as
<PATCH_TOP_DIR>.
10. Extract the contents of the patch ZIP file to the location you created
in Step (2). To do so, run the following command:
$ unzip -d <PATCH_TOP_DIR> p31233849_134000200430_Generic.zip
11. Ensure that you shut down the OMS by running the following command:
$ emctl stop oms

Note
In case of a multi-OMS environment, shut down all the OMSes.

12. Run the following command on each OMS instance home to ensure that you
do not have any issues with configuration, and binary prerequisite checks:
$ cd <PATCH_TOP_DIR>/31233849

While Installing a System patch

$ omspatcher apply -analyze -property_file <location of property file>

While Deinstalling a System patch

$ omspatcher rollback -analyze -id 31233849 -property_file <location of
property file>

Note
If the Analyze step fails on a Windows operating system, then check the log
files to see if there is a binary prerequisite failure due to
checkActiveFilesAndExecutables. For more information, see Oracle Enterprise
Manager Cloud Control Administrator's Guide.

Installing the System Patch

-------------------------------

To install the patch, follow these steps:

1. Navigate to the <PATCH_TOP_DIR>/31233849 directory:
$ cd <PATCH_TOP_DIR>/31233849
2. Install the patch by running the following command:
On Unix:
$ omspatcher apply -property_file <location of property file>
On Windows:
omspatcher apply -property_file <location of property file>

Note
For single OMS environment, omspatcher will run the patching steps.
For multi-OMS environments, omspatcher provides instructions that you need to
follow in your environment to complete the patching process.
For stand by OMS, omspatcher prints a list of steps that you need to perform
to complete the patching process. For more information, see Section 9.2.

3. Start the OMS by running the following command:

$ emctl start oms

Note : In case of a multi-OMS environment, you must start all the OMSes.

Deinstalling the System Patch

--------------------------------
To deinstall the patch, follow these steps:

1. Navigate to the <PATCH_TOP_DIR>/31233849 directory:

$ cd <PATCH_TOP_DIR>/31233849
2. Deinstall the patch by running the following command:
On Unix:
$ omspatcher rollback -id 31233849 -property_file <location of property
file>
On Windows:
omspatcher rollback -id 31233849 -property_file <location of property
file>

Note
For single OMS environment, omspatcher will run the patching steps.
For multi-OMS environment, omspatcher provides readme files in HTML or text
format, with a list of steps that you need to run in your environment to
complete the patching process.
For stand by OMS, omspatcher prints a list of steps that you need to perform
to complete the patching process.

3. Start the OMS by running the following command:

$ emctl start oms

Note: In case of a multi-OMS environment, you must start all the OMSes.

9 Appendix
----------------
The appendix contains the following topics:
Creating a Property File
Patching Principles for Standby OMS Configuration

Creating a Property File

---------------------------
The automated patching functionality achieved using OMSPatcher expects
WebLogic Administration Server URL and credentials as an input for patching
and configuration detection operations. Primarily, the WebLogic Administration
server is the host that manages the Managed Server where the OMS instance is
deployed. If you do not want to set the credentials every time you are
prompted while patching the OMS, you can update the property file. OMSPatcher
allows you to repeatedly provide the inputs using property file option.

Note
Property file for a Primary OMS and Standby OMS are different, as they are in
different domains.

Follow these steps to create a property file for OMSPatcher:

1. Run the following script to create the WebLogic encrypted

configuration and key files.
On Unix:
$ OMSPatcher/wlskeys/createkeys.sh -oh <full path of platform home>
-location <location to put the encrypted files>
On Windows:
OMSPatcher\wlskeys\createkeys.cmd -oh <full path of platform home>
-location <location to put the encrypted files>

When prompted, enter the credentials of the WebLogic Administration Server

that manages the Managed Server on which OMS instance is deployed. Two files
are generated with the file names: config and key.

2. Create the property file with the following entries:

AdminServerURL=t3s://<host address from where admin server is running>:<port
of the admin server>
AdminConfigFile=<'config' file location>
AdminKeyFile=<'key' file location>

Patching Principles for Standby OMS Configuration

---------------------------------------------------
There following are the different types of configurations principles in
standby setup:
Standby OMS - Replicating OMS, Software Library, and Repository Component
If a standby OMS is setup using a file system replication, then there is no
need to apply patch on standby setup separately. If you apply patches on the
primary OMS, then you must replicate the latest changes in the file system to
standby host either manually or using the automatic storage replication.

Note
If you follow this recommendation, you do not have to perform any of the
patching steps required for standby OMS using omspatcher.

For more information, see Enterprise Manager Disaster Recovery chapter in the
Oracle Enterprise Manager Administration guide.
Standby OMS Configured Along with Primary OMS System
When patches are applied on the primary OMS, they have to be applied on the
standby site Management Services too. Typically, the patches update the Oracle
home instances (using the omspatcher apply command), and optionally require
scripts to run on the Management Repository. On the standby site, it is
sufficient to update the Oracle Home instances (using omspatcher), and skip
the running of scripts on the Management Repository because database changes
are automatically propagated to the standby site using Data Guard. To achieve
this, use standby option with the commands omspatcher apply and omspatcher
rollback. For more information about these commands, see Section 7 and Section
8 sections in the Oracle Enterprise Manager Administration guide.