Database Reference
In-Depth Information
Patching with the EM CLI Clients
Patching can be performed by utilizing deployment procedures from the command-line interface as completely as
it can be performed via the Enterprise Manager console. Patching is performed in conjunction with a properties file,
which includes the inputs to ease commands and offers the information the EM CLI requires to complete the patching
process. It's important to remember that EM CLI is not an agent like the regular EM agent on each host; it is a utility
that installs as client software.
To create a properties file from scratch, you need to know how and when to create one, using one of the
following steps:
•
from a template from an existing procedure
•
using a properties file in its current state, created via the console
•
re-using a saved properties file from a previous execution
Creating a Properties File from a Template
Using an existing procedure GUID, a template can be built with just a few commands and values inserted for the new
procedure that you want to execute.
Then perform the execution of the EM CLI command to pull info about the procedure templates available.
For our example below, we are going to pull patching template examples:
./emcli get_procedures -type=PatchOracleSoftware
CF9D698E8D3843B9E043200B14ACB8B3, PatchOracleSoftware, CLONE_PATCH_SIDB, Clone and Patch Oracle
Database, 12.2, ORACLE
CF9D698E8D4743B9E043200B14ACB8B3, PatchOracleSoftware, PATCH_ALL_NODES_CLUSTER_ASM, Patch Oracle
Cluster ASM - All Nodes, 12.2, ORACLE
The first information returned is the procedure GUID that we require to then create our properties file from
which to work:
./emcli describe_procedure_input -procedure=CF9D698E8D3843B9E043200B14ACB8B3
> Patch_template.properties
Verifying parameters ...
And your template file is now created:
-rw-r--r-- 1 oracle dba 65950 Jan 27 19:12 Patch_template.properties
Patching Remote Client Installations
If you have EM CLI clients deployed to target servers, it is simple to track them by registering them with the OMS as
part of the EM CLI setup. Tracking information is retained in the OMS on all EM CLI client installation binaries that
require patching. It will also identify EM CLI installations that need to be updated with new passwords or synced with
new verbs from the OMS repository. Client software installations are not targets in OEM, so they are not tracked or
monitored by the EM agents.
Search WWH ::
Custom Search