Category: OEM13c

How to Apply RU/RUR Patches onto Standalone Database using Fleet Maintenance in Oracle Enterprise Manager Cloud Control

Fleet maintenance uses the Out of Place Patching option with minimum downtime. Also this can be done only via emcli verb and there is no GUI option available.

This post demonstrates how to apply the latest Release Update DB July 2020 Release Update 19.8.0.0.200714   and  OJVM July 2020 Release Update 19.8.0.0.200714 onto standalone database.

Environment:

Primary Host/Database : oemnode1 / OEMREP
Standby Host/Database : stbnode1 / STBOEMREP
Current ORACLE_HOME   : /u01/app/oracle/product/19.0.0/dbhome_1
Referenced ORACLE_HOME: /u01/app/oracle/product/19.0.0/dbhome_2
REF_TARGET_NAME       : OraDB19Home2_8_oemnode1_8
New Out of Place ORACLE_HOME: /u01/app/oracle/product/19.0.0/dbhome_3

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

How to Apply Oracle Enterprise Manager 13c Release 4 Update 4 (13.4.0.4) for Oracle Management Service

This post demonstrates how to apply Enterprise Manager 13c Release 4 Update 4 (13.4.0.4) for Oracle Management Service.

The current latest OEM 13cR4( 13.4.0.0.0) Release Update ( RU ) is  “Oracle Enterprise Manager 13c Release 4 Update 4 (13.4.0.4) for Oracle Management Service”.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

After patching, start up the OMS by running the following command:

[oracle@oemnode1 ~]$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 4
Copyright (c) 1996, 2020 Oracle Corporation. All rights reserved.
Starting Oracle Management Server…
WebTier Successfully Started
Oracle Management Server Successfully Started
Oracle Management Server is Up
JVMD Engine is Up
Starting BI Publisher Server …
BI Publisher Server Already Started
BI Publisher Server is Up
[oracle@oemnode1 ~]$

Verify Patch Applied

[oracle@oemnode1 ~]$ $ORACLE_HOME/OPatch/opatch lspatches
[oracle@oemnode1 ~]$ omspatcher lspatches|grep 31459685

ORA-20411: Monitoring credentials not set for target

While promoting auto-discovered targets in OEM 13.4, the following errors occur:

“ORA-20411: Monitoring credentials not set for target name RACTESTDB target type rac_database set nameDBCredsMonitoring”

After testing monitoring user DBSNMP credentials , all works fine.

WORKAROUND

Remove the auto discovered targets, and manually add them into OEM again by :

Setup -> Add Target -> Add Targets Manually -> Add Using Guided Process

Apply Oracle Coherence Patch onto OMS

This post demonstrates how to apply an Oracle Coherence patch onto 13.4 OMS home.

First thing to do is to download Oracle Coherence 12.2.1.3.7 patch binary “p31030882_122130_Generic.zip”, and unzip it onto a staging area.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

How to Configure OMS to Connect to Repository Database with Standby Database

This post demonstrates how to configure database connection string for OMS to connect to repository database, which has a data guard standby database.  The purpose is to make sure OEM is still functioning after database has been switched or failed over to data guard physical standby database.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Restart all OMS

[oracle@oemnode1 ~]$ emctl stop oms -all
[oracle@oemnode1 ~]$ emctl start oms

Switch Over Repository Database to Standby Database

DGMGRL> show configuration;

Configuration - dg_oemrep

Protection Mode: MaxPerformance
Members:
oemrep - Primary database
stboemrep - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 27 seconds ago)
DGMGRL> switchover to stboemrep;
Performing switchover NOW, please wait...
Operation requires a connection to database "stboemrep"
Connecting ...
Connected to "STBOEMREP"
Connected as SYSDBA.
New primary database "stboemrep" is opening...
Operation requires start up of instance "OEMREP" on database "oemrep"
Starting instance "OEMREP"...
Connected to an idle instance.
ORACLE instance started.
Database mounted.
Connected to "OEMREP"
Switchover succeeded, new primary is "stboemrep"
DGMGRL>

Check and Confirm OEM 13c  is Still Working