Database Reference
In-Depth Information
A full coverage of target compliance is beyond the scope of this chapter. There are some basic concepts to get
you started, however. Oracle envisages that, in line with industry practice, you define a set of standard practices
(for example, that you will use Automatic Storage Management (ASM) for your database storage requirements, or that
database listeners won't use the default port of 1521). These are managed individually as compliance standard rules.
You then group a set of related rules into a corporate standard for, typically, a target type. So you might roll up your
ASM standard together with a standard that states you will not use bigfile tablespaces and one that requires locally
managed tablespaces with a uniform extent size into a Database Storage Standard. Finally, you can group related
standards into a compliance framework. In our example, we might create a storage standard as described earlier,
and a database password standard to comply with corporate password policy. These can then both be grouped
together to form a Database Compliance framework for your organization. As of this release, the standards and policy
rules are editable for your organization. In addition, Oracle ships several compliance frameworks with supporting
standards and rules.
■
this one change means that the compliance capability of enterprise Manager that was rarely used in previous
releases should now be on your to-investigate list.
Note
The rules, standards, and frameworks that you create form a Compliance Library. You can review this from the
Library link in the Compliance menu. Enterprise Manager then allows you to ensure compliance in two ways. First,
a compliance score is calculated as a weighted average of the results of evaluating your compliance standard rules
against a managed target. This score shows up on the target and enterprise home pages. Second, a compliance officer
can view target status interactively and use the Enterprise Manager reporting framework to maintain corporate
assurance that standards are being complied with, and that variations from standards are addressed, either by
corrective action or by documentation of the reasons for noncompliance.
The Enterprise menu's Provisioning and Patching option is the entry point to EM's provisioning and patching
capabilities. As those capabilities are covered in Chapter 6, we do not go into that functionality here.
The next item is called Quality Management, but this is, in my view, a misnomer. The submenu shown in
Figure
4-32
contains links to a variety of added-value options for the Database and WebLogic products. As these items
are separately licensed, we don't cover these in this introduction to the Enterprise Manager interface.
Figure 4-32.
Quality management
