4.4 Oracle Health Check Collections Manager Application Features

Familiarize yourself with the features of Oracle Health Check Collections Manager Application.

4.4.1 Global Select Lists

Oracle Health Check Collections Manager Application provides an option to display the data based on select lists like Business Units, Systems, and Data for last periods of time.

All these select lists are global within the application and options available on starting of each tab.

  • Business Unit

  • System

  • Data interval

4.4.2 Home Tab

Displays systems and their statuses, and recent activities of all users who has permission to access the application.

  • Displays systems and their statuses in graphs with color coded green, orange, and red based on check results (passed, warning, and failed).

  • The Home tab provides an option to display the data based on select lists like Business Units and Data for last periods of time. There is also an option to filter the most failed/warned checks and recent collections based on system name.

  • The Most Failed Checks region displays information for the most frequently failed checks for all collections for the time period, Business Unit, or System selected, and displays the check name, fail count. There is a similar region for most warned checks.

  • The Recent Collections region displays brief information about recently uploaded collections based on time frame, Overall score with Fail, Warning, and Pass counts and a Status flag. Recent collections are automatically compared to the last collection from the same system, whenever it occurred, if there is one.

    Status Flags are color-coded green, orange, or red based on the comparison between the recent collection and the last collection, if any.

    • GREEN: There is no difference at all between the two collections or one or more findings from the last collection improved from WARNING or FAIL to PASS or there was no earlier collection to compare with.

    • ORANGE: There were one or more regressions between the last collection and the most recent on a given system. In other words some findings transitioned in a negative way, for example, PASS to WARNING.

    • RED: There were one or more regressions between the last collection and the most recent on a given system. In other words some findings transitioned in a negative way, for example, PASS to FAIL.

  • Recent Activity in User Range shows recent activities by all users across all collections specific to the access role granted the user.

    • DBA role users can see everything that happens in the systems assigned to them.

    • DBA Manager role users can see everything within their Business Unit and the systems assigned to them.

    • Admin role user can see everything when there is a collection data uploaded in to the application.

4.4.3 Collections Tab

Displays incidence information for each collection, and collection score for failed, warning, and failed checks.

  • Displays all collections and allows you to filter the list of collections based on Business units and System. You can also filter based on Status flag. The list is also inherently filtered to those collections the user has access to, based on their assigned role.

  • Displays incident information for each collection indicated by Delta (Δ) color coded red, blue, and green based on ticket status. Click the delta symbol to raise a new ticket or alter the ticket for an entire collection.
    • RED (No Incident ticket exists): Click to create a new incident ticket for the collection or individual checks.

    • BLUE (An open Incident ticket exists): Click to open the incident ticket for editing.

    • GREEN (A closed Incident ticket exists): Click opens the closed incident ticket for viewing.

  • Collection Score is calculated based on failed, warning, and passed checks.

    If a user raised a ticket for the collection, resolved the issues and the ticket is closed signifying the issues have all been resolved, then Oracle Health Check Collections Manager changes the collection score to 100%.

    If a user raised a ticket for an individual check and if it is closed signifying that the finding has been resolved, then Oracle Health Check Collections Manager changes the status of the check as PASS and recalculates the collection score.

    Collection Score is derived using following formula.

    • Every check has 10 points.

    • Failure deducts 10 points.

    • Warning deducts 5 points.

    • Info deducts 3 points.

  • A More Info link next to a collection indicates that the collection was manually uploaded into the application.

  • Click the linked collection name in the list to load the collection in the Browse tab.

4.4.4 Browse Tab

Browse tab enables you to list individual checks based on the filters set.

  • Set filters once the list of checks is created.

  • Create and alter incident tickets for individual audit check findings similar to as described in the Collections tab.

  • Select checks to ignore and to undo previously ignored checks. Select the check box beside the audit check and click Ignore Selected. Oracle Health Check Collections Manager marks them as FAIL-IGNORED, indicating that the check had failed but is ignored.

    Oracle Health Check Collections Manager ignores the checks for the entire level based on the level selected for ignoring.

    To ignore selected failed checks, you must choose the ignore type from the following list:

    • Ignore from collection

    • Ignore from system

    • Ignore from a business unit

    • Ignore from all business units

      Note:

      The domain for ignoring checks is within the role assigned to the user.

    All ignored checks are listed under the Ignored Checks tab. If needed, undo ignore.

    To undo the selected Ignored checks, consider the type from the following list:

    • Undo ignore from collection

    • Undo ignore from system

    • Undo ignore from business unit

    • Undo ignore from all business units

      Note:

      The domain for undoing ignored checks is within the role assigned to the user.

Figure 4-45 Browse Tab - Apply Filters

Description of Figure 4-45 follows
Description of "Figure 4-45 Browse Tab - Apply Filters"

Figure 4-46 Browse Tab - Apply Filters - Ignored Checks

Description of Figure 4-46 follows
Description of "Figure 4-46 Browse Tab - Apply Filters - Ignored Checks"

4.4.5 Compare Tab

Compare tab enables you to compare audit check results and patch results.

  • Compare Audit check Results

    • Compare the audit check findings from two different collections based on Business Unit, System, DB Version and Platform. The collections available for comparison are limited to filters set.

    • Compare collections from the same or different systems.

  • Compare Patch Results

    • Compare installed Oracle patches from two different collections. The comparison displays the difference between the two collections based on patch results.

Figure 4-48 Compare Tab - Audit Checks Diff

Description of Figure 4-48 follows
Description of "Figure 4-48 Compare Tab - Audit Checks Diff"

Figure 4-49 Compare Tab - Patch Results Diff

Description of Figure 4-49 follows
Description of "Figure 4-49 Compare Tab - Patch Results Diff"

Note:

Row highlighted in blue indicates that the patch is recommended, but it is not installed in one of the collections.

4.4.6 Report View Tab

Provides a graphical representation of database checks, instance checks, home path checks, and system health checks.

  • Provides a printable view option to print the graphical summary of system collection

  • Displays separate graphical summary view for database checks, instance checks, and home path checks breakup based on check type and check status in collection

  • Displays system health check details based on status and check type in collection

Figure 4-50 Report View Tab - Summary

Description of Figure 4-50 follows
Description of "Figure 4-50 Report View Tab - Summary"

Figure 4-51 Report View Tab - Details

Description of Figure 4-51 follows
Description of "Figure 4-51 Report View Tab - Details"

4.4.7 Upload Collections Tab

Provides an interface to manually upload a collection into Oracle Health Check Collections Manager Application and provides a list of uploaded collections and file details.

These manually uploaded collections are unzipped and their data imported into the framework as if they had been uploaded at runtime when the tool was run. Therefore, even if the tool is not configured for automatic upload into the Oracle Health Check Collections Manager Application, you can always upload collections manually.

Note:

Using a combination of tables and environment variables, you can automate the process of uploading collections into the database hosting the Oracle Health Check Collections Manager Application at runtime.

Figure 4-52 Upload Collections Tab

Description of Figure 4-52 follows
Description of "Figure 4-52 Upload Collections Tab"

4.4.8 Tracking Support Incidents

The Incidents tab gives you a complete system for tracking support incidents.

  • Specify contact details of each customer, products and categories, and then set up values to limit status codes, severity, and urgency attributes for an incident

  • Raise a new ticket by clicking the Delta (Δ) symbol. Oracle Health Check Collections Manager displays this symbol only in the Collections and Browse tabs.

  • The Browse tab enables you to create a new ticket on individual checks

  • The Collections tab enables you to create a single ticket for entire the collection

  • Delta (Δ) symbol is color coded red, blue, and green based on the ticket status.

    • RED (No Incident ticket exists): initiates the process to create a new incident ticket for the collection or individual checks

    • BLUE (An open Incident ticket exists): opens the incident ticket for editing

    • GREEN (A closed Incident ticket exists): opens the closed incident ticket for viewing

  • Track the progress of the ticket in an update area of the ticket, or add attachments and links to the incident

  • Use tags to classify incidents and use the resulting tag cloud in your reports

  • Incident access and management happen only within your access control range

Note:

Incident Tracking feature is a basic stand-alone system and it is not designed for integration with other commercial enterprise-level trouble ticketing systems.

Incident Tracking Features

  • Search options

  • Track and analyze incident tickets

  • Flexible and updateable incident status

  • Robust reporting

  • Link, Note, and File Attachments

  • Flexible Access Control (reader, contributor, administrator model)

4.4.8.1 Creating or Editing Incidents Tickets

Create or edit incident tickets for individual checks or for an entire collection.

Oracle Health Check Collections Manager represents the statuses of each ticket with different colored icons. To act upon the tickets, click the icons.

4.4.8.1.1 Creating Incident Tickets

To create incident tickets:

  1. Click the Delta (Δ) symbol colored RED.
  2. Add your ticket details.
  3. Click Next.
  4. Select the Product and Product Version.
  5. Click Next.
  6. Select the Urgency of the ticket.
  7. Select the Severity of the ticket.
  8. Select the Status of the ticket.
  9. Select the Category of the ticket.
  10. Enter a summary and description of the incident.
  11. Click Create Ticket.
4.4.8.1.2 Editing Incident Tickets

To edit incident tickets:

  1. Click the Incident tab.
  2. Click Open Tickets.
  3. Click the ticket.
  4. Click Edit Ticket.
  5. Alter required details, click Apply Changes.

Note:

Click the delta symbol colored GREEN in the Collections or Browse tabs to edit incident tickets.

4.4.9 Authoring User-Defined Checks

Define, test, and maintain your own checks that are specific to your environment.

Oracle supports the framework for creating and running user-defined checks, but not the logic of the checks. It is your responsibility to test, verify, author, maintain, and support user-defined checks. At runtime, Oracle ORAchk and Oracle EXAchk script run the user-defined checks and display the results in the User Defined Checks section of the HTML report.

The user-defined checks are stored in the Oracle Health Check Collections Manager schema and output to an XML file, which is co-located with the ORAchk script. When run on your system, ORAchk 12.1.0.2.5 and later tries to find the XML file. If found, then Oracle ORAchk runs the checks contained therein and includes the results in the standard HTML report.

To author user-defined checks:

  1. Click the User Defined Checks tab, then select Add New Check.

    Figure 4-54 User-Defined Checks Tab

    Description of Figure 4-54 follows
    Description of "Figure 4-54 User-Defined Checks Tab"
  2. Select OS Check or SQL Check as Audit Check Type.

    Operating system checks use a system command to determine the check status. SQL checks run an SQL statement to determine the check status.

    Figure 4-55 User-Defined Checks Tab - Audit Check Type

    Description of Figure 4-55 follows
    Description of "Figure 4-55 User-Defined Checks Tab - Audit Check Type"

    Once you have selected an Audit Check Type, Oracle Health Check Collections Manager updates the applicable fields.

    Any time during authoring, click the title of a field to see help documentation specific to that field.

    Operating system and SQL commands are supported. Running user-defined checks as root is NOT supported.

    Figure 4-56 User-Defined Checks Tab - Audit Check Type - OS Check

    Description of Figure 4-56 follows
    Description of "Figure 4-56 User-Defined Checks Tab - Audit Check Type - OS Check"

    Once a check is created, the check is listed in the Available Audit Checks section.

    Filter the checks using the filters on this page.

    Figure 4-57 User-Defined Checks Tab - Available Audit Checks

    Description of Figure 4-57 follows
    Description of "Figure 4-57 User-Defined Checks Tab - Available Audit Checks"
  3. Click the Generate XML.

    On the right, find a link to download the generated user_defined_checks.xml file.

    The generated XML file includes all the checks that have been authored and have not been placed on hold. Placing checks on hold is equivalent to a logical delete. If there is a problem with a check or the logic is not perfect, then place the check on hold. The check that is placed on hold is not included in the XML file. If the check is production ready, then remove the hold to include the check the next time the XML file is generated.

  4. Download and save the user_defined_checks.xml file into the same directory as the Oracle ORAchk and Oracle EXAchk tools.

    Oracle ORAchk and Oracle EXAchk run the user-defined checks the next time they run.

    Figure 4-58 User-Defined Checks Tab - Download User-Defined Checks

    Description of Figure 4-58 follows
    Description of "Figure 4-58 User-Defined Checks Tab - Download User-Defined Checks"
  5. Alternatively, to run only the user-defined checks use the profile user_defined_checks.
    When this option is used, then the user-defined checks are the only checks run and theUser Defined Checks section is the only one with results displayed in the report.
    orachk –profile user_defined_checks
    exachk –profile user_defined_checks
  6. To omit the user-defined checks at runtime, use the –excludeprofile option.
    orachk –excludeprofile user_defined_checks
    exachk –excludeprofile user_defined_checks

Related Topics