1.10 Oracle Health Check Collections Manager for Oracle Application Express 4.2

Oracle Health Check Collections Manager for Oracle Application Express 4.2 provides you an enterprise-wide view of your health check collection data.

1.10.1 Installation

Follow the installation procedures sequentially to install Oracle Health Check Collections Manager.

Note:

Upgrade Oracle Health Check Collections Manager directly from the Oracle ORAchk or Oracle EXAchk tool.

Related Topics

1.10.1.1 Configuring Oracle Application Express and Creating a Workspace

To configure Oracle Application Express and create a workspace, follow these procedures.

If the Oracle Application Express 4.2 component is already installed and configured on your database, then skip to Install Collection Manager Application.
  1. Download the latest version of Oracle Application Express.
  2. To install and configure Oracle Application Express, refer to the Application Express Installation Guide.
  3. Create a workspace.
    1. Log in to Oracle Application Express administration services.

      Note:

      The URLs used for accessing the Oracle Health Check Collections Manager application depend on how Oracle Application Express was deployed initially.

      • If you have configured Oracle Application Express using the Oracle HTTP Server with mod_plsql, then specify the URL as follows: 
        http://host:port/pls/apex/apex_admin
      • If you have configured Oracle Application Express the Oracle XML DB HTTP listener with the embedded PL/SQL gateway, then specify the URL as follows: 
        http://host:port/apex/apex_admin
        For example: 
        http://dbserver.domain.com:8080/apex/apex_admin

      • The default schema user for Oracle Application Express administration services in the Oracle database is ADMIN.

      • The password is the one you gave at the time of configuring the Oracle Application Express component in the Oracle database.

      Figure 1-88 Administration Services Login

      Description of Figure 1-88 follows
      Description of "Figure 1-88 Administration Services Login"
    2. In the Oracle Application Express Admin home page, click Manage Workspaces.

      Figure 1-89 Manage Workspaces

      Description of Figure 1-89 follows
      Description of "Figure 1-89 Manage Workspaces"
    3. Under Workspace Actions, click Create Workspace.

      The Create Workspace Wizard appears.

      Figure 1-90 Identify Workspace

      Description of Figure 1-90 follows
      Description of "Figure 1-90 Identify Workspace"

      • Identify Workspace:

        1. Workspace Name: Enter a unique workspace name, for example, ORAchk_CM_WS.

        2. Workspace ID: Leave Workspace ID blank to have the new Workspace ID automatically generated.

          Workspace ID must be a positive integer greater than 100000.

        3. Workspace Description: Enter workspace description.

        4. Click Next.

        Note:

        Associate a workspace with a database schema.

      • Identify Schema:

        1. Specify whether you are reusing an existing schema or creating a new one. This depends on whether you already have Oracle ORAchk and Oracle EXAchk configured to upload data to a schema in the database. If you do, then specify the existing schema. If not, then the name of the schema you create must be the one you intend to use for uploading the Oracle ORAchk data once configured.

        2. If you choose an existing schema in the database, then it should not be an Oracle Application Express administration schema (admin).

          • If you are using an existing schema:

            1. For Re-use existing schema, select YES.

            2. Select a schema from the list.

            3. Click Next.

              Figure 1-91 Identify Schema - Reuse Schema

              Description of Figure 1-91 follows
              Description of "Figure 1-91 Identify Schema - Reuse Schema"

          • If you are creating a new schema:

            1. For Re-use existing schema, select NO.

            2. Enter the schema name and password, for example, ORAchk_admin, and so on.

            3. Specify the space quota.

            4. Click Next.

              Figure 1-92 Identify Schema - New Schema

              Description of Figure 1-92 follows
              Description of "Figure 1-92 Identify Schema - New Schema"

              Note:

              Minimum Space Quota should not be less than 100 MB to prevent application import failures.

      • Identify Administrator:

        1. Enter administrator user name and password.

        2. Enter Personal details.

        3. Click Next.

          Figure 1-93 Identify Administrator

          Description of Figure 1-93 follows
          Description of "Figure 1-93 Identify Administrator"

      • Confirm your selections and then click Create Workspace.

        Figure 1-94 Create Workspace - Confirm Request

        Description of Figure 1-94 follows
        Description of "Figure 1-94 Create Workspace - Confirm Request"

        Your workspace is created.

  4. Click Manage Workspaces.

    • Under Workspace Reports, click Existing Workspaces.

      Figure 1-95 Manage Workspaces - Existing Workspaces

      Description of Figure 1-95 follows
      Description of "Figure 1-95 Manage Workspaces - Existing Workspaces"

    • To edit Workspace information, click the workspace name, edit any necessary details, and then click Apply Changes.

    • Log out from Oracle Application Express Administration services.

Related Topics

1.10.1.1.1 Log in to the Workspace

To log in to Application Express admin user workspace, follow these procedures.

  1. Log in to Oracle Application Express Admin User Workspace.

    Note:

    The URLs used for accessing the Oracle Health Check Collections Manager application depend on how Oracle Application Express was deployed initially.

    • If you have configured Oracle Application Express the Oracle HTTP Server with mod_plsql, then specify the URL as follows: 
      http://host:port/pls/apex/apex_admin
    • If you have configured Oracle Application Express using the Oracle XML DB HTTP listener with the embedded PL/SQL gateway, then specify the URL as follows: 
      http://host:port/apex/apex_admin
      For example: 
      http://dbserver.domain.com:8080/apex/apex_admin
  2. Enter the workspace name, workspace user name, and password details to log in.

    Figure 1-96 Log into the Workspace

    Description of Figure 1-96 follows
    Description of "Figure 1-96 Log into the Workspace"
  3. For the first time login, Application Express prompts you to change the password.
  4. Log in again using the new password.

1.10.1.1.2 Application Express User Accounts

Application Express provides three types of users, namely, workspace administrators, developers, and end users.

Table 1-15 Application Express Types of Users

Type of User Description

Workspace administrators

Workspace administrators can also create and edit user accounts, manage groups, and manage development services.

Developers

Developers can create and modify applications and database objects.

End users

End users are non-administrative who have no development privileges and can only access applications that do not use an external authentication scheme. For the Oracle Health Check Collections Manager Application, almost all the users fall into this category. A special role within the Oracle Health Check Collections Manager Application, DBA Managers, and the DBAs manage all application users.

To grant access to the Oracle Health Check Collections Manager Application for non-administrative users (End users), you must log in to the Workspace as an Admin user.

  1. Log in to Oracle Application Express admin user workspace.
  2. Click the Administration tab.
  3. Click Manage Users and Groups.
  4. Click Create User.

    • These users are application admin users, DBA Managers, and DBAs who can authenticate to the application and manage their collections.

  5. Fill in the user details.

    • Follow a consistent naming convention and specify unique user names. A reasonable naming convention would be firstname.lastname.

      Figure 1-97 Application Express User Accounts

      Description of Figure 1-97 follows
      Description of "Figure 1-97 Application Express User Accounts"

    • For non-administrators, use the default, No for User is a developer and User is a Workspace Administrator options.

  6. Assign a temporary password for each user and communicate that password to the end user. Application Express prompts them to change this password the first time they log in.
  7. Click Create User.

1.10.1.2 Install Oracle Health Check Collections Manager Application

To install Oracle Health Check Collections Manager, follow these procedures.

  1. Verify if the workspace admin schema owner and the owner of the schema used for import of the Oracle Health Check Collections Manager Application have grants to:

    • Create Job

    • Execute on the database packages DBMS_RLS and UTL_SMTP owned by the SYS user.

    The Oracle Health Check Collections Manager Application is distributed as an SQL script. Stage the script on the workstation that is used to install the application.

    Execute privilege on the database package UTL_SMTP is required only if you use Oracle Health Check Collections Manager Email Notification System Feature. Oracle Health Check Collections Manager uses UTL_SMTP package on one of the objects RAC13_EMAIL. Failing to grant EXECUTE ON UTL_SMTP privilege to workspace owner ends up in compilation error. You can see this information in the Installation Summary. Ignore this information, if you are not using the Oracle Health Check Collections Manager Email Notification System feature.

  2. Verify if you have required privileges by running the SQL query as follows: 
    select GRANTEE,TABLE_NAME,PRIVILEGE  from USER_TAB_PRIVS; 
GRANTEE      TABLE_NAME PRIVILEGE
CM_USER     DBMS_RLS            EXECUTE
CM_USER     UTL_SMTP            EXECUTE

select USERNAME,PRIVILEGE from USER_SYS_PRIVS;
USERNAME    PRIVILEGE
CM_USER     CREATE JOB
  3. Log in to the Oracle Application Express workspace administration services.
  4. Click Application Builder on the Home page.
  5. Click Import .
  6. Click Choose import file, select the SQL script appropriate for the Oracle Application Express version you are using.

    CollectionManager_App.sql when using Oracle Application Express 4.2

  7. File type: select the default option Database Application, or Component Export.
  8. File Character Set: select the default option Unicode UTF-8.
  9. Click Next.

    Figure 1-100 Specify File

    Description of Figure 1-100 follows
    Description of "Figure 1-100 Specify File"
  10. Click Install Application.

    Figure 1-101 File Import Confirmation

    Description of Figure 1-101 follows
    Description of "Figure 1-101 File Import Confirmation"
  11. Click Next.

    Note:

    Ensure that the execute privilege on DBMS_RLS and UTL_SMTP packages and create job sys privilege are granted to parsing schema owner before starting the import of the application. This prevents database support object creation failures that prevent the proper installation of the application.

    • For Parsing Schema, select the schema specified for the workspace.

    • Build Status: select default option Run and Build Application.

    • Install As Application.

    • Select any one option based on your requirement or if possible use the same application id as it is easy to upgrade the application in future. However, the application Id must be unique. Ensure that the application ID is not used by any other application, or any workspace administrators within Oracle Application Express Administration server.

      Figure 1-102 Install Application

      Description of Figure 1-102 follows
      Description of "Figure 1-102 Install Application"
  12. Click Install Application.
  13. Click Next.

    Figure 1-105 Install Applications Supporting Objects

    Description of Figure 1-105 follows
    Description of "Figure 1-105 Install Applications Supporting Objects"
  14. Click Install.

    Figure 1-106 Application Installed Successfully

    Description of Figure 1-106 follows
    Description of "Figure 1-106 Application Installed Successfully"
  15. Review the Installation summary for any errors or installation of database objects and seed data has failures.
  16. Capture the application ID generated for the application from the dialog upon successful installation of the application.

    The application ID is used in the URLs for accessing the application. Distribute the correct URL to the eventual users of the application.

  17. Click Run Application.

1.10.1.3 Log in to Oracle Health Check Collections Manager Application

To log in to Oracle Health Check Collections Manager, follow these procedures.

  1. Enter user name and password details to log in to the Oracle Health Check Collections Manager Application, click Login.

    Figure 1-107 Log in to Oracle Health Check Collections Manager Application

    Description of Figure 1-107 follows
    Description of "Figure 1-107 Log in to Oracle Health Check Collections Manager Application"

    After successful login, you are all set to use Oracle Health Check Collections Manager Application and its features.

    By default, the Oracle Health Check Collections Manager Application is deployed with some default sample data for acclimating new users to the application. Oracle Health Check Collections Manager displays the sample data In the Home page. Sample data is hidden automatically once your own data starts streaming into the application as you establish the automation and upload functionality of the tool. If you are already using the upload functionality and have your audit check results data in the database tables, and that data replaces the sample data.

    Figure 1-108 Oracle Health Check Collections Manager Default View

    Description of Figure 1-108 follows
    Description of "Figure 1-108 Oracle Health Check Collections Manager Default View"
  2. Log in to Oracle Health Check Collections Manager Application as End user:

    • The end user is not an administrator. The end users have only limited access to the application. Non-administrator users cannot do any administrative access unless administrator or developer privileges are granted.

    • The End User accounts must exist in the workspace where the application is installed.

    • To log in to the application, end user needs an application URL and login credentials.

      Provide the end users with one of the following URLs (they are interchangeable) and the temporary password that was assigned for them. 
      http://hostname:port/apex/f?p=ApplicationID

      http://hostname:port/pls/apex/f?p=ApplicationID
      For example: 
      http://dbserver.domain.com:8080/apex/f?p=103

1.10.2 Upgrading Oracle Health Check Collections Manager Application

Oracle ORAchk or Oracle EXAchk automatically upgrades new versions of the Oracle Health Check Collections Manager.

Related Topics

1.10.3 Getting Started

Familiarize yourself with the Oracle Health Check Collections Manager Application.

1.10.3.1 Incident Ticket System Lookup Lists and Seed Data

Oracle Health Check Collections Manager Application provides a basic Incident Ticket system.

Oracle Health Check Collections Manager Application is deployed with seed data for the lookup lists used for data entry for incident tickets:

  • Products

  • Category

  • Customer Contacts

  • Notifications

  • Status Codes

  • Incident Severity

  • Incident Urgency

The seed data is values that are commonly used. Add or change the seed data provided with the application. However, you must have administrator privileges to manage seed data through the Administration tab.

To access the Administration tab, click the gear icon at the upper-right corner.

1.10.3.2 Access Control System

Limit and control access based on functional roles.

By default, the Access Control system is disabled. If Access Control is disabled, then all authenticated users are granted administrator privileges and can access all application features. To assign one or more roles to the end users, manage access controls through the Administration tab. You can enable the following three functional roles available in the Oracle Health Check Collections Manager.

  • Admin: Admin role user can also be a Workspace Administrator for the application and it depends on your functional roles requirements.

  • DBA Manager

  • DBA

Assign role to the users after configuring the Access Control system.

1.10.3.3 Oracle Health Check Collections Manager Application Administration

To restrict authorized users alone to access the application, grant sufficient privileges to different roles.

Admin

Any end user who is granted an admin role by the workspace administrator has administrator privileges within the Collection Manager application.

Log in to Oracle Health Check Collections Manager Application using a URL as follows: 
http://hostname:port/apex/f?p=ApplicationID
http://hostname:port/pls/apex/f?p=ApplicationID)
For example: 
http://dbserver.domain.com:8080/apex/f?p=103

As an admin user, you must see the Administration menu (gear icon) at the upper-right corner. Click this icon to go to the Administration page.

  • Following are the admin user privileges:

    • Add or revoke admin privileges

    • Define Business Units (BU)

    • Assign DBA Manager role to users

    • Assign DBA Managers to one or more BUs

    • Assign systems to BUs (a system can belong to one BU)

    • Assign DBAs to DBA Managers

    • Assign systems to DBAs

    • Ignore any check on a collection, BU, or system

    • Create and assign incidents to any user

    • Manage all incidents

    Figure 1-109 Oracle Health Check Collections Manager - Administration

    Description of Figure 1-109 follows
    Description of "Figure 1-109 Oracle Health Check Collections Manager - Administration"

  • Only Admin role can edit any section under the Administration menu.

  • The administrator must configure data based on their requirements under the administration menu to prepare for the wider usage of the application. This is a one-time activity, however, change the configuration over time to suit your needs.

    Examples of the configuration data that you need set up are:

    • Products

    • Customers (internal designations for workgroups)

    • Categories

    • Notifications

    • Status codes

    • Manage Email Server and Job details

    • Manage Notifications

    • Incident Severity

    • Urgency

    • Manage User Roles and Assign systems to users

    • Business Units (BUs)

    • Assign systems to BUs

DBA Manager

Any user who is granted the DBA Manager role.

Log in to Oracle Health Check Collections Manager Application using a URL as follows: 
http://hostname:port/apex/f?p=ApplicationID
http://hostname:port/pls/apex/f?p=ApplicationID)

The DBA Managers must see an Administration menu (gear icon) at the upper-right corner of the application.

Figure 1-110 Oracle Health Check Collections Manager - DBA Manager Administration

Description of Figure 1-110 follows
Description of "Figure 1-110 Oracle Health Check Collections Manager - DBA Manager Administration"

Click Manage User Roles.

Figure 1-111 Oracle Health Check Collections Manager - DBA Manager - Manage User Roles

Description of Figure 1-111 follows
Description of "Figure 1-111 Oracle Health Check Collections Manager - DBA Manager - Manage User Roles"
Following are the DBA manager privileges:

  • Assign DBAs to BUs the manager manages

  • Assign DBAs to one or more systems

  • Ignore any check on a collection, BU, or system

  • Create incidents for any system

  • Assign incidents to DBAs that manage the systems in their BUs

  • Manage any incidents for systems within their assigned BUs

DBA

Any user who is granted the DBA role.

Log in to Oracle Health Check Collections Manager Application using a URL as follows: 
http://hostname:port/apex/f?p=ApplicationID
http://hostname:port/pls/apex/f?p=ApplicationID)

The DBA must see the Administration menu (gear icon) at the upper-right corner of the application.

Any end user who is granted administrator role by the workspace administrator has administrator privileges within the Oracle Health Check Collections Manager application.

Figure 1-112 Oracle Health Check Collections Manager - DBA Administration

Description of Figure 1-112 follows
Description of "Figure 1-112 Oracle Health Check Collections Manager - DBA Administration"

Click Manage User Roles.

DBA has read-only access.

Figure 1-113 Oracle Health Check Collections Manager - DBA - Manage User Roles

Description of Figure 1-113 follows
Description of "Figure 1-113 Oracle Health Check Collections Manager - DBA - Manage User Roles"
Following are the DBA privileges:

  • Cannot manage Access Control List

  • Manage systems within one or more BUs, if the DBA Managers of those BUs assign them

  • Ignore any check on a collection or system they manage

  • Manage any incidents assigned to them

1.10.3.4 Selectively Capturing Users During Login

Configure Oracle Health Check Collections Manager to capture user details and assign the users Oracle Health Check Collections Manager roles.

Automatically capturing users during login automates user management. You need not create users manually.

By default, Oracle Health Check Collections Manager:

  • Captures details of users that are logging in with LDAP authentication

  • Assigns them Oracle Health Check Collections Manager roles, for example, DBA role.

Note:

The Oracle Health Check Collections Manager roles are specific to Oracle Health Check Collections Manager and do not equate to system privileges. For example, the DBA role is not granted SYSDBA system privilege.

However, you can disable automatic capture and re-enable anytime later. If you disable, then you must manually create users and assign them roles.

To enable or disable capturing user details automatically:

  1. Click Administration, and then select Manage Users, User Roles and assign System to users.

    Figure 1-114 Manage Users, User Roles and assign System to users

    Description of Figure 1-114 follows
    Description of "Figure 1-114 Manage Users, User Roles and assign System to users"
  2. To disable automatic capture of users details, click Don’t Capture User Details (When Login).

    Figure 1-115 Don’t Capture User Details (When Login)

    Description of Figure 1-115 follows
    Description of "Figure 1-115 Don’t Capture User Details (When Login)"
  3. To re-enable automatic capture of user details, click Capture User Details (When Login).

    Figure 1-116 Capture User Details (When Login)

    Description of Figure 1-116 follows
    Description of "Figure 1-116 Capture User Details (When Login)"

1.10.3.5 Configuring Email Notification System

Oracle Health Check Collections Manager provides an email notification system that users can subscribe to.

The setup involves:

  • Configuring the email server, port, and the frequency of email notifications.

  • Registering the email address

Note:

Only the users who are assigned Admin role can manage Email Notification Server and Job details.

To configure the email notification system:

  1. Log in to Oracle Health Check Collections Manager, and then click Administration at the upper-right corner.

    Figure 1-117 Oracle Health Check Collections Manager - Administration

    Description of Figure 1-117 follows
    Description of "Figure 1-117 Oracle Health Check Collections Manager - Administration"
  2. Under Administration, click Manage Email Server & Job Details.

    Figure 1-118 Oracle Health Check Collections Manager - Configure Email Server

    Description of Figure 1-118 follows
    Description of "Figure 1-118 Oracle Health Check Collections Manager - Configure Email Server"
    1. Specify a valid Email Server Name, Port Number, and then click Set My Email Server Settings.
    2. Set Email Notification Frequency as per your needs.
      See the Notification Job Run Details on the same page.

      Figure 1-119 Oracle Health Check Collections Manager - Notification Job Run status details

      Description of Figure 1-119 follows
      Description of "Figure 1-119 Oracle Health Check Collections Manager - Notification Job Run status details"
  3. Go back to the Administration page, and click Manage Notifications.

    Figure 1-120 Oracle Health Check Collections Manager - Manage Notifications

    Description of Figure 1-120 follows
    Description of "Figure 1-120 Oracle Health Check Collections Manager - Manage Notifications"
    1. If you are configuring for the first time, then enter your email address.
      Subsequent access to Manage Notifications page shows your email address automatically.
    2. By default, Subscribe/Unsubscribe My Mail Notifications is checked. Leave as is.
    3. Under Collection Notifications, choose the type of collections for which you want to receive notifications.
    4. Select to receive notification when the available space in ORAchk CM Tablespace falls below 100 MB.
    5. Validate the notification delivery by clicking Test under Test your email settings.

      If the configuration is correct, then you must receive an email. If you do not receive an email, then check with your administrator.

      Following is the sample notification: 
      From: username@example.com
Sent: Thursday, January 28, 2016 12:21 PM
To: username@example.com
Subject: Test Mail From Collection Manager

Testing Collection Manager Email Notification System
    6. Click Submit.

Note:

Manage Notifications section under the Administration menu is available for all users irrespective of the role.

If the ACL system is enabled, then the registered users receive notifications for the systems that they have access to. If the ACL system is not configured, then all the registered users receive all notifications.

Depending on the selections, you made under Collection Notifications section, you receive an email with Subject: Collection Manager Notifications containing application URL with results.

Figure 1-121 Oracle Health Check Collections Manager - Sample Email Notification

Description of Figure 1-121 follows
Description of "Figure 1-121 Oracle Health Check Collections Manager - Sample Email Notification"

Under Comments column, click the Click here  links for details. Click the respective URLs, authenticate, and then view respective comparison report.

Figure 1-122 Oracle Health Check Collections Manager - Sample Diff Report

Description of Figure 1-122 follows
Description of "Figure 1-122 Oracle Health Check Collections Manager - Sample Diff Report"

1.10.3.6 Bulk Mapping Systems to Business Units

Oracle Health Check Collections Manager provides an XML bulk upload option so that you can quickly map many systems to business units.

To bulk map systems to the business units:

  1. Click Administration, then select Assign System to Business Unit.

    Figure 1-123 Assign System to Business Unit

    Description of Figure 1-123 follows
    Description of "Figure 1-123 Assign System to Business Unit"
  2. Click Bulk Mapping.

    Figure 1-124 Bulk Mapping

    Description of Figure 1-124 follows
    Description of "Figure 1-124 Bulk Mapping"
  3. Upload a mapping XML.
    1. Click Generate XML File (Current Mapping).
    2. Download the resulting XML file that contains your current system to business unit mappings.

      Figure 1-125 Upload a mapping XML

      Description of Figure 1-125 follows
      Description of "Figure 1-125 Upload a mapping XML"
    3. Amend the XML to show mappings that you want.
    4. Upload new Mapping XML through Upload Mapping (XML File).

1.10.3.7 Adjusting or Disabling Old Collections Purging

Modify or disable the purge schedule for Oracle Health Check Collections Manager collection data.

By default, Oracle Health Check Collections Manager purges collections older than three months.

To adjust or disable the collection purging frequency:

  1. Click Administration, and then select Manage Email Server & Job Details.

    Figure 1-126 Manage Email Server and Job Details

    Description of Figure 1-126 follows
    Description of "Figure 1-126 Manage Email Server and Job Details"
  2. Select an appropriate option:

    • Change the frequency of purges by setting different values in Purge Frequency . Then click Click To Purge Every.

    • To disable purging, click Click To Disable Purging.

    • To re-enable purging, click Click To Enable Purging.

Figure 1-127 Configure Purging

Description of Figure 1-127 follows
Description of "Figure 1-127 Configure Purging"

1.10.4 Oracle Health Check Collections Manager Application Features

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

  • 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.
  • Home Tab
    Displays systems and their statuses, and recent activities of all users who has permission to access the application.
  • Collections Tab
    Displays incidence information for each collection, and collection score for failed, warning, and failed checks.
  • Browse Tab
    Browse tab enables you to list individual checks based on the filters set.
  • Compare Tab
    Compare tab enables you to compare audit check results and patch results.
  • Report View Tab
    Provides a graphical representation of database checks, instance checks, home path checks, and system health checks.
  • 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.
  • Tracking Support Incidents
    The Incidents tab gives you a complete system for tracking support incidents.
  • Authoring User-Defined Checks
    Define, test, and maintain your own checks that are specific to your environment.

1.10.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

1.10.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.

Figure 1-128 Home Tab

Description of Figure 1-128 follows
Description of "Figure 1-128 Home Tab"

1.10.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.

Figure 1-129 Collections Tab

Description of Figure 1-129 follows
Description of "Figure 1-129 Collections Tab"

1.10.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 1-130 Browse Tab

Description of Figure 1-130 follows
Description of "Figure 1-130 Browse Tab"

Figure 1-131 Ignored Checks

Description of Figure 1-131 follows
Description of "Figure 1-131 Ignored Checks"

Figure 1-132 Browse Tab - Apply Filters

Description of Figure 1-132 follows
Description of "Figure 1-132 Browse Tab - Apply Filters"

Figure 1-133 Browse Tab - Apply Filters - Ignored Checks

Description of Figure 1-133 follows
Description of "Figure 1-133 Browse Tab - Apply Filters - Ignored Checks"

1.10.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 1-134 Compare Tab

Description of Figure 1-134 follows
Description of "Figure 1-134 Compare Tab"

Figure 1-135 Compare Tab - Audit Checks Diff

Description of Figure 1-135 follows
Description of "Figure 1-135 Compare Tab - Audit Checks Diff"

Figure 1-136 Compare Tab - Patch Results Diff

Description of Figure 1-136 follows
Description of "Figure 1-136 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.

1.10.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 1-137 Report View Tab - Summary

Description of Figure 1-137 follows
Description of "Figure 1-137 Report View Tab - Summary"

Figure 1-138 Report View Tab - Details

Description of Figure 1-138 follows
Description of "Figure 1-138 Report View Tab - Details"

1.10.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 1-139 Upload Collections Tab

Description of Figure 1-139 follows
Description of "Figure 1-139 Upload Collections Tab"

1.10.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.

Figure 1-140 Incidents Tab

Description of Figure 1-140 follows
Description of "Figure 1-140 Incidents Tab"

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)

1.10.4.8.1 Creating or Editing Incidents Tickets

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

The statuses of each ticket is represented by icons with different colors. You can act upon by clicking the icons.

1.10.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.
1.10.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.

1.10.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 1-141 User-Defined Checks Tab

    Description of Figure 1-141 follows
    Description of "Figure 1-141 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 1-142 User-Defined Checks Tab - Audit Check Type

    Description of Figure 1-142 follows
    Description of "Figure 1-142 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 1-143 User-Defined Checks Tab - Audit Check Type - OS Check

    Description of Figure 1-143 follows
    Description of "Figure 1-143 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 1-144 User-Defined Checks Tab - Available Audit Checks

    Description of Figure 1-144 follows
    Description of "Figure 1-144 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 1-145 User-Defined Checks Tab - Download User-Defined Checks

    Description of Figure 1-145 follows
    Description of "Figure 1-145 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

1.10.5 Uploading Collections Automatically

Configure Oracle ORAchk and Oracle EXAchk to automatically upload check results to the Oracle Health Check Collections Manager database.

Specify the connection string and the password to connect to the database and upload collection results. Oracle Health Check Collections Manager stores the connection details in an encrypted wallet.

Related Topics

1.10.6 Viewing and Reattempting Failed Uploads

Use these procedures to view and reattempt to upload the failed uploads.

Related Topics

1.10.7 Oracle Health Check Collections Manager Application Uninstallation

Anytime you can decommission Oracle Health Check Collections Manager Application setup. Follow these steps sequentially to uninstall the application leaving no residual files.

1.10.7.1 Deleting Oracle Health Check Collections Manager Application

You need administrative privileges to uninstall Oracle Health Check Collections Manager Application.

After successful uninstallation, application definition and the supporting objects are deleted from the hosting database.

  1. Log in to Oracle Health Check Collections Manager Application. 
    http://hostname:port/apex
http://hostname:port/pls/apex/
    For example: 
    http://dbserver.domain.com:8080/apex/
  2. Specify the Workspace Name, Workspace Username, and Password, and then click Login.

    Figure 1-146 Application Express Login

    Description of Figure 1-146 follows
    Description of "Figure 1-146 Application Express Login"
  3. Click Application Builder.
  4. Select Collection Manager Application, then click Edit.
  5. Click Edit Application Page.

    Figure 1-147 Application Express - Edit Application

    Description of Figure 1-147 follows
    Description of "Figure 1-147 Application Express - Edit Application"
  6. Click Delete.

    Figure 1-148 Application Express - Delete

    Description of Figure 1-148 follows
    Description of "Figure 1-148 Application Express - Delete"
  7. Choose Deinstallation Options.

1.10.7.2 Deleting Workspace Admin

You need administrative privileges to delete a workspace. There may exist one or more workspaces so be cautious while deleting workspaces.

  1. Log in to Oracle Application Express.
  2. Click Manage Workspaces.
  3. Under Workspace Reports, click Existing Workspaces, and check the Workspace name.

    Figure 1-151 Application Express - Manage Workspaces

    Description of Figure 1-151 follows
    Description of "Figure 1-151 Application Express - Manage Workspaces"
  4. Under Action, click Delete.
  5. Select the check box to confirm that you want to proceed with the removal and then click Next.

    Figure 1-152 Application Express - Confirm Delete

    Description of Figure 1-152 follows
    Description of "Figure 1-152 Application Express - Confirm Delete"
  6. Click Remove Workspace.

    Figure 1-153 Application Express - Remove Workspace

    Description of Figure 1-153 follows
    Description of "Figure 1-153 Application Express - Remove Workspace"

The install process displays the Workspace has been successfully removed message.

Related Topics

1.10.8 Troubleshooting Oracle Health Check Collections Manager

This topic describes how to troubleshoot Oracle Health Check Collections Manager.

Related Topics