Cherry's blog: 13.5.0 Enterprise Manager Cloud Control

Overview of the Enterprise Manager Proactive Patch Program (Doc ID 822485.1)

List of patches:

OMS – RU 22

Patch 36335368: 13.5.0 Enterprise Manager Cloud Control Base Platform Monthly Release Update (RU) 22
Patch 19999993: OMSPatcher patch of version 13.9.5.20.0 for Enterprise Manager Cloud Control 13.5.0.0.0
Patch 28186730: OPATCH 13.9.4.2.15 FOR EM 13.5 AND FMW/WLS 12.2.1.4.0 and 14.1.1.0.0
Patch 35430934: MERGE REQUEST ON TOP OF 12.2.1.4.0 FOR BUGS 32720458 33607709
Patch 34153238: HTTPS PROXY CONFIGURATION IS NOT USED WHEN PROTOCOL IS CONFIGURED TO TCP
Patch 31657681: THREADS CONTEND FOR LOCK IN LOADFILEBASEDKEYSTORE WHEN OPENING TLS/SSL ENABLED JDBC CONNECTIONS

Agent – RU 22

Patch 36335371: Oracle Enterprise Manager 13c Release 5 Update 22 ( 13.5.0.22 ) for Oracle Management Agent
Patch 33355570: AgentPatcher release of version 13.9.5.8.0 for Enterprise Manager Cloud Control Agent 13.5.0.0.0

Notes:

Backup Database and Application before Patching
Apply OMS RU 22 before applying Agent RU 22
Apply OMSPatcher and OPatch the latest version before applying OMS RU 22
Apply Oracle Database to the latest version of Oracle Database 19c before applying OMS RU 22

Main steps:

Apply Oracle Database to the latest version of Oracle Database 19c
Apply OMSPatcher and Opatch to the latest version
Apply OMS RU 22
Apply Agent RU 22

A. Apply Oracle Database to the latest version of Oracle Database 19c

- With Fresh Installation, we should patch Oracle Database to the latest version during installation Oracle Database server.

B. Apply OMSPatcher and OPatch to the latest version

1. Apply OMSPatcher to the latest version

Ref: 13.5: How to Upgrade Enterprise Manager 13.5 Cloud Control OMSPatcher Utility to the Latest Version (Doc ID 2809842.1)

Get current version

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ cd $ORACLE_HOME

[oracle@monitor-app middleware]$ omspatcher version

OMSPatcher Version: 13.9.4.4.0

OPlan Version: 12.2.0.1.16

OsysModel build: Tue Apr 28 18:16:31 PDT 2020

OMSPatcher succeeded.

Patching to new version

[oracle@monitor-app middleware]$ mv OMSPatcher OMSPatcher.bak

[oracle@monitor-app ~]$ cd /source/monitor/patch/

[oracle@monitor-app patch]$ unzip p19999993_135000_Generic.zip -d $ORACLE_HOME

[oracle@monitor-app middleware]$ omspatcher version

OMSPatcher Version: 13.9.5.20.0

OPlan Version: 12.2.0.1.16

OsysModel build: Tue Apr 28 18:16:31 PDT 2020

OMSPatcher succeeded.

2. Apply Opatch to the latest version

Ref: EM 13c: How to Upgrade OPatch to the Latest Version on the Enterprise Manager 13.4 or 13.5 Cloud Control (Doc ID 2728285.1)

💩Pre-Installation Instructions

Ensure that the OMS is shutdown before upgrading the OPatch

For OMS:

[oracle@monitor-app ~]$ emctl status oms

[oracle@monitor-app ~]$ emctl status oms –details

[oracle@monitor-app ~]$ emctl stop oms -all

For Agent:

[oracle@monitor-app ~]$ . agent_env

[oracle@monitor-app ~]$ emctl status agent

[oracle@monitor-app ~]$ emctl stop agent

For Grafana:

[root@monitor-app ~]# systemctl stop grafana-server.service

Verify:

[oracle@monitor-app ~]$ ps -ef | grep oracle

💩Installation

Unzip this patch into your staging directory
Check current version

[oracle@monitor-app ~]$ opatch version

OPatch Version: 13.9.4.2.5

OPatch succeeded.

Install the software

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ $ORACLE_HOME/oracle_common/jdk/bin/java -jar /source/monitor/patch/6880880/opatch_generic.jar -silent oracle_home=$ORACLE_HOME

To validate the installation

[oracle@monitor-app ~]$ opatch version

OPatch Version: 13.9.4.2.15

OPatch succeeded.

💩Post-installation Instructions

Start the OMS

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ emctl start oms

[oracle@monitor-app ~]$ emctl status oms

Start Agent

[oracle@monitor-app ~]$ . agent_env

[oracle@monitor-app ~]$ emctl start agent

[oracle@monitor-app ~]$ emctl status agent

C. Apply the one-off patches

Notes: All of these patches listed above have the same installation.

Stop all servers (Admin Server and all Managed Server(s))

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ emctl stop oms –all

Unzip these patches in staging

[oracle@monitor-app patch]$ ls -la

…

drwxr-xr-x 4 oracle oinstall 48 Aug 13 2021 31657681

drwxr-xr-x 4 oracle oinstall 48 May 26 2023 34153238

drwxr-xr-x 4 oracle oinstall 48 May 26 2023 35430934

Apply the patches one by one

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ cd /source/monitor/patch/

[oracle@monitor-app patch]$ ls –la

[oracle@monitor-app patch]$ cd 35430934/

[oracle@monitor-app 35430934]$ opatch apply

[oracle@monitor-app patch]$ cd 34153238

[oracle@monitor-app 34153238]$ opatch apply

[oracle@monitor-app patch]$ cd 31657681

[oracle@monitor-app 31657681]$ opatch apply

Note: DO NOT START OMS because we will stop oms for patching in next step

D. Apply OMS RU 22

Ref:

13.5.0 Enterprise Manager Cloud Control Base Platform Monthly Release Update (RU) 22 (Doc ID 3023005.1)
How to Update Oracle Enterprise Manager from RU 13.5.0.16 to RU 13.5.0.20 | Vinicius DBA
Applying RU on Enterprise Manager 13c R5

Notes:

Ensure that the Oracle WebLogic Administration server that hosts the OMS is up and running
Ensure that the Oracle Database, which houses the Management Repository and its Listener, is up and running
To use the OMSPatcher functionality, you must set the WebLogic Administration Server credential access. To avoid setting the credentials every time, you can update the property file with the necessary information

Start the Oracle WebLogic Administration server

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ emctl start oms -admin_only

Oracle Enterprise Manager Cloud Control 13c Release 5

Starting Admin Server only...

Admin Server Successfully Started

Creating a Property File

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ $ORACLE_HOME/OMSPatcher/wlskeys/createkeys.sh -oh /u01/app/oracle/middleware -location /source/monitor/patch

The oraclehome passed is valid.

The wls url is t3s://monitor-app.taolaobidao.com:7102

Please enter weblogic admin server username : weblogic

Please enter weblogic admin server password :

The cfgFile is /source/monitor/patch/config

The keyFile is /source/monitor/patch/key

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Thu May 23 14:41:07 ICT 2024

Storing WLS User configuration

Admin url: t3s://monitor-app.taolaobidao.com:7102

Admin Config File: /source/monitor/patch/config

Key File : /source/monitor/patch/key

Please enter weblogic admin server username :

Enter Admin user's password:

Thu May 23 14:41:07 ICT 2024

Connecting to AdminServer

Connecting to t3s://monitor-app.taolaobidao.com:7102 with userid weblogic ...

Successfully connected to Admin Server "EMGC_ADMINSERVER" that belongs to domain "GCDomain".

Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key...

The username and password that were used for this WebLogic Server connection are stored in /source/monitor/patch/config and /source/monitor/patch/key.

Disconnected from weblogic server: EMGC_ADMINSERVER

****************** **********************88

User configuration file created: /source/monitor/patch/config

User key file created: /source/monitor/patch/key

'createkeys' succeeded.

[oracle@monitor-app patch]$ ls -la

…

-rw-r----- 1 oracle oinstall 233 May 23 14:41 config

-rw-r----- 1 oracle oinstall 80 May 23 14:41 key

[oracle@monitor-app patch]$ vi oem_ru22_property

AdminServerURL=t3s://monitor-app.taolaobidao.com:7102

AdminConfigFile=/source/monitor/patch/config

AdminKeyFile=/source/monitor/patch/key

[oracle@monitor-app patch]$ ls -la

…

-rw-r----- 1 oracle oinstall 233 May 23 14:41 config

-rw-r----- 1 oracle oinstall 80 May 23 14:41 key

-rw-r--r-- 1 oracle oinstall 133 May 23 14:46 oem_ru22_property

💩Installing the RU in Traditional Patching

[oracle@monitor-app ~]$ . oms_env

[oracle@monitor-app ~]$ cd /source/monitor/patch/36335368/

[oracle@monitor-app 36335368]$ omspatcher apply -analyze -property_file /source/monitor/patch/oem_ru22_property

[oracle@monitor-app 36335368]$ omspatcher apply -property_file /source/monitor/patch/oem_ru22_property

Check patching log:

[oracle@monitor-app 36335368]$ pwd

/u01/app/oracle/middleware/cfgtoollogs/omspatcher/36335368

[oracle@monitor-app 36335368]$ tail -f omspatcher_2024-05-23_14-58-54PM_apply.log

…

💀Verify the version

[oracle@monitor-app ~]$ omspatcher lspatches

…

oracle.sysman.si.oms.plugin/13.5.1.0.0 Plugin 36335368 36329196 Oracle Enterprise Manager for Systems Infrastructure 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service

…

oracle.sysman.emas.oms.plugin/13.5.1.0.0 Plugin 36335368 36329020 Oracle Enterprise Manager for Fusion Middleware 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service

…

[oracle@monitor-app ~]$ opatch lsinventory | grep 13.5.1.22

Patch description: "Oracle Enterprise Manager for Cloud Framework 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service"

Patch description: "Oracle Enterprise Manager for Systems Infrastructure 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service"

Patch description: "Oracle Enterprise Manager for Exadata 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service"

Patch description: "Oracle Enterprise Manager for Oracle Database 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service"

Patch description: "Oracle Enterprise Manager for Fusion Middleware 13c Release 5 Plug-in Update 22 (13.5.1.22) for Oracle Management Service"

Note:

Because of not using the “Online mode” for patching on OEM, so this step mentioned in the above note are not required.

E. Apply Agent RU 22

Apply Agent RU 22 includes 2 parts:

Update AgentPatcher utility in all servers running the agent.
Patching Oracle Enterprise Manager 13c Release 5 Update 22 ( 13.5.0.22 ) for Oracle Management Agent

1. Method 1 – Manually

Ref:

Enterprise Manager Cloud Control Management Agent 13.5 Release Update (RU) 5 Bug List (Doc ID 2854426.1)
13.5: How to Upgrade AgentPatcher to the Latest Version (Doc ID 2810322.1)

Main steps:

Copy patch p33355570_135000_Generic.zip, p36335371_135000_Generic.zip to server running the agent
Set environment parameters
Patching AgentPatcher
Patching OEM 13c R5 Update 22 (13.5.0.22) for Oracle Management Agent

[oracle@feelviewdb-standby ~]$ ls -l /soft/monitor/

total 266700

-rw-r--r-- 1 oracle oinstall 843331 May 16 15:23 p33355570_135000_Generic.zip

-rw-r--r-- 1 oracle oinstall 272256333 May 16 14:48 p36335371_135000_Generic.zip

[oracle@feelviewdb-standby ~]$ . agent13c

[oracle@feelviewdb-standby monitor]$ unzip p33355570_135000_Generic.zip -d $ORACLE_HOME

[oracle@feelviewdb-standby ~]$ agentpatcher version

[oracle@feelviewdb-standby ~]$ agentpatcher lspatches

[oracle@feelviewdb-standby monitor]$ unzip p36335371_135000_Generic.zip

[oracle@feelviewdb-standby ~]$ agentpatcher apply -analyze /soft/monitor/36335371/

[oracle@feelviewdb-standby ~]$ emctl stop agent

[oracle@feelviewdb-standby ~]$ agentpatcher apply /soft/monitor/36335371/

[oracle@feelviewdb-standby ~]$ emctl status agent

[oracle@feelviewdb-standby ~]$ agentpatcher lspatches

Note: Need to upload and refresh on console to validate installed patches

2. Method 2 – Using Patch Plans (Recommended)

Ref:

Because of the AgentPatcher will be updated automatically during patching RU 22, we create the Patch Plan for RU 22 with below steps:

Upload Patches: Enterprise > Provisioning and Patching > Saved Patches (inludes Patch Zip File and Patch Metadata)
Create Patch Plan: Enterprise > Provisioning and Patching > Patches and Updates > Search Patch