Using Oracle Enterprise Manager Cloud Control with Database Classic Cloud Service

Oracle Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) includes Hybrid Cloud Management, which you can use to manage the Oracle Databases on Oracle Database Classic Cloud Service from the same management console that you use for your on-premises databases.

Oracle Enterprise Manager is Oracle’s integrated enterprise IT management product line, which provides the industry’s only complete, integrated and business-driven enterprise cloud management solution. Oracle Enterprise Manager 12c delivers comprehensive capabilities to manage, migrate, test, and deploy applications and workloads across hybrid clouds. See EM Hybrid Cloud Management for information about its hybrid cloud features.

To use the Hybrid Cloud Management feature to manage the Oracle Databases on Database Classic Cloud Service, you perform these high-level tasks:

Ensure that your on-premises Enterprise Manager Cloud Control Oracle Management Service (OMS) is of version 12.1.0.5, and that at least one 12.1.0.5 Management Agent exists in your enterprise.
Configure one or more version 12.1.0.5 Management Agents within your enterprise to act as Hybrid Cloud Gateway Agents, which provide an SSH-based communication channel between Database Classic Cloud Service compute nodes and the on-premises OMS.
Ensure that the Hybrid Cloud Gateway Agents and the on-premises OMS can communicate with the Database Classic Cloud Service compute nodes.
Deploy Management Agents to Database Classic Cloud Service compute nodes using the Add Host Targets Wizard or Enterprise Manager Command Line Interface.

For the detailed steps to perform these tasks, see Enabling Hybrid Cloud Management in Oracle Enterprise Manager Cloud Control Administrator's Guide, 12c Release 5 (12.1.0.5).

Preserving the Hybrid Cloud Agent Home When Patching a Database Classic Cloud Service Deployment

If you installed the Oracle Enterprise Manager Cloud Control agent under /u01/app/oracle (the Oracle Base directory) the agent home will be moved to /u01/app.ORG/oracle when a database patch is applied to the database deployment using the cloud tooling.

If the agent home has already been moved to /u01/app.ORG/oracle, you can copy it back to /u01/app/oracle to restore it.

Perform the following steps to configure the patching tools so that they do not move the agent home to /u01/app.ORG/oracle:

Connect to the compute node as the oracle user.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Create a file named /var/opt/oracle/patch/files_to_save.ora.
Add the full path of the agent directory to the /var/opt/oracle/patch/files_to_save.ora file.
Disconnect from the compute node, and then reconnect as the opc user.
Start a root-user command shell:
```
$ sudo -s
#
```

Edit the patching configuration file, /var/opt/oracle/patch/dbpatchm.cfg, and search for the following lines:

# create /var/opt/oracle/patch/files_to_save.ora with full path of directory or
# files to preserve any special files you may have in your /u01/app directory.
# set this to yes, if you have files_to_save.ora
special_files="no"

Change special_files="no" to special_files="yes".
Save and close the file.
Exit the root-user command shell and disconnect from the compute node.

After performing these steps, the agent home will be preserved in its original location whenever the database deployment is patched.