Software Library, Patching, and Provisioning - Expert Oracle Enterprise Manager 12c - page 225

Figure 6-53. Patching roles located under Security
Let's take a look at these roles as defined for patching:
EM_PATCH_ADMINISTRATOR : This is the role for creating, editing, deploying, deleting,
and granting privileges for any patch plan in Enterprise Manager. This role can also grant
privileges to other administrators after creating them. This is a full privilege access role
to any patch plan and template within Enterprise Manager. This role should be given out on
a limited basis.
EM_PATCH_DESIGNER : This role can create and view any patch plan. This role is normally
used in the identification of patches across the patching lifecycle (development, testing,
and production). This role would be assigned to a senior DBA in an organization. This role
has the ability to create patch plans and templates and grant privileges to those plans to
EM_PATCH_OPERATORS .
EM_PATCH_OPERATORS : This is a role for deploying patch plans. This role is very limited in
that is can only deploy patch plans. It has no privileges to create or modify any patch plans
or templates. This role is ideal for junior DBAs of an organization.
These new patching roles enable administrators to provide a division of work between many layers
of a department while making sure that patches are applied on a consistent schedule.
Provisioning
Provisioning is another important part of the lifecycle offered with Cloud Control. It allows us to provision database
options, such as single-instance Oracle databases and Oracle Real Application Cluster databases; extend or delete
nodes from Real Application Clusters, Oracle Real Application Clusters One; and upgrade single-instance databases
in an automated manner.
Overview of Database Provisioning
First, let's take a general look at database provisioning. Figure 6-54 shows the provisioning solution in a
hierarchical view.