1. Cloud Control Database Lifecycle Management Administrator's Guide
  2. Manage Configuration, Compliance and Change Management
  3. Manage Configuration Information
  4. Comparisons

Comparisons

This section describes the template creation process and the use of rules in the process. It also provides information on setting up comparisons and managing comparison templates.

This section covers the following topics:

About Comparisons

Enterprise Configuration Management deals with the collection, storage, and monitoring of configuration data tied to managed entities within the enterprise. A host, for example, has configuration item types related to its hardware and software components—number of CPUs, memory, IO devices, OS platform and version, installed software products, and so forth.

Changes to configuration data invariably happen, typically because of common events like patches and upgrades. At some point a change to one component can affect the overall system in a negative way. Detecting the root cause becomes paramount.

Enterprise Manager provides the following types of comparisons:

  • Configuration drift

    Enables you to compare configurations of a target with configurations of another target of the same type.

  • Configuration consistency

    Reflects the changes of target members within a system. For example, you would use configuration consistency to ensure that the configuration parameters for all databases within a cluster database are the same

The comparisons can be done on the current configuration or on configurations previously saved (for example, just before applying a patch or doing an upgrade).

Comparisons allow you to:

  • Ignore certain attributes during a comparison. Define comparison templates to disregard unnecessary attributes.

  • Notify key personnel when differences are detected

  • Design and share comparison templates with other administrators

  • Compare complete target systems; match target system members automatically or manually

  • Compare configuration file data as raw file content or in a parsed format

Note that after you define and save comparisons, a change in configuration automatically starts a recomparison. If you have setup notifications, you will be notified of the changes.

About Comparison Templates

A comparison template is an exemplar for fine-tuning a comparison of like configurations. A template is associated with a specific target type, which determines the configuration item types, items, and properties to be compared. Oracle provides a set of default templates to support certain target types. A template enables you to establish specific settings to take into account when comparing configurations of the given target type; for example, which property differences to ignore, and which property differences trigger an alert. You also can use constraints to establish acceptable values for specific properties. A configuration being compared that does not comply with the constraint constitutes a difference.

A template can invoke rules, or expressions, to be evaluated in determining when there is a match for comparison purposes, and when to disregard differences detected in a comparison.

Templates can be used as is, or as a guideline. So, for example, you might decide that an existing comparison template, with just a few tweaks, can meet your requirements. Perhaps the template ignores property differences that you are concerned about. In this case, use the create-like feature to make the adjustments to an existing template and save it under another name.

For systems, you design a system template that references member templates, based on the target types that make up the system. Create the member templates before you create the system template.

About One-Time Comparisons

One-time comparisons are used to immediately view the differences between target configurations. One-time comparisons differ from drift and consistency comparisons in that the comparison is only evaluated once, even if you choose to save the results for later viewing.

If you are thinking of creating a drift or consistency comparison, consider creating a one-time comparison to verify that the initial drift or consistency evaluation will not result in immediate differences. Using the results, you can change the errant configuration values, or fine-tune your comparison template to ensure that only configuration items of interest are compared.

To perform a one-time comparison:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. In the One-Time Comparison section of the Dashboard page, click Create Comparison.

  3. Select Basic or Advanced comparison.

    • The Basic One-Time Comparison is a simple comparison between two or more targets. The fields are:

      • Reference Target (Current)

        Target against which the comparison is being made.

      • Comparison Template

        Template or pattern to be used for the comparison. This template can contain property settings, rules for matching configuration items, and rules for including and excluding configuration items.

    • The Advanced One-Time Comparison provides more options than the Basic One-Time Comparison. For example, you can use saved configurations and perform a consistency comparison within a system.

      The fields are:

      • Reference Target (Current)

        Target against which the comparison is being made. Use this option when comparing targets. Note that the list of the targets is restricted to 2,000. Use the Search option to restrict the list of targets.

      • Reference Target (Saved)

        Configuration that was created at an earlier time and which will be used as the base for the comparison. Use this option when you want to compare targets against your gold configuration.

      • Consistency Target Type (use for systems)

        When comparing systems, provide the type of system, for example, Cluster Database or Database System.

        Use this option to test the consistency of targets among systems. Note that all cluster members have the same saved configuration. For example, you can determine if all the configuration database parameters are the same within a cluster database.

      • Comparison Template

        Select a template that has gone through rigorous testing or use this one-time comparison to fine tune the comparison template to compare only what you need.

        An example of an existing template is one that you created or a template provided by Oracle. If you don't supply a template, there will be a one-to-one comparison between the fields in the reference target and the compared targets.

  4. Click Add to select targets or Add Saved to select saved configurations for the comparison. Remember that you can only compare targets of the same target type.

    Note that the more targets you add, the longer it will take for the compare operation to complete.

    After you have added the targets, and you decide to minimize the number of targets, on the Target menu, highlight the targets to eliminate and click Remove.

  5. Click OK. The comparison begins immediately and results are displayed on the Comparison Results page.

    Depending on the options you chose, it may take a while for the results to display. Click the Enterprise Manager Refresh button until the comparison is completed and the In Progress icon disappears. Click the i icon located by Comparison Results name for a listing of the options chosen for the comparison.

About Configuration Drift

Configuration drift ensures consistency (uniformity) across a large number of targets. For example, ensures that the configuration of the personnel database is the same across all the personnel databases throughout the company. This is particularly useful in this day and age of company acquisitions.

To perform a Drift Management Comparison:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. In the Drift Management section of the Dashboard page, click Create Definition.

  3. On the Compare Configurations dialog box, select the Target Type and Template. For example, select Database Instance and the template of choice, in this case Database Instance Template. Then, click OK.

On the Drift Definition page, provide the following information:

  • Definition Name - Make the name meaningful. The information from the Compare Configurations popup is replicated.

  • Source Configuration

    Select either Latest Configuration or Saved Configuration. Either one is the gold configuration against which the other targets will be compared. When using the Latest Configuration, choose the source target. When using the Saved Configuration, choose the appropriate configuration.

  • Advanced

    Expand this section to provide additional factors on the comparison.

    • Choose the severity of the drift. Options are: Minor Warning, Warning, and Critical.

    • Target Property Filter

      You can specify specific target properties that determine which targets this definition can work against. These properties are Operating System, Target Lifecycle State, Version, and Platform. When you specify a target property filter for this definition, for instance for Linux OS, it will only be applicable to targets on Linux Operating Systems.

    • Description

      Describe this drift definition and provide as much detail as possible. This information provides information for others who will be using this definition in the future.

    • Rationale

      Explain the reason for this comparison, for example: This content will detect configuration drifts for the targets.

    • Keywords

      Enables you to categorize this drift definition for quick reference.

After you have provided the information, select one of these options:

  • Save and Test Targets

    Once a target is associated with a comparison, comparisons are automatically triggered for that target when appropriate. For example, when the target's configuration changes, a comparison will be triggered, and if the automatic comparison results in a difference from the reference target, notifications will be sent, and the differences will be available in any reports for the drift comparison.

    Before associating targets with a comparison, you may want to run a test comparison. Configuration differences detected during a test comparison do not cause notifications to be sent, and will not appear in reports. The results from the test comparison can be used to verify that the comparison template is only comparing items of interest. Also, the test results can give a preliminary indication of how different a target is from the reference target. The Save and Test Targets option lets you run these test comparisons.

    To test targets, in the Test Targets page, clickAddto add a compared target. Select the target, and click Run Test. This will trigger a test comparison, and the number of differences generated will be placed in the Differences column of the table. To view the results of the test comparison, click on the difference count. Once you are satisfied with the comparison results, select the target and click Associate to permanently associate the target with the drift comparison, enabling automatic re-comparisons, notifications, and visibility of the target in reports.

  • Save and Associate Targets

    Saves the input, triggers automatic comparisons that use this comparison definition, and directs you to the Target Association for Drift Definition page.

    Click Add and select the targets you want to associate with this definition. Click OK. You will be prompted on whether you really want to save the associations.

  • Save and Return

    Saves the input for future use. You can view the saved comparison definition in the Definition Library tab of the Comparison & Drift Management dashboard.

    You are returned to the page from where the configuration drift was launched. For example, if you started from Drift Definition Library page, you will return to that page. If you started from the Overview tab, you will return to the Overview tab. If you started from the Drift Results page, you will return to the Drift Results page.

  • Cancel

    Aborts the operation. None of the input will be saved.

About Configuration Consistency

Configuration consistency reflects the changes of target members within a system or group. "For example, you would use configuration consistency to ensure that all of the database instances within a cluster database have the same configuration.

To perform a Consistency Management Comparison:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. Locate the Consistency Management section of the Dashboard Overview page. Click Create Definition.

    Note: You can create comparison definitions from several locations. You can create comparison definitions from:

    • Overview tab

    • Definition Library tab

    • Comparison Templates tab, after selecting a template

  3. On the popup, select the Target Type and Template. For example, select Cluster Database and the template of choice. The template can be one that you have defined, or as in this case, Cluster Database Template. Then click OK.

  4. On the Consistency Definition Details page, change the Definition Name as needed. The Compare Template and Applicable To information are replicated.

  5. Click Advanced to provide information which is used for compliance.

    • Compliance Standard Name is the same name as used for the Consistency Definition Name. This is the name to search for when using compliance standards.

    • Rule Name is the same name as the compliance standard name.

    • Compliance Rule State is automatically considered Production.

    • Choose the severity of the drift. Options are: Minor Warning, Warning, and Critical. When a consistency is in a Critical state, it needs to be addressed in a timely manner. For example, if the space on a database is getting very low, it needs to be addressed before it crashes.

    • Target Property Filter

      You can specify specific target properties that determine which targets this definition can work against when it is associated with a compliance standard. These properties are Operating System, Target Lifecycle State, Version, and Platform. When you specify a target property filter for this definition, for instance for Linux OS, it will only be applicable to targets on Linux Operating Systems.

    • Description

      Describe this consistency definition and provide as much detail as possible. This information provides information for others who will be using this definition in the future.

    • Rationale

      Explain the reason for this comparison, for example: This content will detect configuration consistency for the systems.

    • Keywords

      Enables you to categorize this consistency definition for quick reference.

  6. For consistency comparisons, Oracle chooses one target of each member target type as the reference target. All other members will be compared against the reference target of the same target type.

    Note: Since all members of the same type should be the same, it should not matter which target is selected as the reference target. However, if you would prefer to choose specific targets as reference targets, click the Edit icon in the Reference Targets when associating targets, or click the Reference Targets button when creating a one-time comparison. This allows you to choose your own reference targets for each member target type.

    After you have provided the information, select one of these options:

    • Save and Test Targets

      Saves the comparison definition which compares the members against reference members within the system. You can then run test comparisons to verify that the comparison template only compares attributes of interest to you.

      To review the results, click the number in the Differences column. The Comparison Results page appears.

    • Save and Associate Targets

      Saves the input and directs you to the Target Association for Consistency Definition page. Click Add and select the systems you want to associate with this definition. Click OK.

      Once the targets are associated with a comparison, comparisons are automatically triggered for the targets when appropriate. For example, when a target's configuration changes, a comparison will be triggered, and if the automatic comparison results in a difference from the reference target, notifications will be sent, and the differences will be seen in any reports for the consistency comparison.

    • Save and Return

      Saves the input for future use. You will be returned to the Comparison Dashboard.

    • Cancel

      Aborts the operation. None of the input will be saved.

About the Definition Library

The Definition Library is the repository for all the drift and consistency definitions created using the Comparison & Drift Management Dashboard.

To access the Definition Library, select Comparison & Drift Management from the Enterprise menu. On the Dashboard page, click the Definition Library.

From this page, you can:

  • Create a new definition

  • Edit an existing definition (as needed)

  • Run tests against a definition

  • Associate targets or groups to a definition (perform the association after you have verified test results from the Test Association page)

  • Delete a definition

Get Started Using Comparisons

This section describes how to create, edit, and otherwise manage comparisons and comparison templates.

Creating or Editing a Comparison Template

Use these instructions when creating a new template or editing an existing template; this includes create-like.

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management. Click the Templates tab.

  2. To search for a template, click Search. You can search for multiple target types from the target type list. Select the target types that you want to search for. You can also specify the Template Name, the name of the Owner, and specify if the template is a default template or an Oracle provided template. Click Search.

  3. Each template has a lock beside the template name. A closed lock represents an Oracle provided template. These templates cannot be edited. The templates that have an open lock are user defined comparison templates, and can be edited.

  4. For a new template, click Create and provide a name and target type. To base a template on an existing one, select the template row, click Create Like, and provide a name. In either case, the action creates a new template row.

  5. Select the appropriate template row in the table and click the Edit button. The Template Details page appears.

    The compared configurations' target type drives the hierarchy of configuration item types and configuration items on the left. The settings in play for the respective properties on the right derive from the selected template, unless you are creating a new template from scratch, in which case there are no settings.

    A system comparison takes an overall template and a template for each system member. Thus there is an additional tab for Member Settings. Edit the tab as follows:

    • Optionally select the member template to use for each system member type.

    • For any given member type, you can elect to compare configurations by checking the check box.

    • For member types that you are comparing, select a target property to use as a matching key. The default is target name, but typically you would want to use a distinguishable property to align comparison entities, such as department or location.

  6. To create or edit the comparison template for each member, select the Member Settings tab.

    You can choose to view the mapping display in a tree or table format. If you set the Mapping Display to Tree, the View mapping and Comparison results will display the system members in a hierarchical tree format. If you set the Mapping Display to Table, the View mapping and Comparison results will display the system members in a table format. You can edit the following:

    • Optionally select the member template to use for each system member type.

    • For any given member type, you can elect not to compare configurations by clearing the check box.

      Note:

      When you clear a check box for a system member, the children instances of the system member will automatically be ignored during the comparison that uses this template.

    • For member types that you are comparing, select a target property to use as a matching key. The default is target name, but typically you would want to use a distinguishable property to align comparison entities, such as department or location.

  7. In the Template Settings tab, select a configuration item type or item in the left pane to expose its properties in the right pane. A key icon denotes a property that is defined as a key column in the configuration item type's metadata.

    Tip:

    Notice the Compare check box column on the Template Settings tab. This is a powerful feature that enables you to streamline the comparison by selecting only those items you want to compare. When you select the check box, the comparison engine includes the corresponding configuration item type and all of its descendants.

    Contrast this with the ability to compare individual columns and rows on the Property Settings tab, in which the settings are stored as part of comparison results, giving you the option to view the compared properties on the results page.

    So, for example, in comparing host configurations, you may decide that any differences in CPU properties are immaterial. Simply expand the Hardware configuration item type and deselect the CPUs check box to exclude all properties associated with the item.

  8. Click the Property Settings tab and check boxes for property differences to be compared and alerted if different. They are mutually exclusive. When you compare differences in a property value in this fashion, you are doing so unconditionally for all differences detected in the property value for the configuration item type.

    Use a value constraint rule to filter the property value. In this case, the comparison engine compares the property value in the configurations being compared (the second through n configurations) to the constrained value. A property value that satisfies the constraint constitutes a difference. For example, test for a version equal to or greater than 6. Any instance in the compared configurations of a version property value under 6 constitutes a difference. Clearly, you would not set a value constraint if you checked compare differences. Specify a rule expression to set a value constraint. See Get Started Using Rules for details.

  9. Repeat the preceding steps to set additional property settings on other configuration items.

  10. Optionally, select an item in the left pane and click the Rules for Matching Configuration Items tab. For a given property, specify a rule expression to be evaluated to determine when a match exists between configuration instances. In other words, if the expression resolves to true, compare the instances. See Get Started Using Rules for details.

    Match rules are column-based; they apply an AND logical operator. If you specify rules for multiple properties, they must all resolve to true to constitute a match.

  11. Optionally, select an item in the left pane and click the Rules for Including or Excluding Configuration Items tab. For a given property, specify a rule expression to be evaluated:

    • Compare all - Compares everything in the configuration item.

    • Excludes items that match these rules - Compares everything except the properties listed.

    • Includes items that match these rules - Only compares the properties listed, that is, ignores everything else.

    The rules for including or excluding configuration items are row-based; they apply an AND logical operator within a subset of rules and an OR logical operator between rule subsets. So, if you specify two rules for property A and two rules for property B, either both rules set on property A OR both rules set on property B must resolve to true to constitute a match.

Set Up a Comparison Template

To set up a comparison template, follow these steps:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. On the left of the Dashboard page, click the Templates icon.

  3. On the Comparison Templates page, click Create to create a new template or Create Like to create a template similar to one that already exists. Using the Create Like option enables you to use existing templates and make minor changes as needed.

    Provide data for the Name and Target Type. When providing a name, make it obvious so folks can determine the reason for the template. For historical purposes, provide a description that explains the reasons and specifics of this template. When you provide the target type, configuration items for that target are automatically added to the template definition.

  4. After you create (or create like) the template, edit the template to delete or modify configuration items.

    When the Save Only Differences option is checked, only differences will be saved when this template is used in drift, consistency, and one time comparisons. If the box is not checked, then all information will be stored in the comparisons in which this template is a part.

    Note: When creating a system template, for example, a cluster database, the template page provides more information when there is a target with members like a Cluster Database.

  5. Compare Configurations: This option provides the same functionality as if you were on the Dashboard page and clicked Create Comparison for One-Time Comparison, Create Definition for Drift Management, or Create Definition for Consistency Management.

  6. After you associate targets to the comparison definition, the comparison will rerun automatically whenever there is a change to the configuration for a target, when the system members change, or when the template changes.

  7. If you choose Table for the Mapping Display, and do not override the default flat map when defining the comparison, the members of the systems will be matched for comparison without regard to their level in the system hierarchy. Thus, when viewing the results, the original system hierarchy cannot be retrieved.

    Chose the Table option only if you are not concerned about how the members of the system are related to each other.

Managing Comparison Templates

In addition to creating and editing comparison templates, you manage them by doing the following:

  • View a template's settings and composition; this is read-only

  • Delete a template (requires the proper permissions)

  • Share templates by exporting them in XML file format and importing them into other Cloud Control systems

Viewing a Comparison Template

You can view templates provided by Oracle and other users' templates to which you have access. Viewing a template is read-only: you see its makeup, but you cannot change anything, even temporarily.

  1. Select a template in the Comparison Templates page and click the View button.

  2. Expand items in the tree on the left and peruse the settings and rules on the various tabs.

Deleting a Comparison Template

Deleting a template is subject to the following constraints:

  • You cannot delete an Oracle provided template. An Oracle provided template is represented by a closed lock beside the template name.

  • You cannot delete a comparison template unless you have the proper permissions.

  • You cannot delete a default comparison template.

  • You cannot delete a comparison template currently in use.

To delete a template, select it in the Comparison Templates page, click Delete, and confirm the operation.

Exporting a Comparison Template

Use the export feature to save a template as an external file that can be imported into another Cloud Control system.

  1. Select a template in the Comparison Templates page, select the Actions menu and click Export.

    A platform-specific file dialog opens. For example, if you are using Firefox, the dialog notes that you have chosen to open the named template, which it identifies as an XML file. The dialog asks what you want Firefox to do, open the file in an XML editor or save the file.

  2. Select the save radio button and click OK.

  3. Browse to the desired location in the file system and save the file, changing the name if applicable. You cannot change the name of a template provided by Oracle on export.

Importing a Comparison Template

Any comparison template import must comply with the comparison template .xsd. So, for all intents and purposes, the import should be a previously exported template to ensure compliance.

  1. In the Comparison Templates page, select the Actions menu, and click Import.
  2. Browse to the template file location and click Import.

    The imported template appears as a new row in the template table.

An exported template is associated with its owner. A template whose owner is not the same as the login ID of the person importing the template retains its original ownership. If you want to be the owner of the imported template, you have to edit the owner attribute in the template XML file prior to import, changing the value to your login ID. Or, you can simply remove the attribute, in which case the default owner will be set to the ID of the person initiating the import operation.

The Template Manager disallows import of a template provided by Oracle of the same name. Similarly, you could change the name attribute in the template XML file prior to import to allow the import to occur.

Considerations Before Creating a Comparison

Comparisons are an important factor in managing the enterprise. Setting up a comparison involves the following steps:

  • Select the first configuration in the comparison (the one to compare against)

  • Select additional configurations (the one or more configurations to compare to the first configuration)

  • Select a comparison template to fine-tune the attributes being compared (or no template)

  • For system comparisons, map members as needed. It's a way to selectively indicate how members of respective systems should match up in a comparison.

  • Review your work

  • Set up email notification by setting up mail servers and then creating incident rules

  • Review BI Publisher Reports (From the Enterprise menu, select Reports, then select BI Publisher Reports.)

A follow-on step would be to review the results and drill down to differences details.

Set Up a Drift or Consistency Comparison

To create a drift or consistency comparison, follow these steps:

  1. Determine what configuration items you want to compare.
  2. Create a template or use an existing template.
  3. Create a definition of either a Configuration Drift or a Configuration Consistency.
  4. Perform the comparison.
  5. Set up email notification by setting up mail servers and then creating incident rules. See Create Notifications for Comparisons.
  6. View the results from the Comparison & Drift Management Drift Results tab or the Comparison & Drift Management Consistency Results tab. You can also view the results as a BI Report. To view BI Reports: from the Enterprise menu, select Reports, then select BI Publisher Reports.

Create Notifications for Comparisons

Get notified every time there is a comparison change by creating notifications.

There are two parts to set up notifications: setting up the mail servers and creating an incident rule.

Follow these steps to setup notifications:

  1. From the Setup menu, select Notifications, then select Mail Servers.

  2. On the Mail Servers page, provide the Server Identity information then add the outgoing mail (SMTP) server.

After you have set up the Mail Servers, set up the Incident Rules as follows:

  1. From the Setup menu, select Incidents then select Incident Rules.

  2. On the Incident Rules - All Enterprise Rules page, click Create Rule Set.

    Provide a name and description and apply the rule set to Targets. This should apply to All Targets.

  3. Create a rule as follows:

    1. Select - Incoming events and updates to events.

    2. Select - Specific events of type Compliance Standard Rule Violation.

    3. Select either Compliance Standard or Compliance Standard Rule. If selecting a Compliance Standard, select a standard of type Drift or Consistency. If selecting a Compliance Standard rule, select a rule of type Drift or Consistency.

    4. Add a rule - If you selected a compliance standard in the previous step, add a compliance standard of type Configuration Drift or Configuration Consistency. If you selected a compliance rule, select either a Configuration Drift Rule or a Configuration Consistency Rule.

    5. Add Actions - Basic Notifications (E-mail to). Enter the e-mail addresses of those who are to be notified when the comparison detects a difference. Use a comma to separate addresses. Remember that the properties for which differences are alerted were specifically selected in the comparison template.

    6. Click Next and specify rule name and description. Click Continue.

  4. Click Save.

Get Started Using Rules

Specify rules in the context of creating or editing a comparison template (see Creating or Editing a Comparison Template).

Rules enable you to parse configuration data in order to fine-tune comparisons. In terms of the comparison, a rule applies the expression to the value of the selected item in the configuration instance that is being compared to the benchmark configuration. Matching rules are intended to devise a comparison key that aligns the instances being compared. Ignore rules are intended to establish a basis for disregarding any differences detected between instances being compared.

To access the rules functionality, select Configuration from the Enterprise menu, then select Comparison & Drift Management. Click the Templates tab on the left. Select a template to edit and click Edit.

About Rules Expression and Syntax

A rule consists of an operator and operands. Taken together, they form an expression that resolves to a value that is then compared to the value of the selected item. A true condition satisfies the rule.

Operands can be literals (string literals are enclosed in single quotes), legal numbers, or dates of the form YYYY-MM-DD HH24:MI:SS.FF. Operands that directly reference the value of a configuration item must be of the same date type as that value. Operands in square brackets in the syntax are optional.

Operator Operands

is equal to*

An optional literal value to match; string values are case-sensitive; if unspecified, expression evaluates value of the property to which the rule applies

Note that a matching rule compares the values of the configuration items in the respective configuration to one another, not to a third specified value, so the operator does not take an operand in this case.

[match-literal]

is case-insensitive equal to*

An optional case-insensitive string literal; if unspecified, expression evaluates value of the property to which the rule applies

Note that a matching rule compares the values of the configuration items in the respective configuration to one another, not to a third specified value, so the operator does not take an operand in this case.

['match-literal']

is greater than or equal†

A literal value to match; required

match-literal

is greater than †

A literal value to match; required

match-literal

is less than or equal to†

A literal value to match; required

match-literal

is less than†

A literal value to match; required

match-literal

is one of†

A comma-separated list of literal values, at least one of which must be specified, but only one of which need match

match-literal-1[,match-literal-n,...]

is between†

A range specified as start and end literal values; both must be specified; range is inclusive

start-range-literal , end-range-literal

contains†

A string literal on which to perform pattern matching; required

[FALSE|TRUE,] 'pattern-literal'

FALSE (default) means string must comply with Oracle LIKE operator syntax; TRUE means string must comply with Posix regular expression syntax

replace‡

A string literal to match and replace with a second string literal

[FALSE|TRUE,]'pattern-literal'[,'replacement-literal'][,position-integer][,occurrence-integer]

FALSE (default) means string must comply with Oracle LIKE operator syntax; TRUE means string must comply with Posix regular expression syntax

TRUE enables optional positional integer argument to indicate where within the column value to extract the string, and optional occurrence integer argument to indicate the position count to replace

Mandatory pattern literal represents the string value to match

If the replacement string literal is unspecified, replace the matched string literal with nothing

substring‡

Extract specified segment of string value

[FALSE|TRUE,]position-integer[,length-integer][,'pattern-literal'[,occurrence-integer]]

FALSE (default) means string must comply with Oracle LIKE operator syntax; TRUE means string must comply with Posix regular expression syntax

Mandatory positional integer argument indicates where to begin string extraction:

  • If 0 or 1, returns all characters

  • If positive integer, starts extraction from beginning

  • If negative integer, starts extraction counting backwards from end

Optional length integer argument indicates character count starting at position integer

pattern literal represents the value to match; optional if the first argument is FALSE; required if TRUE

occurrence integer argument indicates character count to match; valid only if pattern literal is specified

Notations are as follows:

  • *–Enabled for value constraints, matching rules, and ignore rules
  • †–Enabled for value constraints and ignore rules only
  • ‡–Enabled for matching rules only

Create a Value Constraint Rule

Specify value constraint rules as follows:

  1. Select a configuration item in the left pane.

  2. Click the Property Settings tab in the right pane and select the property on which you want to set a value constraint.

    When the Property Settings tab is selected, keys are displayed in the column to the left of the Property Name.

  3. Click the Edit Rule button in the toolbar. In the dialog that opens:

    1. Select an operator from the drop-down list.

    2. Type an operands expression, then click OK. An operand is a value that you want to either include or exclude from the constraint. For example, if you want to exclude Patch ID 12,34,56,78, you would enter operand as '12', '34', '56', '78'.

    To clear a rule, select the table row and click the Remove Rule button in the toolbar.

    See About Rules Expression and Syntax for details on the formation of a rules expression.

Create a Matching Rule

Specify matching rules as follows:

  1. Select a configuration item in the left pane.

  2. Click the Rules for Matching Configuration Items tab in the right pane, then click New.

  3. Select a property in the drop-down list that appears under Property Name.

  4. To create the rule, select the table row and click the Edit Rule button in the toolbar. In the dialog that opens:

    1. Select an operator from the drop-down list.

    2. Type an operands expression, then click OK.

    3. To specify additional rules, click New and repeat Steps a and b

    To clear a rule, select the table row and click the Remove Rule button in the toolbar.

    For more information on the formation of a rule expressions, see About Rules Expression and Syntax.

    You can enter additional rules for the same or for a different configuration item. When there are multiple rules, they resolve in the order specified. Matching rules take an AND logical operator, which means all conditions must resolve to true to constitute a match.

Create a Rule for Including and Excluding Configuration Items

Specify ignore rules as follows:

  1. Select a configuration item in the left pane.

  2. Click the Rules for Including or Excluding Configuration Items tab in the right pane.

  3. Choose one of the following options: Compare all, Exclude those that satisfy rules, Include only those that satisfy rules. Click New.

  4. Select a property in the drop-down list that appears under Property Name.

  5. To create the rule, select the table row and click the Edit Rules button in the toolbar. In the dialog that opens:

    1. Select an operator from the drop-down list.

    2. Type an operands expression, then click OK.

    3. To specify additional rules, click New and repeat Steps a and b.

    To clear a rule, select the table row and click the Remove Rule button in the toolbar.

    See About Rules Expression and Syntax for details on the formation of a rules expression.

    You can enter additional rules for the same or for a different configuration item. When there are multiple rules, they resolve in the order specified. Including and Excluding rules take an AND logical operator for rules within a subset, and an OR logical operator between subsets. So, for two subsets, each with multiple rules, all rules in the first subset OR all rules in the second subset must resolve to true to constitute a match.

  6. Select New Or to indicate the end of one rule subset and the beginning of another.

Rule Examples

These rule examples assume that you are in the process of creating or editing a template and are at the point where you have selected the configuration item in the tree on the left.

Matching Rule Examples

Suppose, when comparing the hardware of host configurations, you want, for matching purposes, to ignore case in respective vendor names. Here's a simple rule to make the comparison case-insensitive.

  1. In the Rules for Matching Configuration Items tab, click New.

    Note: For this example, ensure you are using a Host target type template.

  2. Select Vendor Name in the drop-down list under Property Name.

  3. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to is-case-insensitive-equal-to. As this operator takes no operands for a matching rule, you are done.

    • Click OK.

Suppose you want to compare WebLogic Servers, aligning on server name, where the names are different: ManagedServer1 and ManagedServer2, for example. To ensure the comparison occurs, you need to fashion a match on server name.

  1. In the Template Settings tab, highlight Server Information.

  2. In the Rules for Matching Configuration Items tab, click New. In the Property Name drop-down list, select Machine Name.

  3. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to substring.

    • Set Operands to 1, 13.

    • Click OK.

    Effectively, the rule says use the first 13 characters of the name (ManagedServer), thus excluding the qualifying integer.

  4. Another way to achieve the same result:

    • Set Operator to replace.

    • Set Operands to true, '(*)(\d*)', '\1'.

    • Click OK.

    This example uses a regular expression (TRUE) to resolve all characters prior to the qualifying integer.

For a more advanced example, consider a database instance comparison that requires a match on Datafiles file names within a Tablespace, where file names are of the form:

/u01/jblack_abc2d/oracle/dbs/dabc2/mgmt_ad4j.dbf
  1. In the Template Settings tab, highlight the Control files configuration item.

    Note: For this example, ensure you are using a Database Instance target type template.

  2. In the Rules for Matching Configuration Items tab, click New.
  3. In the Property Name drop-down list, select File Name.
  4. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to replace.

    • Set Operands to true, '(/u01/)(.*)(oracle.*/dabc[0-9]+.*/)(.*)', '\2\4'.

    • Click OK.

Effectively, the rule says use a regular expression (TRUE) to construct a matching key from the value between /u01/ and oracle, combined with what remains of the original filename after dabc2 /, or jblack_abc2d/mgmt_ad4j.dbf.

Ignore Rule Examples

Generally, you use ignore rules to ignore differences in collections that are row-oriented, as opposed to column-oriented. Configuration extension snapshots, for example, are row-oriented data collections.

Say, for example, you wanted to ignore in configuration extension parsed data, any row where the property Attribute identifies an internal ID or checksum.

  1. In the Rules for Including or Excluding Configuration Items tab, click New.

  2. Select Attribute in the drop-down list.

  3. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to is one of.

    • Set Operands to 'id', 'checksum'.

    • Click OK.

The rule ensures that the comparison ignores any row in the collection data that contains either of the specified values.

Now consider an ignore rule that demonstrates how the comparison engine applies the logical operators AND and OR against the same configuration item type. In this example the objective is to ignore rows in configuration extension parsed data when any of three rule sets satisfies the following conditions:

  • Data Source = ‘sqlnet.ora' AND Attribute = ‘ADR_BASE'
  • OR
  • Data Source = ‘tnsnames.ora' AND Attribute = ‘HOST'
  • OR
  • Data Source = ‘resources.xml' AND Attribute = ‘authMechanismPreference'

Notice that the comparison engine applies the AND operator to rules within a set and the OR operator between rule sets. Rules for ignoring instances support inheritance; thus, in this case, the Data Source property is available in rules creation, as demonstrated in the example.

  1. In the Rules for Including or Excluding Configuration Items tab, click New.
  2. Select Data Source in the drop-down list.
  3. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to is equal to.

    • Set Operands to 'sqlnet.ora'.

    • Click OK.

  4. Click New and select Attribute in the drop-down list.
  5. Select the table row and click the Edit Rules button in the toolbar to open the rule dialog.

    • Set Operator to is equal to.

    • Set Operands to 'ADR_BASE'.

    • Click OK.

  6. Click New Or to insert a logical OR operator to signal the end of the first rule set.
  7. Add two new rules where Data Source is equal to 'tnsnames.ora' and Attribute is equal to 'HOST'.
  8. Click New Or to insert a logical OR operator to signal the end of the second rule set.
  9. Add two new rules where Data Source is equal to 'resources.xml' and Attribute is equal to 'authMechanismPreference'.

The comparison ignores any row in the collection data that satisfies any of the three rule sets.

Work with Comparison Results

This section covers comparison results from the following perspectives:

About Consistency Management (System) Comparison Results

Consistency results display when you click the Consistency Results tab on the Comparison & Drift Management Dashboard page. The view summarizes the results of all the consistency comparisons. Red signifies the number of inconsistent targets within the system, whereas green signifies the number of consistent targets within the system. To view the differences for a particular consistency definition, click the number of differences associated with the consistency definition. The Comparison Results page appears.

  • Select Only Differences in the Show drop-down list to eliminate the "noise" of the same results.

The icons that appear in the view are mostly intuitive: equal–same, not equal–different.

The table displays a hierarchy of system and member target types where:

  • The Target Type column displays the system and member tree hierarchy.

  • The Result column shows comparison results based on the mappings established as part of comparison setup. A boxed 1 (left only) or 2 (right only) means there was nothing to compare to the first or second member target, respectively. Note that if the parent target configurations are the same, but one or the other parent has child members marked as left only or right only, the parents are marked as different.

  • To resolve unmatched members, rerun the comparison, this time ensuring in the mapping step that the left and right member pairs appear in the mapped members table. Select an appropriate system comparison template with target matching rules defined, such that these members are mapped, or map the pairs manually.

  • When the Member column displays both an equal and a not equal icon, it indicates equality at the parent level, but a difference in some member.

  • To view a summary of all the differences found when comparing the system target and any member targets, click Export, located at the top of the table that displays the system members. An XLS report will be downloaded.

About Drift (Target) Comparison Results

Drift results display when you click the Drift Results tab on the Comparison & Drift Management Dashboard page. The view summarizes the results of all the drift comparisons. Red signifies how many targets have drifted from the gold standard, whereas green signifies how many targets are similar to the gold standard. To view the differences for a particular drift definition, click the number of differences associated with the drift definition. The Comparison Results page appears.

Simple Target (Non-System Target) Results

When a simple target (non-system target) comparison is completed, the left pane displays a hierarchy of configuration items for the target being compared, and, if applicable, configuration extensions. Refine the scope comparison results as follows:

  • Select Only Differences in the Show drop-down list to eliminate the "noise" of the same results.

  • Select Left Only to display items that are only present on the target displayed on the left and NOT present on the target displayed on the right.

  • Select Right Only to display items that are only present on the target displayed on the right and NOT present on the target displayed on the left.

The icons that appear in the view are mostly intuitive: equal–same, not equal–different. The key icon denotes the key properties of the configuration item type. An indication of Out of Range means that the property value failed a value constraint set on the property. A boxed 1 (left only) or 2 (right only) means that the comparison did not find a matching item to compare to the first or second configuration, respectively.

System Drift Comparison Results

When a system drift comparison is completed, the system results page displays the system and its members along with its comparison results. Drill down from the system results to the simple target results to view additional configuration comparison result details.

Synchronizing Configuration Extension Files

Use this feature to perform on-demand file synchronization when a comparison of file-based configurations returns differences. Often, this involves configuration extensions that users create. See Configuration Extensions and Collections, for information on configuration extensions.

Note:

This feature is available only for file-based configuration extensions. Differences resulting from comparisons of command-based or SQL query-based configuration extensions cannot be synchronized.

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management. Click the Drift Results tab on the left. On the Drift Results page, click the Drift Definition of interest.

    On the Comparison Results page, locate the Configuration Items (Differences) region located on the left. Select all the Configuration Extension items of interest in the Configuration Tree. You can select multiple files, indicating that you'll be updating all of them in the same direction.

    Click the Synchronize icon located to the right of the Configuration Item. This icon is present only for configuration extension (CE) nodes, and only for CE nodes that are eligible for synchronization.

    Note: File synchronization is also available from the results of one-time comparisons.

  2. The Synchronize File page displays the files selected on the Comparison Results page. If there are files that cannot be synchronized, such as those that have no differences, they are not submitted for synchronization.
  3. Optionally, use the Preview feature to view the effect of the update on a file-by-file basis. Click the eyeglasses icon to view the file before and after the update in raw format.
  4. Complete the Credentials and Setting sections as follows:

    • Specify the login credentials as necessary. You must have login access to the target destination and write permission on the directory or directories to be updated.

    • Select the appropriate radio button to indicate a destination directory. In either case (original or alternate), you must have write permission on the directory.

    • Select the appropriate radio button for how to proceed on conflict. The comparison is performed using data from the repository. A conflict arises when the file to be updated has changed on the target and is different from the data used for the comparison. Indicate what you want to do in this case—proceed or stop.

    • Note that irrespective of the selection for destination directory (original or alternate), the conflict check is always performed against files in the original directory.

    • Indicate the desired backup options (both are selected by default when the update target is the original directory):

      • Mark the appropriate check box if you want to save a snapshot of the configuration to be updated prior to synchronizing (give it a descriptive name so you can easily retrieve the file from saved configurations; defaults to a generic name—CCS Synchronization Saved Snapshot—which applies even if you blank the field).

      • Mark the appropriate check box if you want to make a backup copy of the configuration file before it's updated. Browse to a directory on which you have write permission.

      These are not mutually exclusive options. With the former, you are saving time-stamped collection data in the OMS repository; whereas, with the latter, you are storing a copy of a file in a file system.

    • If desired, perform an on-demand collection refresh of the destination target's configuration data immediately after file synchronization. This way, if you rerun the comparison or view the configuration in the Configuration Browser, the effects of the update will be visible. You can also run a manual refresh at any time, or wait for the next scheduled collection.

      The check box is selected by default when the original destination directory is the update target. The check box is disabled if you specified an alternate directory, as there would be nothing to refresh in this case.

    • When satisfied with the results, click Synchronize.

On the Synchronize Files popup, click the link to track the synchronization job. When the job completes, you can rerun the comparison to verify the update, assuming you requested a refresh. You can also open the configuration extension in the Configuration Browser and confirm the update there.

Not All Configuration Files Can Be Synchronized

You may notice in the comparison results differences view that some files, though different, cannot be selected for synchronization (their check boxes are disabled). There are several possible reasons, including:

  • The destination file is non-writable.

  • There is no source file.

  • Files that do not have differences.

  • During the configuration extension definition, the file was associated with a parser that does not support a process called reverse transform, which is, effectively, the ability to return the parsed form of a file to a syntax tree structure that can then be rendered back into a physical representation. Not all parsers support reverse transform.

Note: It is on the File Synchronization page where the files are marked as eligible or ineligible for synchronization. It is on this page where you can determine whether the selections are valid.

Comparisons and Drift Management with Oracle Enterprise Manager 13c Release 4 Update 5 (13.4.0.5) and Above

Comparisons and Drift Management offers new features for Oracle Enterprise Manager 13c Release 4 Update 5 (13.4.0.5) users.

About the Dashboard

The Comparison and Drift Management Dashboard lets you access your drifted and inconsistent targets from a single page.

The dashboard contains the following sections:

Figure 26-1 Comparison and Drift Management Dashboard

This image shows the new layout for the Comparison and Drift Management dashboard available for Enterprise Manager Release Update 5 and above.

Drift Overview

Compare the latest or a saved target configuration to one or more targets. Some of the uses are:
  • Ensure a target's configuration remains unchanged compared to a reference or a saved target configuration.
  • Get notified when a target configuration change results in undesired differences.

Typical Scope: Large number of targets

Consistency Overview

Compare targets within a container for consistency. Some of the uses are:

  • Ensure targets of a similar target type remain the same within a system.
  • Ensure targets within a static or dynamic group remain consistent.

Typical Scope: Large number of targets

Comparison Overview

Compare the latest or a saved target configuration to one or more targets. Some of the uses are:

  • Investigate problems where a change is suspected.
  • Tune a comparison template before using it in Drift or Consistency Management.

Typical Scope: Small number of targets

Drift Results and Consistency Results by Target Type

A bar graph demonstrating the different target's drift and consistency results sorted by target type.

Library

The Library offers a way to see created Drift Definitions, Consistency Definitions, and Comparison Templates.

Create a Drift Definition

Create a Drift Definition to select a target and see when it drifts from the selected source.

To perform a Drift Management Comparison:

  1. From the Enterprise menu, select Configuration, then click Comparison & Drift Management.

  2. Click Drift Results. In Drift Results, click Create Definition.

  3. In the Applicable To dialog box, select the Target Type and Template. For example, select Database Instance and the template of choice, in this case Database Instance Template. Click OK.

On the Drift Definition page, provide the following information:

  • Definition Name - Make the name meaningful. The information from the Compare Configurations popup is replicated.

  • Source Configuration

    Select either Latest Configuration or Saved Configuration. Either one is the gold configuration against which the other targets will be compared. When using the Latest Configuration, choose the source target. When using the Saved Configuration, choose the appropriate configuration.

  • Advanced

    Expand this section to provide additional factors on the comparison.

    • Severity

      Options are: Minor Warning, Warning, and Critical.

    • Target Property Filter

      You can specify specific target properties that determine which targets this definition can work against. These properties are Operating System, Target Lifecycle State, Version, and Platform. When you specify a target property filter for this definition, for instance for Linux OS, it will only be applicable to targets on Linux Operating Systems.

    • Description

      Describe this drift definition and provide as much detail as possible. This information provides information for others who will be using this definition in the future.

    • Rationale

      Explain the reason for this comparison, for example: This content will detect configuration drifts for the targets.

    • Keywords

      Enables you to categorize this drift definition for quick reference.

After you have provided the information, select one of these options:

  • Save and Test Targets

    Once a target is associated with a comparison, comparisons are automatically triggered for that target when appropriate. For example, when the target's configuration changes, a comparison will be triggered, and if the automatic comparison results in a difference from the reference target, notifications will be sent, and the differences will be available in any reports for the drift comparison.

    Before associating targets with a comparison, you may want to run a test comparison. Configuration differences detected during a test comparison do not cause notifications to be sent, and will not appear in reports. The results from the test comparison can be used to verify that the comparison template is only comparing items of interest. Also, the test results can give a preliminary indication of how different a target is from the reference target. The Save and Test Targets option lets you run these test comparisons.

    To test targets, in the Test Targets page, clickAddto add a compared target. Select the target, and click Run Test. This will trigger a test comparison, and the number of differences generated will be placed in the Differences column of the table. To view the results of the test comparison, click on the difference count. Once you are satisfied with the comparison results, select the target and click Associate to permanently associate the target with the drift comparison, enabling automatic re-comparisons, notifications, and visibility of the target in reports.

  • Save and Associate Targets

    Saves the input, triggers automatic comparisons that use this comparison definition, and directs you to the Target Association for Drift Definition page.

    Click Add and select the targets you want to associate with this definition. Click OK. You will be prompted on whether you really want to save the associations.

  • Save and Return

    Saves the input for future use. You can view the saved comparison definition in the Definition Library tab of the Comparison & Drift Management dashboard.

    You are returned to the page from where the configuration drift was launched. For example, if you started from Drift Definition Library page, you will return to that page. If you started from the Overview tab, you will return to the Overview tab. If you started from the Drift Results page, you will return to the Drift Results page.

  • Cancel

    Aborts the operation. None of the input will be saved.

Create a Consistency Definition

Create a Consistency Definition to select a target type within a system and verify all targets have the same configuration.

To perform a Consistency Comparison:

  1. From the Enterprise menu, select Configuration, then click Comparison & Drift Management.

  2. Click Comparison Results. In Drift Results, click Create Definition.

  3. Select a location.

    Note:

    You can create comparison definitions from several locations. You can create comparison definitions from:

    • Overview tab

    • Definition Library tab

    • Comparison Templates tab, after selecting a template

  4. On the popup, select the Target Type and Template. For example, select Cluster Database and the template of choice. The template can be one that you have defined, or as in this case, Cluster Database Template. Then click OK.

  5. On the Consistency Definition Details page, change the Definition Name as needed. The Compare Template and Applicable To information are replicated.

  6. Click Advanced to provide information which is used for compliance.

    • Compliance Standard Name is the same name as used for the Consistency Definition Name. This is the name to search for when using compliance standards.

    • Rule Name is the same name as the compliance standard name.

    • Compliance Rule State is automatically considered Production.

    • Choose the severity of the drift. Options are: Minor Warning, Warning, and Critical. When a consistency is in a Critical state, it needs to be addressed in a timely manner. For example, if the space on a database is getting very low, it needs to be addressed before it crashes.

    • Target Property Filter

      You can specify specific target properties that determine which targets this definition can work against when it is associated with a compliance standard. These properties are Operating System, Target Lifecycle State, Version, and Platform. When you specify a target property filter for this definition, for instance for Linux OS, it will only be applicable to targets on Linux Operating Systems.

    • Description

      Describe this consistency definition and provide as much detail as possible. This information provides information for others who will be using this definition in the future.

    • Rationale

      Explain the reason for this comparison, for example: This content will detect configuration consistency for the systems.

    • Keywords

      Enables you to categorize this consistency definition for quick reference.

  7. For consistency comparisons, Oracle chooses one target of each member target type as the reference target. All other members will be compared against the reference target of the same target type.

    Note: Since all members of the same type should be the same, it should not matter which target is selected as the reference target. However, if you would prefer to choose specific targets as reference targets, click the Edit icon in the Reference Targets when associating targets, or click the Reference Targets button when creating a one-time comparison. This allows you to choose your own reference targets for each member target type.

    After you have provided the information, select one of these options:

    • Save and Test Targets

      Saves the comparison definition which compares the members against reference members within the system. You can then run test comparisons to verify that the comparison template only compares attributes of interest to you.

      To review the results, click the number in the Differences column. The Comparison Results page appears.

    • Save and Associate Targets

      Saves the input and directs you to the Target Association for Consistency Definition page. Click Add and select the systems you want to associate with this definition. Click OK.

      Once the targets are associated with a comparison, comparisons are automatically triggered for the targets when appropriate. For example, when a target's configuration changes, a comparison will be triggered, and if the automatic comparison results in a difference from the reference target, notifications will be sent, and the differences will be seen in any reports for the consistency comparison.

    • Save and Return

      Saves the input for future use. You will be returned to the Comparison Dashboard.

    • Cancel

      Aborts the operation. None of the input will be saved.

Create a One-Time Comparison

Create a one-time comparisons to immediately view the differences between target configurations. One-time comparisons differ from drift and consistency comparisons in that the comparison is only evaluated once, even if you choose to save the results for later viewing.

To perform a One-Time Comparison:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. Click One-Time Comparison Results.

  3. Click Create Comparison.

  4. Select Basic or Advanced comparison.

    • The Basic One-Time Comparison is a simple comparison between two or more targets. The fields are:

      • Reference Target (Current)

        Target against which the comparison is being made.

      • Comparison Template

        Template or pattern to be used for the comparison. This template can contain property settings, rules for matching configuration items, and rules for including and excluding configuration items.

    • The Advanced One-Time Comparison provides more options than the Basic One-Time Comparison. For example, you can use saved configurations and perform a consistency comparison within a system.

      The fields are:

      • Reference Target (Current)

        Target against which the comparison is being made. Use this option when comparing targets. Note that the list of the targets is restricted to 2,000. Use the Search option to restrict the list of targets.

      • Reference Target (Saved)

        Configuration that was created at an earlier time and which will be used as the base for the comparison. Use this option when you want to compare targets against your gold configuration.

      • Consistency Target Type (use for systems)

        When comparing systems, provide the type of system, for example, Cluster Database or Database System.

        Use this option to test the consistency of targets among systems. Note that all cluster members have the same saved configuration. For example, you can determine if all the configuration database parameters are the same within a cluster database.

      • Comparison Template

        Select a template that has gone through rigorous testing or use this one-time comparison to fine tune the comparison template to compare only what you need.

        An example of an existing template is one that you created or a template provided by Oracle. If you don't supply a template, there will be a one-to-one comparison between the fields in the reference target and the compared targets.

  5. Click Add to select targets or Add Saved to select saved configurations for the comparison. Remember that you can only compare targets of the same target type.

    Note that the more targets you add, the longer it will take for the compare operation to complete.

    After you have added the targets, and you decide to minimize the number of targets, on the Target menu, highlight the targets to eliminate and click Remove.

  6. Click OK. The comparison begins immediately and results are displayed on the Comparison Results page.

    Depending on the options you chose, it may take a while for the results to display. Click the Enterprise Manager Refresh button until the comparison is completed and the In Progress icon disappears. Click the i icon located by Comparison Results name for a listing of the options chosen for the comparison.

Manage the Definition Library

Run management tasks from the Definition Library, the repository for all drift and consistency definitions.

To access the Definition Library:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. Click Definition Library.

From the Definition Library, you have access to the following tasks:

  • Create a new definition.

  • Edit an existing definition.

  • Run tests against a definition.

  • Search for a definition.

  • Associate targets or groups to a definition (perform the association after you have verified test results from the Test Association page).

  • Delete a definition.

  • Import and export a definition.

Manage Comparison Templates

Run management tasks from the Comparison Templates screen.

To access the Comparison Templates screen:

  1. From the Enterprise menu, select Configuration, then select Comparison & Drift Management.

  2. Click Comparison Templates.

From the Comparison Templates screen, you have access to the following tasks:

  • Create a new comparison template.

  • Create Like an existing comparison template. This will import the configuration of an existing comparison template.

  • Edit an existing comparison template.

  • Search for a comparison template.

  • Compare comparison templates.

  • Delete a comparison template.

  • Import and export comparison templates.

Comparison and Drift Management BI Publisher Reports

Business Intelligence Publisher (BI Publisher) is the primary reporting system that provides a single, Web-based platform for authoring, managing, and delivering interactive reports and all types of highly formatted documents.

Using BI Publishes, Enterprise Manager provides the following Comparison and Drift Management reports:

  • Drift Report for Systems - Drift results report for system targets. It includes Drift definition summary, various roll-ups and Drift Comparison results. Examples of system targets are databases and fusion applications.

  • Drift Report - Drift results report. It includes Drift definition summary, various roll-ups and Drift Comparison results. Use this report to view simple targets, for example, host.

  • Patch Differences for Fusion Instances (Scheduled)

    Note: This is a Bursting/Scheduler only report. Preconditions include:

    • Comparison template for Fusion Instance and its corresponding Oracle Home target type is available.

    • Oracle Home comparison template contains the 'Patches Installed In Oracle Home' configuration item, and has the 'Patches ID' and 'Patch Language' properties enabled.

    • Comparison was performed using the proper template.

  • Patch Differences for Fusion Instances

    Preconditions include:

    • Comparison template for Fusion Instance and its corresponding Oracle Home target type is available.

    • Oracle Home comparison template contains the 'Patches Installed In Oracle Home' configuration item, and has the 'Patches ID' and 'Patch Language' configuration properties enabled.

    • Drift definition was created using the proper Fusion Instance template.

To access the Comparison and Drift Management BI Publisher reports:

  1. From the Enterprise menu, select Reports, then select BI Publisher Enterprise Reports.

  2. In the list of Enterprise Manager Reports, select Comparison and Drift Management.

  3. In the login screen, provide your credentials to access the reports.

NOTE:

  • To see information in these reports, you must have had to run a comparison

  • Only differences are reported

  • Information is grouped by compared targets