Oracle Health Check Collections Manager for Oracle Application Express 20.2

Oracle Health Check Collections Manager is a companion application to Oracle Autonomous Health Framework that gives you an enterprise-wide view of your compliance check collection data.

To install or upgrade APEX, see Oracle APEX Documentation.

Scope and Supported Platforms

Oracle Health Check Collections Manager provides an enterprise-wide repository and dashboard for tracking health check collection data by Business Unit and time, with automated uploads. It requires Oracle Application Express 20.2 or later and supports Oracle Database 11g Release 2 and later, including 12c, 18c, and 19c; XE support is limited to OTN discussion forums.

Prerequisites

Oracle Health Check Collections Manager requires Oracle Database 11g Release 2 or later and Oracle Application Express 20.2 or later.

Installation

Installation involves deploying and configuring Oracle Application Express, creating a dedicated workspace and parsing schema, establishing administrator and end-user accounts, downloading the application package, verifying required database privileges, importing the application SQL script, installing supporting objects, and recording the application ID. After installation, users can access dashboards, filters, sample data, collection uploads, email settings, and configurable themes; upgrades should be performed directly from Oracle Autonomous Health Framework.

Upgrading Oracle Health Check Collections Manager Application

Upgrade the application by downloading the latest package and running the -cmupgrade option through Oracle Orachk or Oracle Exachk. The installed APEX version must meet the application requirement, and the application is unavailable during the upgrade, so failed uploads must be reviewed and retried afterward. Fresh installations must be imported through the APEX framework when indicated.

Getting Started

Initial administration includes customizing incident lookup seed data, enabling Access Control, and assigning Admin, DBA Manager, DBA, or Read Only roles. Administrators can configure Business Units, system assignments, users, incidents, notifications, and retention policies; DBA Managers and DBAs have progressively narrower operational scopes. The page also describes LDAP user capture, bulk XML-based system-to-Business Unit mapping, and daily purging of collections older than three months.

Oracle Health Check Collections Manager Application Features

The application provides global filters and dashboards for system health, failed and warned checks, recent collections, activity, collection scores, and status trends. Users can browse, compare, and report on collections, upload collections manually, ignore or restore checks at authorized scopes, and manage incidents for collections or individual findings. Administrators can create role-controlled incident workflows and author OS- or SQL-based user-defined checks, export them to XML, and run them through Oracle Orachk or Oracle Exachk profiles.

Viewing and Reattempting Failed Uploads

Oracle Orachk and Oracle Exachk record database upload status in check_env.out; a failed status can be identified with the -checkfaileduploads option. Use -uploadfailed with all or a comma-delimited collection list to retry uploads, while previously uploaded collections cannot be uploaded again because of a SQL unique constraint.

Oracle Health Check Collections Manager Application Uninstallation

Administrators can uninstall the application through Oracle Application Express by removing its application definition and deinstalling supporting objects, which deletes related database objects and data. APEX administrators can then remove the associated workspace after verifying its identity, recognizing that workspace deletion may affect other applications and users.

Troubleshooting Oracle Health Check Collections Manager

Common troubleshooting actions include granting UTL_SMTP execution privileges, recreating and validating the APEX WWV_FLOW_EPG_INCLUDE_MOD_LOCAL function, granting access to RCA13_GET_DOC for downloads, restoring APEX configuration and account access, configuring network ACLs for email, checking scheduler jobs and processing logs for collections stuck in NEW, and increasing tablespace capacity when storage is insufficient.

Integrating Collection Manager with Oracle Internet Directory for Authentication

Integrate Oracle Health Check Collections Manager with Oracle Internet Directory by first validating LDAP connectivity with ldapbind, then creating an APEX LDAP Directory authentication scheme with the appropriate host, port, SSL, and distinguished-name settings. Test the configuration with LDAP credentials, make the validated scheme current, and confirm integration by logging in to the application with an LDAP user.
Read More: Integrating Collection Manager with Oracle Internet Directory for Authentication