EM 12c, EM 13c: Patching a RAC DB via Fleet Maintenance in Enterprise Manager 12c Cloud Control with the Rolling Method Stops all RAC instances at Once (Doc ID 2266862.1)

Last updated on JULY 25, 2017

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.8.0 to 13.2.2.0.0 [Release 12.1 to 13.2]
Information in this document applies to any platform.

Symptoms

Enterprise Manager (EM) 12.1.0.5) Cloud Control
EM DB Plugin Bundle Patch 12.1.0.8.161031

Note: this symptom can apply to EM 13.1 and 13.2, also.


EM DB Plugin Bundle Patch 12.1.0.8.161031 is to be applied to a RAC database target via fleet maintenance with the rolling method.

The emcli command, however, stops the database services on all nodes in the cluster (which is not expected), instead of one at a time, in sequence (which is expected).

This emcli command is issued for one node of the cluster to initiate a rolling patch application (acme1.foo.com):

# Node1

 

The emcli command from the other node results in these similar entries in the "Copy required files from source to destination
Oracle" step of the patching procedure for each db:(note, again, the time stamps are almost simultaneous):

Tue Feb 21 18:47:27 2017 - Executing
command:"/ora01/app/oracle/product/12.1.0.2/bin/srvctl stop service -d DB1"
to stop services running from Oracle Home /ora01/app/oracle/product/12.1.0.2
Tue Feb 21 18:47:28 2017 - Executing
command:"/ora01/app/oracle/product/12.1.0.2/bin/srvctl stop service -d DB2"
to stop services running from Oracle Home /ora01/app/oracle/product/12.1.0.2

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms