Installing Oracle Enterprise Manager Cloud Control 13c Release 5 (13.5)

Installs Oracle Enterprise Manager Cloud Control 13.5: an existing 19c database is prepared as the Management Repository (the documented parameters, resetting the optimizer settings), a silent installation is done on the OMS server (on OL9 software only + RU + ConfigureGC), the Release Update is applied, agents are deployed to the target servers and the Oracle database (single instance, Oracle Restart or RAC) is brought under monitoring. The result is the https://<OMS>:7803/em console, agents uploading data and monitored database targets.

Topology: OMS server + repository database server (+ target servers to monitor)

Before you start

• The versions are supported in the EM 13.5 certification matrix (MOS → Certifications): for the OMS, …OL9/RHEL9 is supported only with 13.5 RU22 and later (MOS 3036957.1)…OL7/RHEL7 (7.9, UEK or RHCK)…OL8/RHEL8…; for the repository, 19c Enterprise Edition (with a current RU applied), PDB (or non-CDB).
• On the OMS server, em13500_linux64.bin and em13500_linux64-2.zip … em13500_linux64-5.zip (oracle.com/eDelivery) are together under …; the directory name contains no spaces.
• OMS: for …, at least 4 cores and 10 GB RAM (recommended: 16 GB), ~24 GB for the EM software + Software Library space, and 14 GB for the installation temporary directory (…). Repository server: RAM to cover SGA … MB + PGA … MB; …~110 GB…~335 GB…~460 GB… of disk for the MGMT tablespaces.
• The OMS server name … (FQDN) resolves forward and reverse in DNS and has a static IP; localhost resolves to 127.0.0.1. The name is at most 24 characters, letters/digits/hyphens/dots only.
• The repository database is dedicated to EM; in the 19c CDB the … PDB is open and the … service is registered with the listener. Supplemental logging is disabled (not supported on the repository). The SYS password is known and a password file exists (REMOTE_LOGIN_PASSWORDFILE = EXCLUSIVE/SHARED).
• The round-trip latency between the OMS and the repository is below 1 ms (same data center).
• The default ports are free on the OMS: 7803 (console HTTPS), 7788 (console HTTP), 4903 (agent upload HTTPS), 4889 (upload HTTP), 7102 (WebLogic Admin Server), 3872 (agent on the OMS). 4903/tcp is open from the targets to the OMS, and 3872/tcp from the OMS to the targets.
• The repository database can be backed up (if the installation fails halfway, the repository has to be cleaned up or restored); before starting the installation, take an RMAN backup or create a guaranteed restore point.
• The target server list contains all nodes of the cluster (… nodes entered); an agent is installed separately on each node, on local disk. Clusterware is running on the nodes and the olsnodes output matches the list.

Phases of the guide

• Repository database preparation — Check the current settings of the repository database · Set the EM repository parameters · Reset the hidden optimizer parameters · Check the redo log size · Restart the repository database · Prepare the tablespace directory …
• OMS server preparation — Update the system and install the preinstall RPM · Install the RPMs required by EM · Set the limits and kernel settings · Prepare the hostname and /etc/hosts · Create the directories · Open the EM ports in the firewall
• Enterprise Manager installation — Write new_install.rsp · Install EM 13.5 (silent…, software only…) · Run the root scripts · Update OMSPatcher (before configuration) · Apply the Release Update to the software only (bitonly) · Configure Enterprise Manager (ConfigureGC.sh)
• Post-installation and Release Update — Check the OMS status · Check the status of the agent on the OMS · Log in to the console · Update OMSPatcher (before the RU) · Run the pre-analysis for the Release Update (OMSPatcher) · Apply the 13.5 Release Update (OMS) …
• Agent deployment to the target servers — Download the agent image (emcli) · Copy the agent image to the targets · Target: agent directory and image extraction (…) · Target: install the agent (agentDeploy.sh, …) · Target: run the root.sh script (…) · Target: check the agent status (…)
• Adding the Oracle database as a target — Target: unlock the DBSNMP account · Add the database as a target (emcli) · …Discover and add the cluster and the RAC database…Discover and add the Oracle Restart database… (emcli discover_db) · Complete the monitoring settings