# Oracle Autonomous Health Framework User's Guide This file contains the text from each Oracle Autonomous Health Framework User's Guide article landing page, release 26.9. # Changes in this Release This preface lists changes in the Oracle Autonomous Health Framework Checks and Diagnostics User's Guide 26.9. # Changes In Previous Releases ## Oracle Autonomous Health Framework 26.8 Release Notes Summary AHF 26.8 completes migration from JKS to PKCS12 certificates and introduces customer CA-signed certificate support, trusted self-signed upload-server certificates, and synchronization requiring bidirectional TCP access on ports 5000–5005 between cluster nodes. SSH host keys are recorded on first contact and validated thereafter, while Base Database Cloud@Customer support adds diagnostic collection and OCI Monitoring integration. The release also delivers more than 50 reliability, performance, and security fixes. Read More: [Oracle Autonomous Health Framework 268 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_268_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 26.5 Release Notes Summary AHF 26.5 strengthens Exachk SSH host-key validation for Exadata cells and switches, automatically runs TFA self-diagnostics after failed collections, and adds cluster-wide diagnostic flood control to reduce redundant bundles and storage use. Orachk and Exachk also introduce checks for enabled Exadata cryptographic policies and critical issues DB56 and DB57. Read More: [Oracle Autonomous Health Framework 265 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_265_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 26.3 Release Notes Summary AHF 26.3 disables Lucene metadata indexing by default on new installations to reduce resource usage, modernizes Windows operations with PowerShell and CIM while retaining WMIC fallback, and extends generated certificate validity to 365 days. Exachk gains a System Overview and adaptive load-aware scheduling, administrators can manage switch configurations securely through the CLI and wallet, and Orachk/Exachk add RMAN destination storage-option validation. Read More: [Oracle Autonomous Health Framework 263 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_263_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 26.2 Release Notes Summary AHF 26.2 adds Exadata Live Update status to Exachk HTML and JSON reports, deriving patching state from image history and grouping nodes by update and reboot requirements. The release also adds the Exadata critical-issue DB55 best-practice check. Read More: [Oracle Autonomous Health Framework 262 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_262_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 26.1 Release Notes Summary AHF 26.1 is the final release supporting HP-UX and adds a RAC netperf profile for measuring interconnect bandwidth. Orachk and Exachk incorporate DBSAT 4.1 security guidance, support configuration updates across multiple base versions, expose per-check execution timings, and automatically select the best configured switch account on KVM Dom0 for data collection. Read More: [Oracle Autonomous Health Framework 261 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_261_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.11 Release Notes Summary AHF 25.11 adds the HugePagesNotUtilized diagnostic signature, selective Exachk output-format generation, structured activity logging with rotation and retention, and activity-specific chronological Alert History analysis. Orachk and Exachk also add checks confirming that ASM and RDBMS DIAGNOSTIC\_DEST locations use local filesystems. Read More: [Oracle Autonomous Health Framework 2511 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2511_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.10 Release Notes Summary AHF 25.10 is a stabilization release featuring JRE 11.0.29, lower memory usage, critical security updates, and more than 180 fixes. Collections now capture selected administrative command history, Insights detects additional eviction and performance problems with recommended resolutions, and Orachk/Exachk add core-dump configuration, invalid-object, and EX93 checks. Read More: [Oracle Autonomous Health Framework 2510 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2510_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.9 Release Notes Summary AHF 25.9 updates Orachk and Exachk with DBSAT 4.0 guidance, simplifies compliance-report retrieval, improves Exadata DomU alert and response-file collection, makes scan-file monitoring configuration-driven, and records OneView collection and upload durations. It also improves OneView database validation and ZIP handling and adds kernel- and user-space core-dump checks. Read More: [Oracle Autonomous Health Framework 259 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_259_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.8 Release Notes Summary AHF 25.8 centralizes excluded compliance-check management, allows multi-node collections to continue when individual repositories are unavailable, expands ODA diagnostics with RMAN logs, and enables PDB collection through the DBTEXTINSTALL SRDC. Platinum users can verify Fleet Insights configuration, Health Check Collections Manager is distributed separately, and Orachk adds standby DB\_BLOCK\_CHECKING validation. Read More: [Oracle Autonomous Health Framework 258 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_258_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.7 Release Notes Summary AHF 25.7 enhances Data Guard Insights with database properties, detailed readiness information, log-switch analysis, and transport-network utilization. Diagnostic collections improve large-file handling, Exachk JSON inclusion, rotated-log inventory, and OneView partial-success reporting; DNFS and ORA-1555 diagnostics become more targeted, collection searches gain filters, Orachk adds private-memory comparison, Python clients gain an AHF-IPC library, and new standby protection checks are included. Read More: [Oracle Autonomous Health Framework 257 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_257_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.6 Release Notes Summary AHF 25.6 introduces an interactive command-line Insights explorer, hourly CHM Inline Analysis that reduces storage while extending OS-metric retention, and resource-limited processing to minimize system impact. Standalone non-root Linux deployments can collect SHM data and generate OS Insights reports, although users must manually manage SHM with sysmonctl and receive reduced metric coverage compared with root installations. Read More: [Oracle Autonomous Health Framework 256 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_256_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.5 Release Notes Summary AHF 25.5 moves upgrade configuration to the newer ahf configuration CLI, reduces Fleet Insights upload payloads, audits cloud TFA opt-in changes, and adds process-count spike detection. Insights and Orachk provide richer process CPU and start-time data plus name-prefix memory grouping, while Orachk adds ASM Filter Driver configuration validation. Read More: [Oracle Autonomous Health Framework 255 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_255_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.4 Release Notes Summary AHF 25.4 delivers the April JRE security update, lower memory usage, and broad reliability fixes. Insights detects increasing process memory usage and recommends resolutions, OneView supports partial ExaDB-C@C and ExaDB-D collections, SRDCs can run on the incident node, and Orachk/Exachk add core-dump, invalid-object, and EX93 best-practice checks. Read More: [Oracle Autonomous Health Framework 254 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_254_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.3 Release Notes Summary AHF 25.3 provides per-node ASM disk-group status, identifies automatic-collection trigger events in the Insights timeline, warns about deprecated CLI usage, and enforces a 15-minute minimum collection window. New diagnostics cover InfiniBand RDS degradation and low-memory differences, while Orachk adds voting-disk-integrity validation. Read More: [Oracle Autonomous Health Framework 253 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_253_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.2 Release Notes Summary AHF 25.2 is a maintenance release with no new features, concentrating on bug fixes and improvements to overall framework reliability and stability. Read More: [Oracle Autonomous Health Framework 252 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_252_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 25.1 Release Notes Summary AHF 25.1 adds Insights analysis for NIC flow-control, memory-growth, RDS/IB, archiver, and redo-log problems with recommended resolutions. The unified CLI can securely manage SSH keys and passwords in the AHF wallet, update configuration is moving from ahfctl to ahf configuration, Oracle Linux 9 supports cgroups v1 and v2 limits, Exadata X11M and System Software 25.1 are supported, and Exachk adds EX92. Read More: [Oracle Autonomous Health Framework 251 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_251_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.11 Release Notes Summary AHF 24.11 adds a limit-db-changes option to AHF Balance so CPU\_COUNT recommendations can be applied gradually at fleet, cluster, or database scope. The feature supports controlled phased tuning and requires Impact analysis connection details; Orachk also adds systemd-udevd CPU-usage validation. Read More: [Oracle Autonomous Health Framework 2411 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2411_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.10 Release Notes Summary AHF 24.10 expands Insights problem detection to I/O errors and UDP-buffer misconfiguration, adds timeline-linked log viewing and in-product feedback, and introduces Orachk checks for tainted kernels and third-party security modules. Exachk adds Live Update validation and critical-issue checks EX89, EX90, and EX91. Read More: [Oracle Autonomous Health Framework 2410 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2410_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.9 Release Notes Summary AHF 24.9 embeds PerfHub, AWR, and AWR Compare reports in Insights and adds detection of CPU-steal, network-buffer, and recovery-block performance problems. Data Guard readiness analysis now covers roles, lag, apply rate, and configuration symmetry; Oracle Database 19c and later can be monitored with configured credentials instead of OS-authenticated SYSDBA; DBSAT 3.1 guidance and several SYS, SYSTEM, profile, and PUBLIC privilege checks are added. Read More: [Oracle Autonomous Health Framework 249 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_249_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.8 Release Notes Summary AHF 24.8 enables shareable Problem Summaries and adds automated detection for several eviction, slowdown, and database-blocking conditions. Insights gains millisecond timelines, tooltips, zooming, improved OS analysis, expanded Data Guard readiness and wait-event views, embedded performance reports, and a faster Virtual DOM interface, while AHF Balance accounts for standby promotion during disaster recovery and Exachk adds DB54. Read More: [Oracle Autonomous Health Framework 248 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_248_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.7 Release Notes Summary AHF 24.7 allows Exadata Dom0, storage-server, and switch credentials to be stored in the AHF wallet for more complete compliance analysis and Platinum automation. SQL Agent connection pooling improves checks with SQL\*Plus fallback, JRE patches can be managed independently, HAMI traces can be managed through tfactl, and Insights adds remediation guidance for storage shortages, MTU errors, and failed network interfaces. Read More: [Oracle Autonomous Health Framework 247 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_247_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.6 Release Notes Summary AHF 24.6 expands Insights detection for HugePages, process-memory, startup, multipath, archiving, and target\_pdbs issues, with richer evidence and configuration context in Problem Summaries. It adds first-failure metrics for standalone databases, installer preservation for downgrade, component-based event grouping, default SHM integration for single-instance systems, and Exachk checks EX88 and DB53. Read More: [Oracle Autonomous Health Framework 246 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_246_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.5 Release Notes Summary AHF 24.5 adds fleet-level AHF Balance reports for Enterprise Manager groups, optional size-based trace filtering for smaller collections, and comprehensive Data Guard Health Reports. It introduces configurable first-failure system metrics, automatic Dom0 discovery, a dedicated report Security section, and checks for patch metadata, Data Guard lag, and failover or switchover readiness. Read More: [Oracle Autonomous Health Framework 245 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_245_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.4 Release Notes Summary AHF 24.4 integrates with Oracle AI Database 26ai, detects HugePages-related node evictions, supports downgrade to a recent prior release while preserving configuration and event data, and automatically collects diagnostics for selected database hangs. Insights generation is faster and more accessible, Oracle provides ORA-04030 Fix Flow guidance, and Orachk/Exachk add obsolete-patch and Unified Audit Trail tablespace checks. Read More: [Oracle Autonomous Health Framework 244 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_244_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.3 Release Notes Summary AHF 24.3 adds Fix Flow guidance for ORA-04031 and ORA-07445, extends GoldenGate compliance checks to Microservices Architecture, and improves Insights accessibility. The unified CLI gains tag, upload, repository, Fleet Insights, and JSON-output capabilities; new checks cover orphaned ASM files, grid-inventory nodes, EX85, and GoldenGate-related configurations. Read More: [Oracle Autonomous Health Framework 243 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_243_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.2 Release Notes Summary AHF 24.2 expands tfactl purge cleanup options, supports single-archive collections, broadens the unified ahf CLI with data operations, and extends diagnostics to Exadata Netdiag and Audit Vault Server. Collections now include Insights reports by default and support single-instance Linux, while the release adds ORA-00600 and TFA collection recovery guidance and updates dependencies to address CVEs. Read More: [Oracle Autonomous Health Framework 242 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_242_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 24.1 Release Notes Summary AHF 24.1 adds ASR client-log collection, JSON collection reporting, improved Orachk/Exachk comparison, RAC Extended Cluster compliance, richer Insights event and disk-space analysis, and terminal-release notices for older operating systems. It deprecates manual mask\_strings.xml masking in favor of ACR, updates security dependencies, and adds loopback-MTU plus Exachk EX83 and EX84 checks. Read More: [Oracle Autonomous Health Framework 241 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_241_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.11 Release Notes Summary AHF 23.11 upgrades Java to 11.0.21, introduces tfactl param, and adds the Database Anomalies Advisor. It supports Oracle Linux 9 on x86\_64 and Arm, provides visual diagnostic-space analytics, displays ExaWatcher metrics in Insights, and enhances timelines with patch events, database filtering, standardized metric precision, and improved node sorting. Read More: [Oracle Autonomous Health Framework 2311 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2311_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.10 Release Notes Summary AHF 23.10 enables Exadata cell-metric collection for guest VMs, custom upload ports, additive compliance profiles, and Insights analysis windows up to 12 hours with adaptive sampling. OS Issues analysis, GoldenGate time-range collection, and platform lifecycle guidance are improved, while Exachk adds startup, inactive-patch, EX80–EX82, and DB52 checks. Read More: [Oracle Autonomous Health Framework 2310 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_2310_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.9 Release Notes Summary AHF 23.9 improves compliance-scheduler control, audit-dump cleanup, automatic-update configuration, and Insights-enabled collection efficiency. CVU reports are collected explicitly and by default with CRS and database collections, while new Orachk checks cover ODA, ADVM, and printk settings and Exachk checks RoCE cabling, cluster limits, and unsupported DSA authentication. Read More: [Oracle Autonomous Health Framework 239 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_239_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.8 Release Notes Summary AHF 23.8 integrates Orachk and Exachk compliance results into Insights with scoring, search, and filtering, while improving usability, anomaly visualization, and restricted-environment operation. Insights reports can be uploaded or scheduled, AHF Balance analyzes CPU overcommitment without requiring a GI home, and new checks cover dictionary health, auditing, GridDisk caching, and kernel taint. Read More: [Oracle Autonomous Health Framework AHF 238 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_238_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.7 Release Notes Summary AHF 23.7 adds patch inventories and timelines to Insights, improves mobile presentation, simplifies Exadata Dom0 upgrades and data-directory defaults, and accelerates ACR redaction through configurable CPU limits and process counts. Orachk also adds validation for inactive patches in Grid Infrastructure and database homes. Read More: [Oracle Autonomous Health Framework AHF 237 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_237_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.6 Release Notes Summary AHF 23.6 introduces aggregated NIC and cross-host process views, supports uncached Insights refreshes, adds Exadata X10M and ARM support, and allows the AHF data directory to be moved without reinstallation. Orachk also validates inactive database-home patches. Read More: [Oracle Autonomous Health Framework AHF 236 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_236_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.5 Release Notes Summary AHF 23.5 enhances Insights with anomaly annotations, system and cluster-wide resource views, and configuration summaries while reducing report size and rendering time. It adds queued-collection visibility, nested ZIP content inspection, and size-based compliance-result cleanup. Read More: [Oracle Autonomous Health Framework AHF 235 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_235_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.4 Release Notes Summary AHF 23.4 extends Insights to ODA and generic RAC, adds JSON-capable system-change tracking and collection-status filtering, and supports JSON Orachk email attachments. The unified CLI gains MRP, fleet-analysis, and refresh functions, while new best-practice checks cover AHF Balance resource contention, listener and Clusterware configuration, KMS encryption, and instance naming. Read More: [Oracle Autonomous Health Framework AHF 234 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_234_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.3 Release Notes Summary AHF 23.3 allows Platinum users to run approved database SRDCs without database DBA-group membership, adds unified CLI commands for viewing and comparing Monthly Recommended Patch levels, and introduces Orachk checks for long-term-release bug fixes. Exachk adds validation for cloud-registration links, TDE wallets, and SYS-based TNS configuration and connectivity. Read More: [Oracle Autonomous Health Framework AHF 233 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_233_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.2 Release Notes Summary AHF 23.2 renames Intelligent Workload Advisor to AHF Balance while retaining its resource-contention and noisy-neighbor analysis capabilities. Exachk adds long-term-release bug-fix validation and the EX78 critical-issue check. Read More: [Oracle Autonomous Health Framework AHF 232 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_232_release_notes_summary.md?ref_type=heads) ## Oracle Autonomous Health Framework 23.1 Release Notes Summary AHF 23.1 introduces an Undetermined status for checks that cannot run reliably, preventing misleading failures, and adds compliance comparisons highlighting unique, different, and common values. AHFCTL gains JSON output, SQL Agent uses connection pooling to reduce overhead and audit activity, and new checks address Enterprise Manager status, long-term-release fixes, password-file sharing, CPU oversubscription, VM configuration, cloud filesystems, and DB service agents. Read More: [Oracle Autonomous Health Framework AHF 231 Release Notes Summary](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/changes_in_previous_releases/26.9/oracle_autonomous_health_framework_ahf_231_release_notes_summary.md?ref_type=heads) # Overview Oracle Autonomous Health Framework is a collection of components that analyzes the diagnostic data collected, and proactively identifies issues before they affect the health of your clusters or your Oracle Real Application Clusters (Oracle RAC) databases. Most of the Oracle Autonomous Health Framework components are already available in Oracle Database 12c release 1 (12.1). ## Oracle Autonomous Health Framework Problem and Solution Space Oracle Autonomous Health Framework improves availability and performance by applying best practices, collecting first-failure data, monitoring servers, databases, I/O, and networks, detecting emerging issues, notifying administrators, and recommending corrective actions. It addresses server availability threats such as interconnect congestion or failures through CVU, Cluster Health Advisor, Cluster Health Monitor, and TFA; database availability problems such as resource contention, attacks, defects, and configuration errors through Blocker Resolver, Orachk, CVU, TFA, and diagnostic monitoring; and performance problems caused by configuration deviations, blocked sessions, unpatched defects, or client resource settings through Orachk, Blocker Resolver, and Cluster Health Advisor. Read More: [Oracle Autonomous Health Framework Problem And Solution Space](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/overview/oracle-autonomous-health-framework-problem-and-solution-space.html) ## Components of Autonomous Health Framework Oracle Autonomous Health Framework includes Orachk and Exachk for proactive health, compliance, configuration, and known-issue checks; Oracle Trace File Analyzer for automated, targeted first-failure diagnostic collection; database attention logs for structured administrator-focused events; AHF Insights for offline, consolidated reports covering configuration, topology, metrics, logs, anomalies, root causes, and recommended fixes; Cluster Health Advisor for continuous model-based monitoring, early warnings, diagnoses, corrective actions, calibration, and historical analysis; AHF Scope for interactive real-time or archived CHA analysis, though it is deprecated in Oracle AI Database 26ai; AHF Balance for analyzing cluster CPU consumption and recommending Database Resource Manager settings; Cluster Health Monitor for recording cluster and operating-system metrics; and Blocker Resolver for detecting and automatically resolving database delays and deadlocks. Read More: [Components of Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/overview/components-of-autonomous-health-framework.html) # Get Started Learn about supported platforms, prerequisites, installation and lifecycle management, and how to start using Oracle Autonomous Health Framework (AHF). ## Supported Platforms Oracle Autonomous Health Framework supports supported Oracle Database and Grid Infrastructure versions across engineered systems, including Oracle Database Appliance, Exadata, and Zero Data Loss Recovery Appliance. Supported operating systems include Linux OEL, Red Hat, SUSE, zLinux, Solaris SPARC and x86-64, AIX, HP-UX, and 64-bit Microsoft Windows, with stated Java requirements and platform-specific limitations. AHF 23.9.0 and later no longer support Solaris 10, Solaris Intel, AIX 6.x, or RHEL/OEL 6; terminal releases remain available for certain legacy platforms through the applicable Oracle support bundle. Read More: [Supported Platforms](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/supported-platforms.html) ## Recommended Browsers Oracle Orachk and Oracle Exachk HTML reports are best viewed using the latest release and five preceding versions of Microsoft Internet Explorer, Microsoft Edge, Google Chrome, Mozilla Firefox, or Apple Safari. Read More: [Recommended Browsers](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/recommended-browsers.html) ## Scope of Oracle Stack Supported Oracle Autonomous Health Framework performs proactive compliance checks across Oracle hardware, databases, Grid Infrastructure, RAC, engineered systems, middleware, applications, Enterprise Manager, identity and access management, Solaris and storage systems, Siebel, PeopleSoft, GoldenGate, Application Continuity, and MAA or upgrade-readiness configurations. Its supported product scope expands with new AHF releases. Read More: [Scope of Oracle Stack Supported](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/scope-of-oracle-stack-supported.html) ## Compliance Framework Oracle Orachk and Oracle Exachk Prerequisites Oracle Orachk and Oracle Exachk can operate with locked Exadata storage servers by using ExaCLI and a temporary access window, normally lasting 50 minutes and automatically closing or expiring after execution; permanent remote-login restrictions remain unchanged. Passwordless SSH equivalency can simplify checks against storage servers and InfiniBand switches, while ExaCLI credentials or switch passwords may be requested when equivalency is unavailable. On Exadata and Zero Data Loss Recovery Appliance, cells can be explicitly unlocked or locked and the timeout adjusted. Non-English environments require the NLS\_LANG globalization setting, although AHF itself supports English only. Read More: [Compliance Framework Oracle Orachk and Oracle Exachk Prerequisites](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/compliance-framework-oracle-orachk-and-oracle-exachk-prerequisites.html) ## Oracle Trace File Analyzer Prerequisites Oracle Trace File Analyzer requires a range of standard Perl modules, including file, process, networking, JSON, threading, and Windows-specific modules. Administrators can use perldoc to verify whether a module is installed and to inspect its version; missing modules are indicated when no documentation or module is found. Read More: [Oracle Trace File Analyzer Prerequisites](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/oracle-trace-file-analyzer-prerequisites.html) ## Installing Oracle Autonomous Health Framework Oracle Autonomous Health Framework can be installed on Linux, Unix, and Microsoft Windows, with full installers shipping Java 11 beginning in version 23.7.0. Cluster installations performed with the local option require identical AHF home and data-directory paths on every node, including nodes added later. Read More: [Installing Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-oracle-autonomous-health-framework.html) ## Prerequisites for Configuring Oracle Autonomous Health Framework AHF configuration requires at least 3 GB of free space for the software directory, 5 GB for the data directory, and 2 GB for /tmp. Additional data-directory capacity is recommended for large clusters, numerous databases, or extended retention of reports and diagnostic collections. Read More: [Prerequisites for Configuring Oracle Autonomous Health Framework](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/get_started/26.9/prerequisites_for_configuring_oracle_autonomous_health_framework.md?ref_type=heads) ## Installing AHF on Linux Installing AHF as root provides full capabilities, daemon operation, automated scheduling, ACL-based diagnostic access, and cluster deployment support; Perl 5.10 or later is required. Non-root installations are limited to local, non-daemon operation and cannot automate collections, gather remote diagnostics, or read protected files. The installer supports upgrades, optional standalone TFA configuration, platform-specific auto-start services, and SELinux policy loading or removal when security enforcement changes. Read More: [Installing AHF on Linux](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-ahf-on-linux.html) ## Installing AHF on a Single-Instance System On a single-instance system, the first execution of tfactl, ahfctl, or orachk initiates AHF installation; administrators can monitor progress with tfactl print status and verify the completed deployment with tfactl or ahfctl status commands. Subsequent command executions use the installed binaries directly, and the status output confirms TFA operation, version, build, and inventory completion. Read More: [Installing AHF on a Single-Instance System](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-ahf-on-a-single-instance-system.html) ## Installing AHF on Microsoft Windows On Microsoft Windows, AHF installs TFA as a Windows service while Orachk and Exachk run on demand. Installation requires an administrator command prompt, a supported Perl distribution, and .NET Framework 4.0.30319 or later; paths containing spaces are prohibited. MOS upload and notification email features are unavailable, and cluster deployments require local installation on each host followed by tfactl syncnodes. Read More: [Installing AHF on Microsoft Windows](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-ahf-on-microsoft-windows.html) ## Installing AHF on Oracle Big Data Appliance On Oracle Big Data Appliance, download the AHF archive as root to a local appliance directory and run ahf\_setup with the desired installation location, optionally using extract mode. Additional installer guidance is available through the setup help option. Read More: [Installing AHF on Oracle Big Data Appliance](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-ahf-on-oracle-big-data-appliance.html) ## Installing AHF on Oracle Exadata Dom0 AHF on Exadata dom0 supports standalone extraction, typical installation with TFA and Exachk scheduling, local scheduler installation followed by certificate synchronization, or recommended multi-node deployment using the scheduler and nodes options. Cell and node synchronization can use SSH passwords or sockets, while standalone installations can be converted to typical mode; installations should account for shared data locations and dom0 resource management. Read More: [Installing AHF on Oracle Exadata Dom0](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/installing-ahf-on-oracle-exadata-dom0.html) ## Group Permissions for Oracle Exachk Results Directories and Files On non-Windows systems, AHF derives a default operating-system group from osdbagrp and applies group permissions to Exachk result directories and files: typically 750 for directories and 640 for uploaded JSON files. The configured group applies to the user\_root, output, and upload areas and can be changed or inspected with ahfctl setosgroup and ahfctl getosgroup. Read More: [Group Permissions for Oracle Exachk Results Directories and Files](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/group-permissions-for-oracle-exachk-results-directories-and-files.html) ## Configure MOS Upload While Installing or Upgrading AHF MOS upload configuration during AHF installation or upgrade is controlled by the setupmos and nosetupmos options. Without either option, the installer prompts for configuration; setupmos forces collection of MOS name, credentials, and URL; and nosetupmos suppresses the prompt. Cluster-wide configurations are synchronized automatically, and ahfctl getupload verifies the resulting settings. Read More: [Configure MOS Upload While Installing or Upgrading AHF](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/configure-mos-upload-while-installing-or-upgrading-ahf.html) ## Upgrading Oracle Autonomous Health Framework AHF can be upgraded with ahf\_setup, which updates existing installations and uses established secure cluster communication, while monthly releases and support-tool bundles should be obtained from Oracle’s current distribution source. AutoUpgrade is available on Linux, Solaris, and AIX when OpenSSL is present, but not on HP-UX, Windows, or most standalone extract installations. Administrators can configure, inspect, disable, or remove automatic upgrades with ahfctl commands, using local, ACFS, NFS, REST, or object-storage staging locations; scheduler-based upgrades preserve saved configuration. Read More: [Upgrading Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/upgrading-oracle-autonomous-health-framework.html) ## Patching Oracle Autonomous Health Framework AHF metadata and framework patches can be downloaded and applied automatically or on demand by users with AHF installation privileges. The ahfctl update, setupdate, getupdate, unsetupdate, applyupdate, queryupdate, rollbackupdate, and deleteupdatebackup commands configure update sources and frequency, apply ZIP packages, inspect update status, revert selected updates, and remove obsolete backups. Updates must be applied on every cluster node, and backups should be deleted cautiously because doing so removes rollback capability. Read More: [Patching Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/patching-oracle-autonomous-health-framework.html) ## Running AHFCTL Update Commands to Apply AHF Metadata and Framework Updates The update-management commands apply metadata and framework ZIP updates to individual nodes, with installation-user privileges required and cluster administrators responsible for repeating operations across all nodes. ahfctl applyupdate replaces local files from a specified package, queryupdate reports applied updates by identifier or in full JSON-formatted listings, rollbackupdate restores a prior state, and deleteupdatebackup removes selected historical backups while preserving the current rollback point. Read More: [Running AHFCTL Update Commands to Apply AHF Metadata and Framework Updates](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/get_started/26.9/running_ahfctl_update_commands_to_apply_ahf_metadata_and_framework_updates.md?ref_type=heads) ## Downgrading Oracle Autonomous Health Framework AHF supports downgrading to the previously upgraded version when that version is less than six months old, preserving configuration and event data through an export, binary replacement, and import process. Administrators can identify and validate a downgrade installer before using ahf\_setup, or invoke ahf software downgrade when a saved installer is available; properties added after an upgrade may need to be reconfigured, while modified existing properties are retained. Read More: [Downgrading Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/downgrading-oracle-autonomous-health-framework.html) ## Uninstalling Oracle Autonomous Health Framework Running ahfctl uninstall as root or the installation user stops Orachk and TFA and removes the AHF installation directory. The deleterepo and silent options can remove the repository without confirmation, and cluster output identifies the nodes being processed before service, binary, configuration, data, and repository components are deleted. Read More: [Uninstalling Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/uninstalling-oracle-autonomous-health-framework.html) ## Start Using Oracle Autonomous Health Framework This page introduces key Oracle Autonomous Health Framework directories, including installation, binaries, component homes, configuration data, diagnostic repositories, and host logs. It explains how to configure shared or component-specific notification addresses for Trace File Analyzer, Orachk, and Exachk; use the tfactl command-line, shell, and menu interfaces; manage Trace File Analyzer with systemctl or tfactl; and control Orachk/Exachk scheduler behavior with autostart, autostop, reset, and unset options, including the changes introduced in AHF 23.9. It also documents AHF 26.1 Exachk switch-user selection on KVM Dom0, where users are evaluated in the priority order dbadmin, switchexa, root, and admin based on equivalency or wallet credentials, with interactive prompting or silent-mode fallback when complete access is unavailable. Read More: [Start Using Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/get-started/start-using-oracle-autonomous-health-framework.html) # Compliance Checking with Oracle Orachk and Oracle Exachk Oracle Orachk and Oracle Exachk share a common compliance check framework and a large portion of their features and tasks are common. ## Getting Started with Running Compliance Checks Oracle Orachk and Oracle Exachk support non-root execution, including authorized root-privileged checks through TFA access roles, direct access to user-specific repositories, scheduled and on-demand compliance assessments, remote synchronous or asynchronous runs using passwordless SSH, custom check profiles, sensitive-data redaction through ACR, automated problem repairs, DBSAT security assessments, AutoUpgrade readiness checks, and enhanced activity logging. TFA manages scheduled cluster-wide runs, notifications, retention, and master-node coordination, while reports provide health scores, findings, recommendations, comparisons, and MAA scorecards. A dynamic load-aware Exachk scheduler can additionally recommend lower-impact execution windows based on system telemetry. Read More: [Getting Started with Running Compliance Checks](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/getting-started-with-running-compliance-checks.html) ## Running Compliance Checks Automatically Oracle Orachk and Oracle Exachk daemon mode, supported on Linux and Solaris, automates recurring checks, notifications, collection purging, password validation, multiple scheduling profiles, and restart behavior. Administrators configure schedules, run flags, recipients, retention periods, password-check intervals, and profile-specific settings with `-set`, inspect them with `-get` or `-autostatus`, and manage execution with `-autostart`, `-autostop`, and optional monthly or randomized run windows. The daemon can be configured for automatic startup and reboot recovery, while status commands show scheduler details and the next run; on-demand checks may use or bypass the daemon, and reports can be emailed directly. Read More: [Running Compliance Checks Automatically](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/running-compliance-checks-automatically.html) ## Running Compliance Checks On-Demand On-demand Oracle Orachk and Oracle Exachk runs assess system health outside scheduled intervals, including before or after upgrades, after hardware or network changes, during troubleshooting, and for go-live validation. The tools discover components, evaluate SSH equivalency, collect local and remote data, handle required credentials interactively or through the daemon and Expect utility, execute checks, and provide HTML and ZIP output locations. Pre- and post-upgrade modes use `-u -o pre` or `-u -o post`, while `-nodaemon` forces independent interactive execution; results can be emailed with `-sendemail`, and runtime depends on cluster size, database topology, hardware, and workload. Read More: [Running Compliance Checks On-Demand](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/running-compliance-checks-on-demand.html) ## Running Compliance Checks in Silent Mode Silent mode provides legacy automated compliance execution for backward compatibility and is less capable than daemon mode. The `-s` option runs silent checks, including root-dependent checks when executed with appropriate privileges, but excludes storage-server and switch checks; `-S` additionally excludes database checks requiring root access. Passwordless SSH is needed for remote collection, while local single-instance checks may not require it. Silent-mode output resembles on-demand reports, and engineered-system storage or InfiniBand checks require suitable environment configuration. Read More: [Running Compliance Checks in Silent Mode](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/running-compliance-checks-in-silent-mode.html) ## Understanding and Managing Reports and Output Oracle Orachk and Oracle Exachk use configurable temporary and output directories, with locations controlled by RAT\_TMPDIR, RAT\_ROOT\_SH\_DIR, RAT\_OUTPUT, and related options. Generated collections include logs, scripts, reports, upload data, HTML output, and ZIP archives containing health scores, findings, recommendations, security results, MAA assessments, skipped checks, timing data, and platform-specific sections. Reports can be tagged, filtered, compared, merged, selectively hidden, or generated in chosen formats; file-attribute snapshots support baseline tracking and change detection. Output growth can be managed through RAT\_PURGE\_SIZE, COLLECTION\_RETENTION, or manual cleanup, while Exachk additionally supports format-specific collections, Exadata Live Update status, and structured System Overview data for Exadata environments. Read More: [Understanding and Managing Reports and Output](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/understanding-and-managing-reports-and-output.html) ## Compare Configuration Across Two Different Systems Oracle Orachk and Oracle Exachk can compare configuration data from two different systems, such as primary and standby, test and production, or healthy and unhealthy environments. Run the checks on both systems, then use the -diff option with their collection ZIP files; adding -force and -showallcomparison compares all applicable database servers, storage servers, switches, ASM, patches, and other discovered targets. The resulting report identifies differing values, system-specific values, and common configurations. Read More: [Compare Configuration Across Two Different Systems](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/compare-configuration-across-two-different-systems.html) ## Running Subsets of Checks Oracle Orachk and Oracle Exachk support targeted compliance runs through upgrade-readiness modes, component-selection options, profiles, individual check IDs, and failed-check reruns. Pre-upgrade and post-upgrade modes assess Oracle Clusterware, databases, and operating systems, while options such as -dball, -dbnone, -dbnames, -pdbnames, -clusternodes, -localonly, -cell, and -ibswitches restrict checks to selected resources. Profiles run, include, or exclude logical check groups; individual checks can be selected or persistently excluded, and -failedchecks reruns only checks that failed in a previous result. The tools also support standalone Grid Infrastructure checks, privileged-user identification, and the netperf profile for RAC network bandwidth testing. Read More: [Running Subsets of Checks](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/running-subsets-of-checks.html) ## Understanding Oracle Exachk specifics for Oracle Exadata and Zero Data Loss Recovery Appliance Oracle Exachk operation on Oracle Exadata and Zero Data Loss Recovery Appliance depends on interface selection, virtualization, execution privileges, collection mode, and component access. Management interfaces can be selected with -clusternodes, while virtualized environments require root execution in DOM0 for hardware and operating-system checks and separate runs in applicable DOMU clusters. Data collection can be made serial through component-specific environment variables, and role-separated environments may require installations on multiple database servers followed by report merging. Alternative storage-server and InfiniBand switch users can be configured, with reduced checks based on privileges; troubleshooting guidance covers unsupported environments causing RC-003 and expected execution times. Read More: [Understanding Oracle Exachk specifics for Oracle Exadata and Zero Data Loss Recovery Appliance](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/understanding-oracle-exachk-specifics-for-oracle-exadata-and-zero-data-loss-recovery-appliance.html) ## Integrating Compliance Check Results with Other Tools Oracle Orachk and Oracle Exachk results can be integrated with Oracle Enterprise Manager, third-party analytics platforms, syslog, and custom applications. Enterprise Manager integrations provide compliance standards, dashboards, target views, violations, scores, and drill-down access to individual checks, while JSON files in each collection’s upload directory support filtering and visualization in tools such as Elasticsearch and Kibana. Results can also be uploaded to centralized database tables for collections, compliance findings, and patch data; upload status is recorded in check\_env.out, failed uploads can be listed and retried, and successfully uploaded collections cannot be duplicated because of database uniqueness constraints. Read More: [Integrating Compliance Check Results with Other Tools](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/integrating-compliance-check-results-with-other-tools.html) ## Using Oracle Orachk to Confirm System Readiness for Implementing Application Continuity Oracle Orachk provides Application Continuity readiness checking to support transparent deployment, but beginning with Oracle Database 19.10, the Application Continuity Protection Check replaces the legacy orachk acchk command. Read More: [Using Oracle Orachk to Confirm System Readiness for Implementing Application Continuity](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/using-oracle-orachk-to-confirm-system-readiness-for-implementing-application-continuity.html) ## Running Oracle ZFS Storage Appliance Compliance Checks Oracle Orachk can assess one or more Oracle ZFS Storage Appliances using the -zfssa option, with appliance names supplied individually or as a comma-separated list for multiple targets. Read More: [Running Oracle ZFS Storage Appliance Compliance Checks](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/running-oracle-zfs-storage-appliance-compliance-checks.html) ## Using Oracle Exachk on Oracle Big Data Appliance Oracle Exachk for Oracle Big Data Appliance versions later than 2.0.1 audits CPU, hardware, firmware, BIOS, operating-system settings, network switches, memory, disks, and installed software to assess appliance health and recommend corrective actions. Run it after deployment, before and after environmental changes, and at least quarterly, preferably during low system load. From node1, run as root; use `exachk -h` to view options and `exachk -a` to perform all supported checks, including best-practice recommendations. Review FAIL, WARNING, and INFO statuses to prioritize remediation. For switch communication timeouts, increase the SSH timeout with `export RAT_PASSWORDCHECK_TIMEOUT=40` and rerun `exachk -a`; consult My Oracle Support for unresolved issues and known problems. Read More: [Using Oracle Exachk on Oracle Big Data Appliance](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/using-oracle-exachk-on-oracle-big-data-appliance.html) ## Easily Manage Cell Switches Databases and exacli Passwords Oracle Autonomous Health Framework provides commands for managing Exadata cell, switch, database, and exacli passwords. The `tfactl setpassword`, `checkpassword`, and `unsetpassword` commands are deprecated from AHF 21.1, so new configurations should use the corresponding `ahfctl` commands. The deprecated `setpassword` syntax supports selecting nodes, databases, users, and exacli credentials through the `-nodes`, `-dbs`, `-user`, and `-exacli` options. Read More: [Easily Manage Cell Switches Databases and exacli Passwords](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/easily-manage-cell-switches-databases-and-exacli-passwords.html) ## Using the exadcli Utility to Collect Cell Metric Data for Guest VMs The `exadcli` utility runs ExaCLI commands across remote nodes identified by host name or IP address to collect cell metrics for guest VMs on cloud systems. Before use, accept each cell or database node’s identity certificate with ExaCLI, save authentication cookies, install Java 1.8 or later, and set `JAVA_HOME`; cookies remain valid for 24 hours and may need renewal after upgrades or certificate changes. Run `exachk -profile workload-capacity` to collect metrics, which are written to `capacity_exadcli.out` in the Oracle Exachk collection directory. Read More: [Using the exadcli Utility to Collect Cell Metric Data for Guest VMs](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/using-the-exadcli-utility-to-collect-cell-metric-data-for-guest-vms.html) ## Query AHF Message Codes to Understand More About the Context and Next Steps AHF message codes provide additional context and recommended next steps for Oracle Orachk and Oracle Exachk findings. Locate the four-digit code in the JSON results file, then query it from the AHF installation directory with `$AHF_HOME/bin/oerr AHF `, such as `$AHF_HOME/bin/oerr AHF 4040`, and review the returned guidance. Read More: [Query AHF Message Codes to Understand More About the Context and Next Steps](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/query-ahf-message-codes-to-understand-more-about-the-context-and-next-steps.html) ## Improved Resource Usage During Compliance Checking Oracle Orachk and Oracle Exachk improve compliance-check efficiency through the SQL Agent, a daemon that maintains reusable database connection pools. If the SQL Agent fails, the tools automatically use SQL\*Plus, creating a new connection for each query. To troubleshoot connection errors, unexpected results, or possible false positives or negatives associated with the SQL Agent, bypass it with `orachk -use_sqlplus` or `exachk -use_sqlplus`; if problems continue, provide the relevant logs and output to My Oracle Support. Read More: [Improved Resource Usage During Compliance Checking](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/compliance-checking-with-oracle-orachk-and-oracle-exachk/improved-resource-usage-during-compliance-checking.html) # 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. Read More: [Scope and Supported Platforms](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/scope-and-supported-platforms.html) ## Prerequisites Oracle Health Check Collections Manager requires Oracle Database 11g Release 2 or later and Oracle Application Express 20.2 or later. Read More: [Prerequisites](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/prerequisites.html) ## 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. Read More: [Installation](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/installation.html) ## 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. Read More: [Upgrading Oracle Health Check Collections Manager Application](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/upgrading-oracle-health-check-collections-manager-application.html) ## 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. Read More: [Getting Started](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/getting-started.html) ## 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. Read More: [Oracle Health Check Collections Manager Application Features](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/oracle-health-check-collections-manager-application-features.html) ## 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. Read More: [Viewing and Reattempting Failed Uploads](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/viewing-and-reattempting-failed-uploads.html) ## 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. Read More: [Oracle Health Check Collections Manager Application Uninstallation](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/oracle-health-check-collections-manager-application-uninstallation.html) ## 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. Read More: [Troubleshooting Oracle Health Check Collections Manager](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/troubleshooting-oracle-health-check-collections-manager.html) ## 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](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oracle-health-check-collections-manager-for-oracle-application-express-20.2/integrating-collection-manager-with-oracle-internet-directory-for-authentication.html) # Collect Diagnostic Data Collect and manage diagnostic data, configure automatic and on-demand collections, monitor system and operating system metrics, and manage Oracle Database and Oracle Grid Infrastructure logs using Oracle Autonomous Health Framework (AHF). ## Managing and Configuring Oracle Trace File Analyzer This section introduces management and configuration of Oracle Trace File Analyzer, covering its daemon, diagnostic collections, and repository administration. Read More: [Managing and Configuring Oracle Trace File Analyzer](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-and-configuring-oracle-trace-file-analyzer.html) ## Querying Oracle Trace File Analyzer Status and Configuration Use the `tfactl print` command to inspect TFA status and configuration, including automatic collection, file trimming, repository size, trace verbosity, automatic purging, collection retention age, and alert-log scanning thresholds. Read More: [Querying Oracle Trace File Analyzer Status and Configuration](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/querying-oracle-trace-file-analyzer-status-and-configuration.html) ## Managing the Oracle Trace File Analyzer Daemon TFA starts automatically with the operating system through platform-specific init or service mechanisms; administrators can manually start or stop it with `tfactl start` and `tfactl stop`, and control automatic restart behavior with `tfactl enable` and `tfactl disable`. Read More: [Managing the Oracle Trace File Analyzer Daemon](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-the-oracle-trace-file-analyzer-daemon.html) ## Managing the Repository TFA stores diagnostic collections in a repository governed by configurable size and location limits. Automatic purging, enabled by default, removes eligible collections from largest to smallest when disk space or repository thresholds are reached, while administrators can configure retention age, purge behavior, location, and maximum size or manually inspect and purge collections with repository and collection commands. Read More: [Managing the Repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-the-repository.html) ## Managing Collections Collection management includes configuring directories and access policies, controlling file trimming and core-file size limits, explicitly including cores in collections, and temporarily blacking out automatic collections for selected targets or events, including resources being provisioned. Read More: [Managing Collections](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-collections.html) ## Configuring the Host Host configuration requires root or sudo access and supports viewing, adding, removing, and synchronizing cluster hosts and their authentication certificates. New hosts are integrated with `tfactl syncnodes`, while existing synchronized certificates can be used with `tfactl host add`; default certificates may be replaced with self-signed or CA-signed certificates. Read More: [Configuring the Host](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/configuring-the-host.html) ## Configuring the Ports Cluster TFA daemons communicate securely through ports 5000–5005 by default. Administrators can assign a primary port or up to five sequential ports with `tfactl set port`, then restart TFA on every node to apply the changes. Read More: [Configuring the Ports](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/configuring-the-ports.html) ## Configuring SSL and SSL Certificates TFA secures cluster communication with TLS protocols, restricts obsolete protocols, and supports configurable cipher suites plus self-signed or CA-signed certificates. Administrators can inspect and restrict protocols, create or import certificates and keystores, protect keystore permissions, apply settings with `tfactl set sslconfig`, and restart TFA; the default cipher suite can also be replaced with a JRE 1.8-supported suite. Read More: [Configuring SSL and SSL Certificates](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/configuring-ssl-and-ssl-certificates.html) ## Configuring Email Notification Details Configure notification addresses globally or per operating-system owner and define SMTP host, authentication, security, sender, recipient, and debugging parameters with `tfactl set smtp`. Use `tfactl print smtp` to review settings and `tfactl sendmail` to validate delivery before relying on automatic collection notifications. Read More: [Configuring Email Notification Details](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/configuring-email-notification-details.html) ## Managing the Index TFA uses Lucene indexes for diagnostic and telemetry metadata. Trace-file metadata indexing is disabled by default beginning with AHF 25.2, while telemetry index corruption can be handled in recreate mode for faster recovery with possible data loss or restore mode, which preserves data through backups and redo at the cost of additional resources and recovery time. Read More: [Managing the Index](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-the-index.html) ## Using Automatic Diagnostic Collections TFA monitors database and Clusterware logs for significant errors and events, consolidates trimmed diagnostics from cluster nodes, stores the results in its repository, and can notify recipients or upload collections for support. Automatic collection is enabled by default, uses a delay and event coalescing window to avoid duplicate collections, supports Cluster Health Advisor events, offers masking or sanitization of sensitive data, and provides flood-control settings to limit repeated collections. Read More: [Using Automatic Diagnostic Collections](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/using-automatic-diagnostic-collections.html) ## Collecting Diagnostics and Analyzing Logs On-Demand The `tfactl` interface provides consistent access to Oracle diagnostic tools and supports on-demand collections when an issue is identified. TFA gathers relevant data for a specified period, trims files for diagnosis, and packages the results on the node where the command is executed. Read More: [Collecting Diagnostics and Analyzing Logs On-Demand](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/collecting-diagnostics-and-analyzing-logs-on-demand.html) ## Viewing System and Cluster Summary The `tfactl summary` command provides a real-time overview of system and cluster status, with additional syntax guidance available through `tfactl summary -help`. Read More: [Viewing System and Cluster Summary](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/viewing-system-and-cluster-summary.html) ## Investigating Logs for Errors Use `tfactl analyze` to search cluster-wide logs for recent errors over a specified hours-or-days interval or to find occurrences of a particular error, such as `ORA-00600`, within a defined period. Read More: [Investigating Logs for Errors](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/investigating-logs-for-errors.html) ## Analyzing Logs Using the Oracle Database Support Tools When the support-tools bundle is installed, TFA provides a unified interface to health checks, operating-system monitoring, database performance analysis, log searching, process inspection, configuration summaries, event reporting, log maintenance, and related tools across Linux, UNIX, and Windows. Administrators can verify installed tools with `tfactl toolstatus` and run them from command-line or interactive shell mode. Read More: [Analyzing Logs Using the Oracle Database Support Tools](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/analyzing-logs-using-the-oracle-database-support-tools.html) ## Searching Oracle Trace File Analyzer Metadata TFA metadata searches use `tfactl search` with JSON criteria to filter indexed events by content, database, and time range. The command can list available datatypes or return all matching events, with platform-specific quoting syntax for Linux, UNIX, AIX, Solaris, and Windows. Read More: [Searching Oracle Trace File Analyzer Metadata](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/searching-oracle-trace-file-analyzer-metadata.html) ## Oracle Trace File Analyzer Service Request Data Collections Service Request Data Collections provide predefined, problem-specific diagnostic profiles that gather and package the appropriate logs, reports, traces, and system information across local or cluster scopes. Administrators can run SRDCs interactively or silently, constrain collection time and database scope, tag or name output, and optionally upload results to a Service Request using configured upload settings. Read More: [Oracle Trace File Analyzer Service Request Data Collections](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/oracle-trace-file-analyzer-service-request-data-collections.html) ## Diagnostic Upload AHF provides generic upload configuration and execution for TFA, ORAchk, and EXAchk collections through HTTP, SQLNET, and SFTP endpoints. Using `ahfctl`, administrators can set, retrieve, validate, and remove named configurations that synchronize across cluster nodes, while `tfactl` or related tools can upload files during or after collection; the feature supports multiple users when installed as root but is not supported on Windows. Read More: [Diagnostic Upload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/diagnostic-upload.html) ## Performing Custom Collections Oracle Trace File Analyzer (TFA) supports targeted diagnostic collections by customizing the time range, event, nodes, components, directories, file sizes, collection names, and packaging behavior. Use `tfactl diagcollect` with options such as `-last`, `-from`, `-to`, `-for`, `-node`, component selectors, `-collectdir`, `-tag`, `-z`, `-nocopy`, `-notrim`, `-silent`, and `-cores`; event-driven collections may invoke an associated SRDC and require database `dba` privileges. IPS packages can also be collected and managed, while large files can be limited through `maxfilecollectionsize`. Read More: [Performing Custom Collections](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/performing-custom-collections.html) ## Limit the Maximum Amount of Memory Used by Oracle Trace File Analyzer On Linux systems with a full, root-installed Autonomous Health Framework, TFA memory usage can be constrained using `ahfctl setresourcelimit`. Limits apply to automatic collections, on-demand collections, and analysis operations, with supported values from 150 MB to 2 GB or 25% of system memory, whichever is lower. Use the `kmem` resource for system memory or `swmem` for combined system and swap memory; limits are enabled by default at the maximum value. Read More: [Limit the Maximum Amount of Memory Used by Oracle Trace File Analyzer](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/limit-the-maximum-amount-of-memory-used-by-oracle-trace-file-analyzer.html) ## Limit Oracle Trace File Analyzer CPU Usage On Linux, TFA CPU consumption can be limited with `ahfctl setresourcelimit -value`. Values range from 0.5 CPU to 4 CPUs or 75% of available CPUs, whichever is lower, and the default limit is the maximum permitted value. For example, setting the value to `0.5` limits TFA to approximately half of one CPU. Read More: [Limit Oracle Trace File Analyzer CPU Usage](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/limit-oracle-trace-file-analyzer-cpu-usage.html) ## Automatic TFA Self-Diagnostics on diagcollect Failure for Faster Issue Resolution When a root user’s manual `tfactl diagcollect` operation fails, TFA automatically runs `tfactl diagnosetfa -local -profile collection` and generates a local self-diagnostic bundle named in the `hostname_ahf_autodiagnostic.zip` format. The fallback covers service interruptions, stalled collectors, fatal collection errors, interruptions, and repository-related aborts, and displays the bundle location and recommended next steps. Remote-node failures and non-root failures require manually running the diagnostic command as root on the affected or local node and uploading the resulting bundles to the Service Request. Read More: [Automatic TFA Self-Diagnostics on diagcollect Failure for Faster Issue Resolution](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/automatic-tfa-self-diagnostics-on-diagcollect-failure-for-faster-issue-resolution.html) ## Proactively Detecting and Diagnosing Performance Issues for Oracle RAC Oracle Cluster Health Advisor provides early warnings, root-cause diagnoses, and corrective actions for emerging performance and availability issues affecting Oracle RAC databases and cluster nodes. It compares observed metrics with expected values from trained normal-operation models, detects significant anomalies, and reports targeted recommendations through Enterprise Manager Cloud Control. This release improves CHA detection on Exadata and adds support for Oracle Solaris RAC deployments. Read More: [Proactively Detecting and Diagnosing Performance Issues for Oracle RAC](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/proactively-detecting-and-diagnosing-performance-issues-for-oracle-rac.html) ## Oracle Cluster Health Advisor Architecture Oracle Cluster Health Advisor operates as the highly available `ochad` cluster resource on each node. Each daemon monitors its host operating system and optionally RAC database instances, receiving operating-system metrics from Cluster Health Monitor and database metrics through memory-mapped files without requiring database connections. The Health Prognostics Engine evaluates these metrics against selected models multiple times per minute for both nodes and monitored database instances. Read More: [Oracle Cluster Health Advisor Architecture](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/oracle-cluster-health-advisor-architecture.html) ## Removing Grid Infrastructure Management Repository Because GIMR is desupported in Oracle AI Database 26ai, existing configurations should be removed after checking GIMR and Oracle Fleet Patching and Provisioning status with `srvctl`. The procedure involves preparing a grid-owned directory, obtaining and extracting the deletion script, optionally exporting CHA models and FPP metadata, and executing `reposScript.sh -mode="Delete"` as the `grid` user. FPP users should use its self-upgrade process where applicable, because deleting GIMR without upgrading and reconfiguring FPP stops FPP functionality. Read More: [Removing Grid Infrastructure Management Repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/removing-grid-infrastructure-management-repository.html) ## Monitoring the Oracle Real Application Clusters Environment with Oracle Cluster Health Advisor CHA is provisioned and enabled by default with RAC or RAC One Node Grid Infrastructure installations and begins node monitoring automatically when database instances are detected. Grid users can enable database monitoring with `chactl monitor database -db`, stop it with `chactl unmonitor database -db`, and review node and database monitoring status with `chactl status`, optionally using `-verbose`. CHA monitors each RAC instance independently but does not support single-instance databases. Read More: [Monitoring the Oracle Real Application Clusters Environment with Oracle Cluster Health Advisor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/monitoring-the-oracle-real-application-clusters-environment-with-oracle-cluster-health-advisor.html) ## Using Cluster Health Advisor for Health Diagnosis CHA autonomously detects and clears problems, while Grid users query stored diagnoses with `chactl query diagnosis`, specifying a database and time range in `YYYY-MM-DD HH24:MI:SS` format. Results identify detected problems, descriptions, causes, impacts, and targeted corrective actions, and can be saved as HTML with `-htmlfile`. Diagnoses can expose issues such as control-file I/O latency, excessive database CPU usage, and frequent log switches. Read More: [Using Cluster Health Advisor for Health Diagnosis](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/using-cluster-health-advisor-for-health-diagnosis.html) ## Calibrating an Oracle Cluster Health Advisor Model for a Cluster Deployment CHA default models are designed to avoid false warnings, but `chactl calibrate` can improve sensitivity for a specific normal workload. Oracle recommends at least six hours of representative data with consistent time ranges across the cluster and databases; use `query calibration` to verify samples and filter abnormal data with KPI sets when necessary. After calibration, save the model under a user-defined name and activate it with `chactl monitor cluster -model`. Read More: [Calibrating an Oracle Cluster Health Advisor Model for a Cluster Deployment](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/calibrating-an-oracle-cluster-health-advisor-model-for-a-cluster-deployment.html) ## Viewing the Details for an Oracle Cluster Health Advisor Model Use `chactl query model -name` to inspect a CHA model’s target type, software version, operating-system platform, calibration target, calibration date, time ranges, and KPI settings. CHA models can also be renamed, imported, exported, or deleted as part of model administration. Read More: [Viewing the Details for an Oracle Cluster Health Advisor Model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/viewing-the-details-for-an-oracle-cluster-health-advisor-model.html) ## Managing the Oracle Cluster Health Advisor Repository When GIMR is configured, the CHA repository retains historical node and database problems, metric evidence, and models. Its default capacity supports 16 targets for 72 hours, with retention decreasing as targets increase; warnings occur below 72 hours and monitoring stops below 24 hours. Use `chactl query repository` to inspect capacity, `chactl set maxretention` to define the maximum retention period, and `chactl resize repository -entities` to expand support for additional targets. Read More: [Managing the Oracle Cluster Health Advisor Repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-the-oracle-cluster-health-advisor-repository.html) ## Viewing the Status of Cluster Health Advisor Use SRVCTL to check CHA service status and configuration across active hub and leaf nodes. `srvctl status cha` reports where the service is running, while `srvctl config cha` reports where it is enabled. A target is monitored only when it is running and its host node’s CHA service is active. Read More: [Viewing the Status of Cluster Health Advisor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/viewing-the-status-of-cluster-health-advisor.html) ## Enhanced Cluster Health Advisor Support for Oracle Pluggable Databases CHA expands support to as many as 4,000 PDBs, up from 256, improving suitability for large Autonomous Database deployments. Its enhanced detection and root-cause analysis considers events such as database reconfiguration, enabling more effective identification and preventive recommendations for issues including instance evictions. Read More: [Enhanced Cluster Health Advisor Support for Oracle Pluggable Databases](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/enhanced-cluster-health-advisor-support-for-oracle-pluggable-databases.html) ## New Profile to Include Cluster Health Advisor Data in Oracle Orachk and Oracle Exachk Reports AHF 25.9 adds the `cha` profile to Orachk and Exachk for collecting and reporting Cluster Health Advisor data. Running either tool with `-profile cha` produces a report containing only the CHA section, while `-includeprofile cha` adds that section to the standard report; the CHA profile is not enabled by default. Read More: [New Profile to Include Cluster Health Advisor Data in Oracle Orachk and Oracle Exachk Reports](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/new-profile-to-include-cluster-health-advisor-data-in-oracle-orachk-and-oracle-exachk-reports.html) ## Collecting Operating System Resources Metrics Cluster Health Monitor and System Health Monitor are lightweight, high-availability daemons that collect operating-system metrics every five seconds with low overhead. They aggregate CPU, device, process, network, NFS, protocol, filesystem, and critical-resource data into Nodeview snapshots, perform inline analysis and summarization, and provide Clusterware-aware tagging and analysis that is more consistent and useful than manually combining standard OS utilities. Read More: [Collecting Operating System Resources Metrics](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/collecting-operating-system-resources-metrics.html) ## Comparing CHM and SHM - Understanding their fundamental differences CHM, provided by Grid Infrastructure as `osysmond`, monitors RAC cluster nodes and stores Nodeview metrics in the GI repository, while SHM, provided by AHF as `ahf-sysmon`, supports single-instance and non-GI systems. CHM is managed by the GI high-availability stack and supports Linux, Solaris, AIX, zLinux, ARM64, and Windows; SHM is managed by AHF, supports Linux only, and stores metrics in the AHF repository. Both automatically archive and purge historical data and include their metrics in `tfactl diagcollect`. Read More: [Comparing CHM and SHM - Understanding their fundamental differences](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/comparing-chm-and-shm-understanding-their-fundamental-differences.html) ## Additional Details About System Health Monitor SHM is enabled by default in AHF on Linux single-instance and non-GI systems, collecting real-time process, memory, network, I/O, and disk metrics for diagnostics and Insights analysis. Administrators can check status with `ahfctl statusahf`, enable or disable it through the enhanced OS metrics property, inspect its process and JSON data, and verify resource cgroup placement. TFA collections include SHM data, which can be validated by collecting and inspecting archives for SHM-related files. Read More: [Additional Details About System Health Monitor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/additional-details-about-system-health-monitor.html) ## Collecting Cluster Health Monitor Data Cluster Health Monitor data can be collected from any cluster node, and Oracle recommends using `tfactl diagcollect` whenever an Oracle Clusterware error occurs so that relevant diagnostic information is gathered for investigation. Read More: [Collecting Cluster Health Monitor Data](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/collecting-cluster-health-monitor-data.html) ## Operating System Metrics Collected by Cluster Health Monitor and System Health Monitor CHM and SHM organize operating-system observations into Nodeview metric sets covering CPUs, devices, processes, network interfaces, NFS, protocols, filesystems, system resources, and Oracle process aggregates. Metrics include utilization, throughput, queueing, latency, errors, memory and swap activity, file descriptors, process states, network packets, filesystem capacity, and aggregated CPU, memory, thread, and descriptor usage for database, ASM, Clusterware, and other process groups. Read More: [Operating System Metrics Collected by Cluster Health Monitor and System Health Monitor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/operating-system-metrics-collected-by-cluster-health-monitor-and-system-health-monitor.html) ## Detecting Component Failures and Self-Healing Autonomously CHM’s `CHMDiag` daemon receives component events through the CRFE API, validates and schedules corrective actions, monitors execution, and terminates actions that exceed configured time limits. It records event details, action results, and daemon logs under the CHMDIAG base directory, while `oclumon chmdiag description`, `query`, and `collect` provide event documentation, reports, and data collection for troubleshooting and autonomous self-healing. Read More: [Detecting Component Failures and Self-Healing Autonomously](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/detecting-component-failures-and-self-healing-autonomously.html) ## CHM Inline Analysis CHM Inline Analysis preserves summarized operating-system diagnostics instead of large raw CHM or SHM files. TFA processes hourly compressed data, stores the smaller analyzed results in the AHF repository, and runs as root under resource constraints. This reduces repository requirements to about 100 MB and extends retention from hours to months, improving the likelihood that useful OS data is available in Service Requests. Read More: [CHM Inline Analysis](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/chm-inline-analysis.html) ## Integrating System Health Monitor into AHF for Standalone Non-Root Installations AHF integrates Linux-only SHM into standalone non-root Oracle Restart and single-instance installations, allowing non-root users to collect OS metrics and generate focused Insights reports. In the initial release, users manage the daemon with `sysmonctl start` and `sysmonctl stop`; SHM reads `/proc`, may collect less information than root installations, and should be validated under enforcing SELinux configurations. Read More: [Integrating System Health Monitor into AHF for Standalone Non-Root Installations](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/integrating-system-health-monitor-into-ahf-for-standalone-non-root-installations.html) ## Creating an AHF Insights Report for Operating System Issues - Non-Root AHF Installation To create an OS Insights report from SHM data in a non-root AHF installation, run the CHM driver from `$AHF_HOME/chm/bin` with the AHF Python interpreter and specify an output directory and start and end times. The driver processes, analyzes, and reports SHM data into Insights ZIP archives; verify source files under the AHF SHM data directory and view the report by opening `web/index.html` after extraction. Read More: [Creating an AHF Insights Report for Operating System Issues - Non-Root AHF Installation](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/creating-an-ahf-insights-report-for-operating-system-issues-non-root-ahf-installation.html) ## Diagnostic Signature - HugePagesNotUtilized AHF 25.11 introduces the `HugePagesNotUtilized` diagnostic signature, which detects when HugePages are configured but none are in use because total and free HugePages are equal. The signature produces a specific alert in the CHM analysis section of Orachk reports, helping identify memory configuration problems more quickly than generic utilization warnings. Read More: [Diagnostic Signature - HugePagesNotUtilized](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/diagnostic-signature-hugepagesnotutilized.html) ## Monitoring System Metrics for Cluster Nodes Oracle recommends Oracle Enterprise Manager for routine Oracle Clusterware monitoring, complemented by Cluster Health Monitor for full-stack operating-system and cluster observation. Both are enabled by default for Oracle clusters, and administrators should also review Clusterware resource activity logs to monitor managed resources and investigate operational issues. Read More: [Monitoring System Metrics for Cluster Nodes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/monitoring-system-metrics-for-cluster-nodes.html) ## Monitoring Oracle Clusterware with Oracle Enterprise Manager Oracle Enterprise Manager provides Cluster Database Home, Interconnects, and Cluster Database Performance views for monitoring RAC databases and Clusterware. These views report node, VIP, node application, alert-log, registry, voting-file, service, interconnect, throughput, error, load, host, cache-fusion, active-session, and database-throughput information. Historical views and Top Activity analysis help identify performance causes, resource needs, SQL or schema tuning opportunities, and cluster wait problems. Read More: [Monitoring Oracle Clusterware with Oracle Enterprise Manager](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/monitoring-oracle-clusterware-with-oracle-enterprise-manager.html) ## Monitoring Oracle Clusterware with Cluster Health Monitor The OCLUMON command-line tool queries CHM repositories for node metrics over selected periods and supports administrative tasks. Commands can change debug levels, display CHM versions, dump Nodeview information, and manage the metrics datafile size. Read More: [Monitoring Oracle Clusterware with Cluster Health Monitor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/monitoring-oracle-clusterware-with-cluster-health-monitor.html) ## Managing Oracle Database and Oracle Grid Infrastructure Logs TFA provides commands for managing Oracle Database and Grid Infrastructure diagnostic data and for monitoring disk-usage snapshots, helping control diagnostic storage and maintain usable log repositories. Read More: [Managing Oracle Database and Oracle Grid Infrastructure Logs](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-oracle-database-and-oracle-grid-infrastructure-logs.html) ## Managing Automatic Diagnostic Repository Log and Trace Files The `tfactl managelogs` command manages ADR files in alert, incident, trace, core-dump, health-monitor, diagnostic, and log directories. Administrators can restrict operations by file age, preview purge results with `-dryrun`, purge database or GI files with `-purge`, and inspect diagnostic-destination usage with `-show usage`; appropriate operating-system privileges are required. Read More: [Managing Automatic Diagnostic Repository Log and Trace Files](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-automatic-diagnostic-repository-log-and-trace-files.html) ## Managing Disk Usage Snapshots TFA automatically records disk-usage snapshots in its repository, using a default 60-minute interval. Administrators can change the interval with `tfactl set diskUsageMonInterval=minutes` and enable or disable monitoring with `tfactl set diskUsageMon=ON|OFF`. Read More: [Managing Disk Usage Snapshots](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/managing-disk-usage-snapshots.html) ## Purging Oracle Database and Oracle Grid Infrastructure Logs Automatic TFA log purging is enabled by default on Domain Service Clusters and disabled elsewhere; when enabled, it periodically removes logs older than the default 30-day age. Use `manageLogsAutoPurge` to toggle purging, `manageLogsAutoPurgePolicyAge` to set the retention age, and `manageLogsAutoPurgeInterval` to define the purge frequency. Read More: [Purging Oracle Database and Oracle Grid Infrastructure Logs](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/purging-oracle-database-and-oracle-grid-infrastructure-logs.html) ## Securing Access to Diagnostic Collections TFA restricts diagnostic commands to authorized users, allowing selected non-root operations for the Grid Infrastructure home owner and database home owners when TFA is root-installed on Linux or UNIX. Administrators can list, add, remove, remove all, or reset users through `tfactl access` commands, with optional local-node scope. Deleted operating-system usernames should also be removed from the AHF access list to prevent future users with the same name from inheriting old privileges. Read More: [Securing Access to Diagnostic Collections](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/securing-access-to-diagnostic-collections.html) ## Database Monitoring Using Database User Credentials AHF supports database monitoring with a configured username and password instead of requiring SYSDBA access, although the default `/` as SYSDBA connection remains preferred because common-user access can limit diagnostic collection. Configure an AHF database user in the CDB for multitenant databases or the database for nonmultitenant environments, preferably grant the DBA role, or provide the required dictionary, directory, advisor, session, container, and catalog privileges. For multitenant databases, enable access to data across all containers with `CONTAINER_DATA=ALL`, then have the Oracle software owner store the credentials in the AHF Wallet using `ahf security add-credentials`; the database unique name must be used to uniquely identify the database. Read More: [Database Monitoring Using Database User Credentials](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/database-monitoring-using-database-user-credentials.html) # Explore Diagnostic Insights Autonomous Health Framework Insights (AHF Insights) provides deeper diagnostic insights into Oracle diagnostic collections collected by AHF diagnostic utilities, Oracle Exachk, Oracle Trace File Analyzer, Exawatcher, and Cluster Health Monitor. AHF Insights is bundled with AHF installer package. You do not need to run a web server to host this site. > **Note:** > > The current version is supported on Linux only. ## Introduction to AHF Insights AHF Insights is a web-based, offline diagnostic reporting interface that consolidates configuration, topology, metrics, logs, and analyzer results into a unified view for system assessment and root-cause analysis. It identifies system state, operating-system anomalies, best-practice gaps, traces, and selected corrective actions. Generate a report with `ahf analysis create --type insights`, optionally specifying a time range, then transfer and extract the resulting ZIP file and open its `index.html` file in a web browser. Read More: [Introduction to AHF Insights](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/introduction-to-ahf-insights.html) ## Ahf Insights Supported Platforms AHF Insights is supported with standard AHF installations on Oracle Linux, but not with standalone AHF, ARM Linux, zLinux, Windows, Solaris, HP-UX, or AIX installations. It can be included in diagnostic collections when `autoInsights` is enabled, including supported SRDCs and selected automatic error events involving database hangs, crashes, performance, RAC, Exadata, Data Guard, ASM, Clusterware, and operating-system resource issues. The `maareview` collection can additionally include Exachk, AWR, Exawatcher, capacity-planning, and Data Guard or Active Data Guard information. Read More: [Ahf Insights Supported Platforms](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/ahf-insights-supported-platforms.html) ## Ahf Insights - Home The Home page summarizes the report’s system state, type, time range, topology, and collected diagnostic information, with selectable items that open detailed views. It provides topology sections for clusters, databases, database servers, storage servers, and fabric switches, along with insights covering database anomalies, Data Guard, timelines, operating-system issues, best-practice compliance, system changes, recommended software, Management Server data, RPMs, database and kernel parameters, space usage, and performance reports. Navigation supports multiple open items, keyboard movement, return-to-top, closing views, and feedback submission. Read More: [Ahf Insights - Home](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/ahf-insights-home.html) ## System Topology System Topology presents cluster and infrastructure details, with Fabric Switches and Storage Servers shown only in Exadata environments. The Cluster section summarizes system, Grid Infrastructure, incidents, databases, servers, storage, and fabric resources, and provides expandable cluster-resource and ASM details, including status, disk groups, and utilization. Databases show instances, PDBs, and tablespaces; database, storage, and fabric server sections provide sortable infrastructure information. Starting with AHF 23.8, cluster, database, server, storage, and fabric details can be copied as text or snippets for inclusion in Service Requests. Read More: [System Topology](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/system-topology.html) ## Insights The Insights page provides analytical views for timeline events, operating-system issues, best-practice compliance, system changes, recommended software, database-server metrics and alerts, RPMs, database and kernel parameters, patches, space usage, database anomalies, and performance reports. Timeline filtering and faceted views correlate events across components, databases, hosts, and time, with associated files available in the File Viewer. Operating-system views cover configuration, metrics, anomalies, Exawatcher data, process groups, and detailed snapshots, while compliance, change, patch, capacity, and parameter views support filtering and cross-node comparison. Database Anomalies Advisor identifies causes and corrective actions, and AWR, AWR Compare, and Performance Hub reports support performance troubleshooting, subject to applicable licensing and collection requirements. Read More: [Insights](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/insights.html) ## AHF Insights Interactive Subshell Command Reference The AHF Insights interactive subshell allows users to inspect report contents directly from a terminal without extracting or transferring files. Launch it with `ahf analysis explore --type insights --from-file FILE`, then use `show -s` to display summaries, topology, databases, problems, events, changes, software, alerts, RPMs, parameters, patches, space, and performance reports. Optional filters support ASM and cluster resources, specific databases, timestamps, hosts, instances, patch bugs, components, and hidden parameters. The REPL supports `show`, `clear`, `help`, and `exit`, while paginated output provides navigation, search, and back controls. Read More: [AHF Insights Interactive Subshell Command Reference](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/explore-diagnostic-insights/ahf-insights-interactive-subshell-command-reference.html) # Analyze Issue Root Cause Autonomous Health Framework Scope (AHF Scope) is a standalone, interactive, real-time capable front-end to Cluster Health Advisor (CHA). AHF Scope requires a very small foot-print on the monitored system. > **Note:** > > The Autonomous Health Framework Scope (AHF Scope) feature of Cluster Health Advisor (CHA) is deprecated in Oracle AI Database 26ai. > > To better align with evolving customer needs, Oracle is discontinuing AHF Scope and recommends using Autonomous Health Framework Insights (AHF Insights) as the replacement. > > When AHF detects issues such as node evictions, instance evictions, or database performance degradation, it provides a comprehensive report through AHF Insights-highlighting the problem, identifying the root cause, and offering recommended actions. > > Additionally, the Database Anomalies Advisor presents a timeline view of anomalies across hosts and database instances. Users can drill down into each finding to understand the underlying cause and suggested resolution. CHA continuously monitors cluster nodes and Oracle RAC databases for performance and availability issue precursors to provide early warning of problems before they become critical. > **Note:** > > GIMR is optionally supported in Oracle Database 19c. However, it's desupported in Oracle AI Database 26ai. For more information, see [Removing Grid Infrastructure Management Repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/collect-diagnostic-data/removing-grid-infrastructure-management-repository.html). ## Introduction to AHF Scope AHF Scope is a lightweight, standalone, interactive front end for Oracle Cluster Health Advisor that supports real-time monitoring through GIMR or offline analysis from archived GIMR data. It is launched with the `ahfscope` script and is designed for efficient operation by cluster and database experts using keyboard shortcuts, pointer navigation, and contextual menus. Read More: [Introduction to AHF Scope](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/introduction-to-ahf-scope.html) ## Cluster View - Connecting And Basics Of Monitoring AHF Scope starts through `ahfscope` on Linux/UNIX or `ahfscope.bat` on Windows, using Oracle Wallet services to obtain GIMR connection parameters. After connecting, it presents the top-level Cloud View and exits when the main window is closed. Read More: [Cluster View - Connecting And Basics Of Monitoring](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/cluster-view-connecting-and-basics-of-monitoring.html) ## Basics of Navigation Through Entity Panels The default interface combines a navigation tree with an analysis panel containing a system timeline, status line, and entity-specific details. Entities are hierarchically organized under OurCloud, with colors indicating normal, abnormal, missing, or partially missing data; status propagates upward from sub-entities. Users can navigate by selecting tree items, double-clicking focused entities, or pressing Enter, while themes, focus behavior, and persistent display settings support efficient analysis across clusters, hosts, databases, and instances. Read More: [Basics of Navigation Through Entity Panels](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/basics-of-navigation-through-entity-panels.html) ## Target Entities CHA supports Host and Instance target entities, each with specialized panels showing an overall state timeline and metric probe histories. Target states use green, yellow, red, and gray to represent normal, probe-level abnormality, diagnosed problems, and missing data; each sample may include observed values, predicted values, probe states, and associated problems. Specialized tabs expose dynamic relationships, such as instances running on hosts, which may change over time independently of the logical navigation hierarchy. Read More: [Target Entities](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/target-entities.html) ## Host Panel The Host panel provides Host Detail and Instances tabs, showing host status and the time-dependent instances running on it. Because multiple instances may run on one host, the relationship is one-to-many and can include shutdowns or host changes. Users can switch directly to an instance panel by focusing its timeline and pressing Enter, using arrow keys, or double-clicking its name. Read More: [Host Panel](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/host-panel.html) ## An Instance Panel The Instance panel displays the instance status history and service interruptions, while its Host tab shows the host associated with the instance over time. An instance has a one-to-one relationship with a host at any particular moment, although it may move between hosts. Users can navigate between related hosts and instances through timeline selection, Enter, or double-click actions, with displayed time ranges adapting to the window size. Read More: [An Instance Panel](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/an-instance-panel.html) ## Browsing Through Time and Pin Operation Live AHF Scope views continuously advance as new samples arrive, with a cursor marker identifying the current time and abnormal probes. Users can pin a timestamp by double-clicking, pressing `p`, or using the arrow keys over a target timeline, then fine-tune it with left and right arrows; `f` restores cursor following. A pinned time is preserved across cluster entities, while Control-assisted cursor movement allows comparison of selected probe values at other timestamps, and live pins are released when they reach the viewport boundary. Read More: [Browsing Through Time and Pin Operation](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/browsing-through-time-and-pin-operation.html) ## Changing the Set of Visible Probes AHF Scope normally displays only abnormal probes or those associated with a selected problem, but users can switch to all high probes, every probe, correlated probe categories, time-range abnormal probes, or custom probe subsets. Menus and hot keys control these modes, while arrow, page, and mouse-wheel navigation scroll through probes when more signals exist than fit on screen. Probe categories and correlations can be explored through focused timelines or the Expert tab. Read More: [Changing the Set of Visible Probes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/changing-the-set-of-visible-probes.html) ## Selecting Abnormal Probes in Any Time Range Users can select a time range by Shift-dragging across a target timeline, activating a filter that displays probes abnormal during the selected interval rather than only at one timestamp. The selection is retained across entities in the cluster, enabling comparisons between hosts or instances. The filter is cleared through the reset option in the context menu or by pressing Escape. Read More: [Selecting Abnormal Probes in Any Time Range](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/selecting-abnormal-probes-in-any-time-range.html) ## Problems or Anomalies Red entity states indicate one or more diagnosed problems, each containing an identifier, description, confidence, root cause, corrective actions, associated abnormal probes, inference chains, and optional detailed tables. Problems are ordered primarily by confidence, with KPI-related problems prioritized, and their content may vary by timestamp. Selecting a problem cycles through its description, diagnosis, and supporting probe timelines, while magenta timeline ranges identify periods when the selected problem was active. Read More: [Problems or Anomalies](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/problems-or-anomalies.html) ## Browsing through active time of a problem When a problem is selected, its active periods appear in magenta on the target timeline. Holding Shift and pressing the left or right arrow key moves the cursor to the previous or next timestamp at which the same problem was reported, allowing rapid review of recurring occurrences. Read More: [Browsing through active time of a problem](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/browsing-through-active-time-of-a-problem.html) ## Expert Mode Expert mode supports deeper comparison of CHA metric observations with model predictions, helping users assess whether warnings are timely and whether the calibration reflects the monitored workload. It provides additional analytical views beyond Standard mode, particularly for investigating potential false positives, missed diagnoses, and model suitability. Read More: [Expert Mode](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/expert-mode.html) ## Activating the Expert Mode Expert mode is enabled with `e` or through the context menu and adds an Expert tab while changing probe timeline displays. It overlays predicted and observed values, using colors to show probe state, and can instead display residuals: positive differences appear as green regions and negative differences as blue regions. Residual analysis is meaningful only when both predicted and observed values are available and can reveal calibration problems or good model alignment. Read More: [Activating the Expert Mode](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/activating-the-expert-mode.html) ## Resizing Expert Diagrams Expert graphs can be vertically zoomed to expose details obscured by automatic scaling. Users place the cursor over the relevant graph and Control-drag with the left mouse button, or use the corresponding Control arrow keys, with graph heights limited to 128 pixels. Read More: [Resizing Expert Diagrams](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/resizing-expert-diagrams.html) ## Selecting Custom Set of Probes The Expert tab provides a hierarchical category tree for selecting individual probes or groups of related probes to display. Category relationships are reflected through highlighting, allowing shared probes to be identified and selectively removed. Custom selections can be saved under named configurations, loaded after restarting AHF Scope on the same host, or deleted from persistent storage; selecting a saved set does not activate it until Load is used. Read More: [Selecting Custom Set of Probes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/selecting-custom-set-of-probes.html) ## Live and Passive Sessions AHF Scope maintains a live session for current GIMR metrics and a replay session for historical periods retrieved through the System Timeline. Replay is available only with a GIMR connection; file-based feeds are passive and cannot retrieve additional historical data. Users move the time selector with Shift and mouse or arrow keys, wait for the historical query to complete, and investigate the static replay while live collection continues; moving to the current endpoint or pressing `=` restores live mode and discards replay data. Read More: [Live and Passive Sessions](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/live-and-passive-sessions.html) ## ahfscope Console Commands The `ahfscope -i` option enables an interactive CLI with commands for listing entities, feeds, metrics, probes, units, missing or flagged values, diagnoses, versions, tracing, zooming, and exiting. Commands support abbreviated prefixes when unambiguous and provide diagnostic summaries or internal data not available through the graphical interface, including feed timing, database tracing, input capture, root-cause output, and topology changes. Read More: [ahfscope Console Commands](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/ahfscope-console-commands.html) ## List of Hot Keys AHF Scope hot keys provide mouse-free control for themes, zooming, probe visibility, Expert mode, residual displays, pinning, problem navigation, time filtering, signal scrolling, and live/replay session control. Arrow and page keys navigate entities and signals, Control combinations resize or inspect graphs, and Shift-arrow commands move through problem occurrences or shift the system time selector. Read More: [List of Hot Keys](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/list-of-hot-keys.html) ## Set of Persistent Settings AHF Scope persists the selected theme, last start time, details-panel width, window size and position, last probe selection, and named custom probe selections. These settings are associated with a specific user and host and can be reused in subsequent sessions on that host. Read More: [Set of Persistent Settings](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/set-of-persistent-settings.html) ## Accessibility Aspects AHF Scope supports complete keyboard operation through Tab, cursor keys, Enter, modifier keys, and hot keys, with no operation timeouts that would prevent use of Sticky Keys or Slow Keys. Its high-contrast, image-free interface supports magnification and does not depend on the operating system’s High Contrast mode. Java accessibility features and JAWS version 17 or later are supported on Microsoft Windows. Read More: [Accessibility Aspects](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/accessibility-aspects.html) ## Customizing Java Run Time System Because AHF Scope runs on Java, advanced users can customize JVM behavior through the launch script or `_JAVA_OPTIONS`. Hardware-accelerated Java 2D rendering through OpenGL or Direct3D can improve display performance, with options available to enable these pipelines and diagnostic output indicating whether acceleration is supported. Rendering behavior may depend on current graphics drivers and, for some hardware, additional framebuffer configuration. Read More: [Customizing Java Run Time System](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/customizing-java-run-time-system.html) ## Setting Proper Character Encoding Page On Microsoft Windows Incorrect Windows console code pages can cause characters such as the Greek micro symbol to display incorrectly in AHF Scope output. Users should check the active code page with `chcp` and switch from unsuitable defaults such as 437 to a multilingual page such as 850 when necessary. Read More: [Setting Proper Character Encoding Page On Microsoft Windows](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/setting-proper-character-encoding-page-on-microsoft-windows.html) ## ahfscope The `ahfscope` command launches AHF Scope with options for live GIMR monitoring, file-based replay, interactive CLI access, query configuration, MDB extraction, and debugging. The `-f` option reads an MDB archive, `-i` enables interactive commands, `-q` controls query duration and timing, `-C` generates JSON without the GUI, and `-D` enables diagnostic tracing. Without options, AHF Scope connects through JDBC and Oracle Wallet, starts a live session, and initially loads the most recent 60 minutes or the duration configured by `-q`; archived MDB files can be produced from exported GIMR repository data for offline analysis. Read More: [ahfscope](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/analyze-issue-root-cause/ahfscope.html) # Resolve Database Issues Learn how to diagnose and resolve database issues, including detected problems, resource contention, database delays, internal errors, memory issues, and database performance problems using Oracle Autonomous Health Framework (AHF). ## Resolve Problems AHF has Detected To investigate problems detected by AHF Insights, run `tfactl diagcollect` as the Oracle user on the affected machine, transfer and extract the diagnostic archive, open its embedded `index.html`, and select **Detected Problems**. The page provides each problem’s description, reason, root cause, supporting evidence, and resolution steps; the section appears only when problems are detected. Typical causes include configuration issues, resource bottlenecks, network or I/O failures, memory growth, contention, blocked processes, insufficient redo or buffers, and storage errors. Read More: [Resolve Problems AHF has Detected](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolve-problems-ahf-has-detected.html) ## Resolve Noisy Neighbor Issues AHF Balance analyzes historical CPU consumption and Database Resource Manager settings from Enterprise Manager to identify CPU-based noisy-neighbor exposure and recommend `CPU_COUNT` values. It supports partitioned clusters, where CPU capacity is dedicated, and risk-management configurations for over-provisioned clusters. Reports are available at cluster, fleet, and database levels and show current, disaster, and recommended exposure and impact scenarios, including enhanced recommendations for standby databases that may become primary during a disaster. Configure the Enterprise Manager repository connection with `ahf configuration set --type impact`, then create fleet or cluster analyses with `ahf analysis create`; reports use hourly EM data, normally retained for 32 days. Read More: [Resolve Noisy Neighbor Issues](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolve-noisy-neighbor-issues.html) ## Resolving Database and Database Instance Delays Blocker Resolver is an autonomous `DIA0` database task that detects sessions waiting on resources, analyzes whether waits represent potential delays, verifies them after a threshold, and terminates the blocking session or process when necessary. Its sensitivity can be set to Normal or High with `DBMS_BLOCKER_RESOLVER`, while trace-file size and count are configurable through `base_file_size_limit` and `base_file_set_count`; `DBMS_HANG_MANAGER` is deprecated in Oracle AI Database 26ai. Resolutions are recorded as ADR incidents with code `ORA-32701`, with diagnostics in DIA0 trace files and alert logs. The cluster resource activity log and `crsctl query calog` provide hierarchical, activity-ID-based details for Oracle Clusterware resource failures and their causes. Read More: [Resolving Database and Database Instance Delays](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolving-database-and-database-instance-delays.html) ## Resolving ORA-00600 Internal Error Codes `ORA-00600` is a generic low-level internal error, usually indicating an unexpected condition or software bug, with arguments that help identify the failing function and diagnostic context. Review the database alert log and referenced trace file, then collect an SRDC from the affected machine with `tfactl diagcollect -srdc ORA-00600` as the Oracle user. Upload the resulting TFA package to the My Oracle Support ORA-00600 troubleshooting tool to obtain matching recommendations and possible bug or release-update information; if no resolution is found, create a Service Request and provide the requested product, version, support, operating-system, and severity details. Read More: [Resolving ORA-00600 Internal Error Codes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolving-ora-00600-internal-error-codes.html) ## Resolving ORA-04031 unable to allocate bytes of shared memory Error Codes `ORA-04031` occurs when a process cannot allocate required shared memory, commonly because memory parameters are too low, automatic tuning has problems, application design causes fragmentation, or a bug or memory leak exists. Collect an SRDC with `tfactl diagcollect -srdc ORA-04031`, selecting the relevant time and database, then upload the affected-node archive to the My Oracle Support ORA-04031 troubleshooting tool for diagnostic recommendations. If the tool does not resolve the issue, create a Service Request, complete the product, version, support identifier, operating system, and severity fields, and submit the diagnostic collection for Oracle Support review. Read More: [Resolving ORA-04031 unable to allocate bytes of shared memory Error Codes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolving-ora-04031-unable-to-allocate-bytes-of-shared-memory-error-codes.html) ## Resolving ORA-07445 exception encountered - core dump `ORA-07445` indicates an operating-system exception in an Oracle process that should generate a core file; common causes include bad data, severe misconfiguration, or a software bug. Run `tfactl diagcollect -srdc ORA-07445` as the Oracle user on the affected machine, specify the relevant time and database, and use the resulting TFA package with the My Oracle Support ORA-07445 troubleshooting tool. The tool analyzes the collection and recommends applicable knowledge documents, bug fixes, or release updates. If no solution is identified, create a Service Request, provide the requested environment and severity information, and attach the diagnostic collection. Read More: [Resolving ORA-07445 exception encountered - core dump](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolving-ora-07445-exception-encountered-core-dump.html) ## Resolving ORA-04030 out of process memory when trying to allocate `ORA-04030` occurs when an Oracle or client process exhausts operating-system memory or its available PGA allocation. Resolution may involve increasing physical memory, adjusting PGA limits, reducing resource consumption, correcting operating-system limits, or addressing a memory leak. Generate an SRDC with `tfactl diagcollect -srdc ORA-04030`, select the relevant event and database, and upload the affected-node archive to the My Oracle Support ORA-04030 troubleshooting tool. Review its recommendations and related bug or release-update information; if necessary, create a Service Request with the required product, version, support, operating-system, and severity details so Oracle Support can analyze the collection. Read More: [Resolving ORA-04030 out of process memory when trying to allocate](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/resolving-ora-04030-out-of-process-memory-when-trying-to-allocate.html) ## Database Performance Tuning Oracle database performance tuning begins by determining whether the issue is database-wide, such as CPU, I/O, memory, network, process, configuration, hang, or bug related, or query-specific, such as inefficient SQL, missing indexes, stale statistics, or changed execution plans. Collect diagnostics with `tfactl diagcollect -srdc dbperf -database `, including bad and comparable good periods when possible, then use AHF Insights to review best-practice deviations, anomalies, resource bottlenecks, operating-system metrics, and embedded PerfHub, AWR, and ADDM reports. Use ASH and ADDM findings to identify CPU-bound workloads and expensive SQL, configure AHF Balance against Enterprise Manager to investigate noisy neighbors when relevant, and create a Service Request with the collection if further assistance is required. Read More: [Database Performance Tuning](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/resolve-database-issues/database-performance-tuning.html) # Troubleshoot Learn to fix Oracle Trace File Analyzer and Compliance Framework (Oracle ORAchk and Oracle EXAchk) issues. ## Cluster Nodes are Not Showing As One Cluster When Viewed by Running the tfactl status Command The cluster appears fragmented because certificates are not synchronized between nodes. As root on any cluster node, run `$GIHOME/tfa/nodename/tfa_home/bin/synctfanodes.sh` to synchronize the keys; the script uses SSH and SCP and may prompt for root passwords unless passwordless SSH or Expect is available. Read More: [Cluster Nodes are Not Showing As One Cluster When Viewed by Running the tfactl status Command](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/cluster-nodes-are-not-showing-as-one-cluster-when-viewed-by-running-the-tfactl-status-command.html) ## Oracle Trace File Analyzer is Not Starting and the init.tfa script is Missing After Reboot After reboot, TFA may fail to start and its `init.tfa` script may be missing when the file system containing `TFA_HOME` was unavailable, slow to mount, inaccessible through NFS, or affected by maintenance or file-system errors. Refer to My Oracle Support note 2224163.1 for corrective steps. Read More: [Oracle Trace File Analyzer Is Not Starting](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-is-not-starting.html) ## Error Message Similar to "Can't locate \*\*\*\* in @inc (@inc contains:....)" Errors such as `Can't locate ... in @inc` can result from using Perl older than version 5.10, which TFA requires. Upgrade Perl, update the Perl path in `tfa_home/tfa_setup.txt`, or specify the Perl installation directory with the `-perlhome` option during installation; the selected directory must contain an executable `/bin/perl` owned by root when installed by root. Read More: [Old version of Perl](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/old-version-of-perl.html) ## Non-Release Update Revisions (RURs) Oracle Trace File Analyzer Patching Fails on Remote Nodes Remote TFA nodes can fail to upgrade because of socket issues, leaving inconsistent versions, build IDs, or upgrade statuses. Install the TFA package locally on failed nodes, then copy the root SSL files `server.jks`, `client.jks`, and `internal/ssl.properties` from the configuration node with root ownership and mode 700 to restore synchronized communication. Read More: [Non-Release Update Revisions Oracle Trace File Analyzer Patching Fails on Remote Nodes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/non-release-update-revisions-oracle-trace-file-analyzer-patching-fails-on-remote-nodes.html) ## Non-Root Access is Not Enabled After Installation Non-root access for the Oracle Grid Infrastructure software owner may not be enabled after installation. As root, run `tfactl access add -user username`, such as `tfactl access add -user xyx`, to grant the specified user group access to TFA. Read More: [Non-Root Access Is Not Enabled After Installation](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/non-root-access-is-not-enabled-after-installation.html) ## TFA\_HOME and Repository Locations are Moved After Patching or Upgrade Patching can relocate `TFA_HOME` into `GRID_HOME` and move the repository to the Grid Infrastructure owner’s `ORACLE_BASE`, potentially losing a customized repository location. Reset the repository path with `tfactl set repositorydir` and adjust its maximum size with `tfactl set reposizeMB`; newer releases migrate or upgrade TFA depending on its current location and patch version. Read More: [TFA\_HOME and Repository Locations are Moved After Patching or Upgrade](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/tfa_home-and-repository-locations-are-moved-after-patching-or-upgrade.html) ## Oracle Trace File Analyzer Fails with TFA-00103 After Applying the July 2015 Release Update Revision (RUR) or Later TFA upgrades use a two-phase process: software is installed locally on every node, then new SSL keys and the secured communication model are deployed after all nodes upgrade, normally within 24 hours. If `TFA-00103` persists, verify matching versions and build IDs with `tfactl print status`, confirm registered directories and synchronized root-owned SSL files, and run `synctfanodes.sh` from a node completing phase 2 to force certificate generation and synchronization for nodes upgraded later or excluded during the waiting period. Read More: [Oracle Trace File Analyzer Fails with TFA-00103 After Applying the July 2015 Release Update Revision or Later](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-fails-with-tfa-00103-after-applying-the-july-2015-release-update-revision-or-later.html) ## OSWatcher Parameters are Different After a Reboot or Otherwise Unexpectedly Different When TFA manages OSWatcher, startup parameters are persisted per user in newer releases, with normal operation using the `oracle` or `grid` settings after reboot. Avoid running OSWatcher as root; if settings are incorrect, stop it and restart it as the non-privileged owner with the intended or default parameters, such as `tfactl start oswbb`, unless OSWatcher is independently installed and not managed by TFA. Read More: [OSWatcher Parameters are Different After a Reboot or Otherwise Unexpectedly Different](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oswatcher-parameters-are-different-after-a-reboot-or-otherwise-unexpectedly-different.html) ## Oracle Trace File Analyzer Installation or Oracle Trace File Analyzer Discovery (tfactl rediscover) Fails on Linux 7 Missing Perl modules such as `Data::Dumper` during TFA installation or `tfactl rediscover` on Linux 7 are associated with known bugs fixed in TFA 12.1.2.6.4. Link the operating system Perl command to the Perl version supplied in `GRID_HOME` to work around the issue. Read More: [Oracle Trace File Analyzer Installation or Oracle Trace File Analyzer Discovery - tfactl rediscover Fails on Linux 7](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-installation-or-oracle-trace-file-analyzer-discovery-tfactl-rediscover-fails-on-linux-7.html) ## OSWatcher Analyzer Fails When OSWatcher is Not Running from the TFA\_HOME OSWatcher Analyzer commands work only when OSWatcher runs from TFA’s managed installation under `TFA_HOME`. Stop and disable any OSWatcher instance running elsewhere, then start OSWatcher through TFA. Read More: [OSWatcher Analyzer Fails When OSWatcher is Not Running from the TFA\_HOME](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oswatcher-analyzer-fails-when-oswatcher-is-not-running-from-the-tfa_home.html) ## Oracle Trace File Analyzer Fails to Start with com.sleepycat.je.EnvironmentLockedException Java Exception A `com.sleepycat.je.EnvironmentLockedException` indicates that TFA’s Berkeley DB lock file is already held or stale. Check the lock with `fuser`, terminate any process using it, remove `je.lck` from the Berkeley DB directory, and restart TFA as root. Read More: [Oracle Trace File Analyzer Fails to Start with Java Exception](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-fails-to-start-with-java-exception.html) ## Oracle Trace File Analyzer Startup Fails When Solution-Soft Time Machine Software is Installed, but Not Running on the System TFA startup can fail when Solution-Soft Time Machine is installed even if it is not running. Uninstall the Time Machine software to resolve the startup conflict. Read More: [Oracle Trace File Analyzer Startup Fails When Solution-Soft Time Machine Software is Installed but Not Running on the System](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-startup-fails-when-solution-soft-time-machine-software-is-installed-but-not-running-on-the-system.html) ## Non-privileged User is Not Able to Run tfactl Commands Use `tfactl access lsusers` as root to verify that the non-privileged user is listed and has an Allowed status. Add missing users with `tfactl access add -user username`; if access is disabled or the issue remains, run `tfactl diagnosetfa -local` and provide the resulting diagnostic file to Oracle Support. Read More: [Non-privileged User is Not Able to Run tfactl Commands](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/non-privileged-user-is-not-able-to-run-tfactl-commands.html) ## Oracle Trace File Analyzer Daemon is Not Starting or Not Running? Errors `TFA-00001` and `TFA-00002` indicate that the Java-based TFA daemon did not start or is stopped. Check for running processes, confirm the state with `tfactl print status`, restart it as root with `tfactl start`, and run `tfactl diagnosetfa -local` for support analysis if startup still fails. Read More: [Oracle Trace File Analyzer Daemon is Not Starting or Not Running](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-daemon-is-not-starting-or-not-running.html) ## Oracle Trace File Analyzer Is Not Collecting Diagnostic Traces of Components Such As CRS, DB, ASM, and So On If TFA cannot collect CRS, database, ASM, or other component traces, verify their Grid Infrastructure base and diagnostic directories with `tfactl print directories`. Add required subdirectories using `tfactl directory add`; use `-force` only when necessary because AHF may reject standard directories it considers invalid. Read More: [Oracle Trace File Analyzer Is Not Collecting Diagnostic Traces of Components](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-is-not-collecting-diagnostic-traces-of-components.html) ## Oracle Trace File Analyzer Fails to Start TFA cannot start when its reserved ports 5000 through 5005 are already in use, producing a Java `Address already in use` or `BindException` error. Set an available port in `data_dir/internal/port.txt` and restart TFA with `tfactl start`. Read More: [Oracle Trace File Analyzer Fails to Start](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-trace-file-analyzer-fails-to-start.html) ## TFACTL Collection Errors: "METADATA JSON FILE ALREADY EXISTS" in tfa\_main.trc Simultaneous manual collections can fail with `METADATA JSON FILE ALREADY EXISTS` because processes generate identically tagged metadata files within the same second. Run concurrent collections with unique `-tag` values so each collection directory and metadata file has a distinct name. Read More: [TFACTL Collection Errors](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/tfactl-collection-errors.html) ## How to Troubleshoot Oracle Orachk and Oracle Exachk Issues Troubleshoot Orachk and Exachk by selecting the correct tool, confirming it is current with the `-v` option, reviewing applicable FAQ and support information, and examining error and execution logs. If needed, enable debug output, collect the resulting ZIP and logs, open a support request, and attach the diagnostic materials. Read More: [How to Troubleshoot Oracle Orachk and Oracle Exachk Issues](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/how-to-troubleshoot-oracle-orachk-and-oracle-exachk-issues.html) ## How to Capture Debug Output Reproduce the issue with the smallest practical check scope, then run Orachk or Exachk with `-debug` and optionally specify a module such as setup, discovery, execution, or output. For daemon-based runs, restart the daemon with `-d start -debug`; collect the generated debug logs, temporary output, and resulting ZIP file for analysis. Read More: [How To Capture Debug Output](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/how-to-capture-debug-output.html) ## Data Entry Terminal Considerations Run Orachk and Exachk from supported UNIX or Linux terminals, recognizing that dropped connections can interrupt interactive prompts and leave processes hung. VNC generally minimizes network disruption; if accessibility software or terminal inactivity controls suspend sessions, adjust the relevant operating-system timeouts before running the tools. Read More: [Data Entry Terminal Considerations](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/data-entry-terminal-considerations.html) ## Tool Runs without Producing Files Orachk and Exachk normally create temporary and output files, but cleanup occurs after cancellation or error. If a completed run produces no output, rerun the tool in debug mode and inspect the results; contact Oracle Support if the problem continues. Read More: [Tool Runs without Producing Files](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/tool-runs-without-producing-files.html) ## Messages similar to “line \*\*\*\*: \*\*\*\* Killed $perl\_cmd 2\>\> $ERRFIL?” Messages stating that a Perl command was killed generally indicate that the built-in watchdog terminated a command exceeding its timeout, typically to prevent a hung process. Investigate the slow or blocked operation and use timeout troubleshooting procedures where appropriate. Read More: [Messages Similar to](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/messages-similar-to.html) ## Messages similar to “RC-001- Unable to read driver files” Driver-file read errors can result from an unsupported platform, insufficient temporary or working-directory space, missing installation support files, or inadequate read/write permissions. Confirm platform support, provide sufficient disk space, ensure the hidden `.cgrep` directory exists, and verify access to the temporary and working directories. Read More: [Messages similar to RC-001- Unable to read driver files](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/messages-similar-to-rc-001-unable-to-read-driver-files.html) ## Messages similar to “There are prompts in user profile on \[hostname\] which will cause issues in \[tool\] successful execution” Orachk and Exachk stop when user profiles contain interactive prompts or commands such as `read -p`, because remote executions cannot answer them and eventually time out. Temporarily comment out profile prompts on all relevant nodes and rerun the tools. Read More: [Messages similar to There are prompts in user profile on](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/messages-similar-to-there-are-prompts-in-user-profile-on.html) ## Problems Related to Remote Login Messages indicating missing SSH or SCP files point to remote-login configuration problems. Verify the executables and configured paths, ensure remote access works manually, correct profile prompts and root authentication issues, and use local runs followed by report merging as a temporary alternative while remote connectivity is repaired. Read More: [Problems Related To Remote Login](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/problems-related-to-remote-login.html) ## Other Error Messages in orachk\_error.log or exachk\_error.log Many messages in Orachk or Exachk error logs are expected in role-separated environments, where permission-denied OPatch operations occur against homes owned by other users and are handled through alternate inventory methods. These messages, along with repeated null integer-expression warnings, generally do not require reporting; running the tools as root can reduce such output. Read More: [Other Error Messages in orachk\_error or exachk\_error logs](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/other-error-messages-in-orachk_error-or-exachk_error-logs.html) ## Space available on {node\_name} at {path} is {x} MB and required space is 500 MB This message means the tool lacks sufficient space for temporary files, which default to the executing user’s home directory. Free at least the required space or set `RAT_TMPDIR` to a location with adequate capacity before rerunning Orachk. Read More: [Space available on node at is x MB and required space is 500 MB](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/space-available-on-node-at-is-x-mb-and-required-space-is-500-mb.html) ## Running Oracle Orachk on Microsoft Windows Throws '{oratab}' is empty Error The Windows `{oratab} is empty` error occurs when no database is installed, registry-key patterns are nonstandard, or the database initialization file is missing. Set `RAT_KEY_DB` for nonstandard registry keys when necessary, restore the expected `initSID.ora`, or explicitly provide the database home and name with `orachk -dbconfig db_home_path%db_name`. Read More: [Running Oracle Orachk on Microsoft Windows throws oratab is empty Error](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/running-oracle-orachk-on-microsoft-windows-throws-oratab-is-empty-error.html) ## Operating System Is Not Discovered Correctly When Orachk or Exachk cannot identify the operating system or derives an unsupported platform, set the `RAT_OS` environment variable to the correct platform identifier before running the tool. Read More: [Operating System Is Not Discovered Correctly](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/operating-system-is-not-discovered-correctly.html) ## Oracle Clusterware Software is Installed, but Cannot be Found Clusterware discovery depends on valid `oraInst.loc` and Oracle inventory files and paths. Correct those files or set `RAT_INV_LOC` to the inventory location and `RAT_CRS_HOME` to the Oracle Clusterware home. Read More: [Oracle Clusterware Software is Installed but Cannot be Found](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-clusterware-software-is-installed-but-cannot-be-found.html) ## Oracle Database Software Is Installed, but Cannot Be Found If the database software is installed but not discovered, set `RAT_ORACLE_HOME` to the applicable Oracle home. Orachk and Exachk will then perform checks for databases running from that home. Read More: [Oracle Database Software Is Installed But Cannot Be Found](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-database-software-is-installed-but-cannot-be-found.html) ## Oracle Database Software Is Installed, but Version cannot Be Found If the database software version cannot be detected, set the `RAT_DB` environment variable to the installed version, such as `11.2.0.3.0`, before running the checks. Read More: [Oracle Database Software Is Installed But Version Cannot Be Found](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-database-software-is-installed-but-version-cannot-be-found.html) ## Oracle ASM Software is Installed, but Cannot be Found When ASM is installed but not detected, set `RAT_ASM_HOME` to the applicable ASM or Grid home so Orachk and Exachk can locate the software. Read More: [Oracle ASM Software is Installed but Cannot be Found](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-asm-software-is-installed-but-cannot-be-found.html) ## Oracle Database Discovery Issues on Oracle Real Application Clusters (Oracle RAC) Systems On RAC systems, Orachk derives database homes from Cluster Registry resource profiles; invalid profiles can prevent discovery or connection. Temporarily specify databases with `-dbnames` or `RAT_DBNAMES`, and use `RAT_DBHOMES` to include additional database homes in recommended patch analysis. Read More: [Oracle Database Discovery Issues on Oracle RAC Systems](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-database-discovery-issues-on-oracle-rac-systems.html) ## Oracle Database Login Problems Database login failures usually result from insufficient privileges or incorrect Oracle environment settings. Test the connection independently with the appropriate operating-system user, `ORACLE_HOME`, `ORACLE_SID`, PATH, network alias, and SQL_Plus SYSDBA credentials; if SQL_Plus cannot connect, Orachk and Exachk cannot connect either. Read More: [Oracle Database Login Problems](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-database-login-problems.html) ## Remote Login Problems Remote checks require working SSH and SCP commands and suitable authentication, including passwordless root access or functional Expect handling where privileged operations are needed. Verify executable paths and manual remote commands, remove interactive profile prompts, enable debugging only under Oracle guidance, and use local collection with later report merging as a workaround. Read More: [Remote Login Problems](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/remote-login-problems.html) ## Permission Problems Ensure the Orachk and Exachk executables have mode 755 and that users can read and write the installation, temporary, working, and output directories. In clustered environments, install the tools in the recommended locations under the appropriate Grid Infrastructure owner or root so role separation does not block inventory and collection operations. Read More: [Permission Problems](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/permission-problems.html) ## Slow Performance, Skipped Checks, and Timeouts Slow or hung child processes are terminated by the watchdog and recorded as skipped checks. Investigate workload, remote profile prompts, and system performance; increase general, check-specific, or password-check timeouts through the relevant `RAT_*_TIMEOUT` variables, exclude problematic checks for separate runs, or tune database parallelism with `-dbparallel`, `-dbparallelmax`, or `-dbserial`. Read More: [Slow Performance Skipped Checks and Timeouts](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/slow-performance-skipped-checks-and-timeouts.html) ## Running Compliance Checks on a Subset of Oracle Home and Oracle Databases Use `-dbconfig` to restrict Orachk or Exachk checks to selected Oracle homes and databases when discovery is incomplete or multiple homes exist. Specify each home and database set as `dbhome%dbname`, separate multiple databases with colons, and separate home groups with commas. Read More: [Running Compliance Checks on a Subset of Oracle Home and Oracle Databases](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/running-compliance-checks-on-a-subset-of-oracle-home-and-oracle-databases.html) ## SSH Connection Timeout If an Exachk SSH session times out while searching database homes, set `ServerAliveInterval 30` in `/etc/ssh/ssh_config` on the machine where the run starts, then retry the check. Read More: [SSH Connection Timeout](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/ssh-connection-timeout.html) ## Oracle Exachk Prompts to Enter Names of RoCE Fabric Switches Exachk repeatedly prompts for RoCE switch names when they are not defined for supported Exadata environments. Add comma- or line-separated leaf and spine switch names to `switches.out`, pass them with `-switches`, or exclude switch checks with the appropriate `-excludeprofile` option. Read More: [Oracle Exachk Prompts to Enter Names of RoCE Fabric Switches](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/oracle-exachk-prompts-to-enter-names-of-roce-fabric-switches.html) ## Unable to Implement CA Certificates in Oracle Trace File Analyzer SSL socket failures after CA certificate configuration can occur when intermediate and server certificates are incorrectly combined in `caroot.cert.txt`, producing an empty certificate chain. Separate the certificates, recreate the server and client JKS files with the prescribed keytool imports, and verify that the resulting keystores contain matching private-key and trusted-certificate entries. Read More: [Unable to Implement CA Certificates in Oracle Trace File Analyzer](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/unable-to-implement-ca-certificates-in-oracle-trace-file-analyzer.html) ## AHF Insights Report Reloads Infinitely in Chrome and Edge On affected Windows systems, the CrowdStrike browser extension can cause AHF Insights `index.html` reports to reload continuously in Chrome and Edge. Open the report in another browser without the extension or in an incognito/private window where extensions are normally disabled; enterprise policy may prevent disabling the extension in standard browsing sessions. Read More: [AHF Insights Report Reloads Infinitely in Chrome and Edge](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/troubleshoot/ahf-insights-report-reloads-infinitely-in-chrome-and-edge.html) # Running the Installer Script Run the installer script to install Oracle Autonomous Health Framework or to just extract the content of the installer package. ## Oracle Autonomous Health Framework Installation Command-Line Options Understand the options that you can supply to the Oracle Autonomous Health Framework installer script to customize the installation. The Oracle Autonomous Health Framework installer script: * Takes you through an interview process if you do not specify any installation parameters. * Appends `/oracle.ahf` to `-ahf_loc` if it does not already exist. * Appends `/oracle.ahf/data` to `-data_dir` if it does not already exist. * Writes the log to the `/tmp/ahf_install_timestamp.log` file, for example, `/tmp/ahf_install_9263_2018_09_25-07_55_52.log`. ### Syntax ``` ahf_setup [-ahf_loc AHF Location] [-data_dir AHF Repository] [-nodes node1,node2] [-extract[orachk|exachk|-notfasetup]] [-force] [-local] [-silent] [-tmp_loc directory] [-debug [-level 1-6]] [-downgrade] [-saveinstaller] ``` ### Parameters ahf\_setup Command Parameters | Parameter | Description | | --- | --- | | {::nomarkdown}-ahf_loc{:/} | Specify the installation directory. Ensure that this directory exists before trying this option. | | {::nomarkdown}-data_dir{:/} | Specify the data directory where Oracle Autonomous Health Framework stores all the collections, metadata, and so on. Ensure that this directory exists before trying this option. | | {::nomarkdown}-nodes{:/} | By default, Oracle Autonomous Health Framework is installed on all the cluster nodes. Specify a comma-delimited list of nodes where you want to install AHF. | | {::nomarkdown}-extract{:/} | {::nomarkdown}

Extracts the files from the installer. This option is default for non-root users.
Specify the -notfasetup option just to extract and not to configure Oracle Trace File Analyzer.

Note:

  • You cannot use the -extract option as root to extract Oracle Trace File Analyzer binaries.
  • For -extract, only the install user must run AHF commands for the given installation.

Run the ahf_setup -extract [exachk\\\|orachk] command to install a local copy of Oracle ORAchk or Oracle EXAchk without installing the rest of AHF.

{:/} | | {::nomarkdown}-force{:/} | {::nomarkdown}The -force option is applicable only when you specify the compliance type orachk or exachk with the -extract option; otherwise, the installer script ignores the -force option.
-extract orachk\\\|exachk{:/} | | {::nomarkdown}-local{:/} | Installs only on the local node. | | {::nomarkdown}-silent{:/} | {::nomarkdown}Use this option for the Oracle Autonomous Health Framework installer script not to prompt any installation questions.
If you use the -silent option, then ensure that you use the -data_dir option. The installer script fails if you do not use the -data_dir option.{:/} | | {::nomarkdown}-tmp_loc{:/} | {::nomarkdown}Specify a temporary location for the Oracle Autonomous Health Framework installer script to extract the install archive. Ensure that this directory exists before trying this option.
Default: /tmp.{:/} | | {::nomarkdown}-perlhome{:/} | Specify a custom location for Perl binaries. | | {::nomarkdown}-debug{:/} | Debugs the Oracle Autonomous Health Framework installer script. | | {::nomarkdown}-level{:/} | {::nomarkdown}

Specify the Oracle Autonomous Health Framework Install debug level. Default 4 with option -debug.

{:/} | | {::nomarkdown}-downgrade{:/} | Downgrade to the last AHF version that was previously upgraded from. | | {::nomarkdown}-saveinstaller{:/} | Save the AHF Installer for later use in case a downgrade is needed. | ### Understanding the Location of the Data Directory * If you install Oracle Autonomous Health Framework using the `-data_dir` option, then the installer script uses the location that you specify. The installer script will not create the specified data directory, so ensure that this directory exists before trying the `-data_dir` option. You can specify a new data directory either under the current Oracle Trace File Analyzer install location or under a different directory. * If you install Oracle Autonomous Health Framework using the `-silent` option, then ensure that you use the `-data_dir` option; otherwise, the installer script will fail. * If you install Oracle Autonomous Health Framework without the `-data_dir` option, then the installer script will list all possible options: * Oracle Autonomous Health Framework installation location (`-ahf_loc`) if the free space is more than 5 GB. * Oracle Trace File Analyzer repository if installed outside the Oracle Grid Infrastructure Home. * Directory one level above the Oracle Grid Infrastructure Base. * Option to enter a different directory. * If you do not use the `-silent` option and do not specify `-ahf_loc` and `-data_dir`, then the installer script displays the default options for you to confirm. For example: ``` # /tmp/ahf_setup -nodes node1 AHF Installation Log : /tmp/ahf_install_15992_2019_10_10-08_07_38.log Starting Autonomous Health Framework (AHF) Installation AHF Version: 193000 Build Date: 201910100757 Default AHF Location : /opt/oracle.ahf Do you want to update default AHF Location ? Y|[N] : AHF Location : /opt/oracle.ahf Choose Data Directory from below options : 1. /u01/app [Free Space : 6742 MB] 2. Enter a different Location Choose Option [1 - 2] : 1 AHF Data Directory : /u01/app/oracle.ahf/data Do you want to add AHF Notification Email IDs ? [Y]|N : n Extracting AHF to /opt/oracle.ahf ``` Example `ahf_setup -downgrade` ``` # ahf_setup -downgrade AHF Installer for Platform Linux Architecture x86_64 AHF Installation Log : /tmp/ahf_install_244000_23265_2024_04_29-05_38_39.log Starting Autonomous Health Framework (AHF) Installation AHF Version: 24.4.0 Build Date: 202404290909 AHF is already installed at /opt/oracle.ahf Installed AHF Version: 24.5.0 Build Date: 202404262209 Do you want to downgrade AHF ? [Y]|N : Downgrading AHF to 24.4.0 AHF is successfully downgraded to 24.4.0 Setting up AHF CLI and SDK Starting ORAchk Scheduler from AHF .------------------------------------------------------------------------------------------------------. | Host | Status of TFA | PID | Port | Version | Build ID | Inventory Status | +---------------+---------------+-------+------+------------+-----------------------+------------------+ | testhost | RUNNING | 26746 | 5000 | 24.4.0.0.0 | 240400020240429090917 | COMPLETE | '---------------+---------------+-------+------+------------+-----------------------+------------------' Moving /tmp/ahf_install_244000_23265_2024_04_29-05_38_39.log to /u01/app/oracle/oracle.ahf/data/testhost/diag/ahf/ ``` # AHFCTL Command Reference ## Running AHFCTL Commands to Manage EMail Configuration for All AHF Tools This page documents commands for configuring, viewing, validating, clearing, and testing SMTP settings used by AHF tools. `ahfctl setsmtp` manages server, credentials, sender and recipient addresses, ports, SSL, authentication, and copy recipients; `getsmtp` queries individual or all settings; `checksmtp` validates stored configuration and optional attachments; `unsetsmtp` removes selected or all settings, including defaults; and `sendmail` sends a test message with optional recipients, subject, body, and attachment. Read More: [Running AHFCTL Commands to Manage EMail Configuration for All AHF Tools](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-manage-email-configuration-for-all-ahf-tools.html) ## Running AHFCTL Update Commands to Automatically Patch Oracle Autonomous Health Framework This page describes AHF commands for configuring and executing automatic metadata updates, which require AHF install-user privileges. `ahfctl setupdate` configures the staging location, autoupdate state, REST service, filesystem type, and 1–30-day frequency; `getupdate` displays these settings; `unsetupdate` removes selected or all settings; and `update` downloads or processes available metadata, after which the update archive may need to be applied on cluster nodes. A staged update should be tested in pre-production before being distributed to production systems. Read More: [Running AHFCTL Update Commands to Automatically Patch Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-update-commands-to-automatically-patch-oracle-autonomous-health-framework.html) ## Running AHFCTL Update Commands to Apply AHF Metadata and Framework Updates This page covers applying, inspecting, rolling back, and removing backups for AHF metadata, framework, Java, and configuration-file updates. `applyupdate` installs an update archive on the local node and must be run on every cluster node, `queryupdate` reports applied updates by ID or in full, `rollbackupdate` restores a specified or previous state, and `deleteupdatebackup` removes historical backup directories when space is required; deleting backups in order and never removing the current update preserves rollback capability. The page also describes Java-only updates and newer configuration-file updates, noting that these legacy commands are deprecated in favor of newer AHF software commands. Read More: [Running AHFCTL Update Commands to Apply AHF Metadata and Framework Updates](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-update-commands-to-apply-ahf-metadata-and-framework-updates.html) ## Running AHFCTL Upgrade Commands to Upgrade Oracle Autonomous Health Framework This page documents root-level commands for configuring and performing complete AHF version upgrades. `getupgrade` reads upgrade settings from `ahf.properties`, optionally as JSON; `setupgrade` configures automatic upgrade, staging location, schedule, filesystem, temporary directory, installer cleanup, REST service, frequency, and related autoupdate behavior; `unsetupgrade` removes selected or all settings; and `upgrade` installs the newest available AHF version from a staging location or REST endpoint. Custom download ports must be configured separately when the default HTTPS port is not used. Read More: [Running AHFCTL Upgrade Commands to Upgrade Oracle Autonomous Health Framework](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-upgrade-commands-to-upgrade-oracle-autonomous-health-framework.html) ## Running AHFCTL Upload Commands to Upload Diagnostics This page explains how to configure, inspect, validate, remove, and use AHF upload endpoints for diagnostics and reports. `setupload` defines HTTPS, SFTP, or SQLNet destinations, credentials, URLs, proxies, security, tokens, headers, database targets, and custom ports; `getupload` retrieves configuration details; `checkupload` validates a named configuration; `unsetupload` removes selected or all settings; and `upload` transfers a specified file, commonly to My Oracle Support. The `mos` configuration name is required for MOS integrations, and Object Store endpoints can support automatic AHF Insights report uploads. Read More: [Running AHFCTL Upload Commands to Upload Diagnostics](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-upload-commands-to-upload-diagnostics.html) ## Running AHFCTL Commands to Manage the Scheduler for Oracle Autonomous Health Framework Components This page describes root- or sudo-level control of the AHF scheduler and its TFA and compliance daemons. `startahf` starts TFA, Oracle Orachk, and Oracle Exachk schedulers individually or together, with optional component arguments; `statusahf` reports daemon state, hosts, processes, versions, schedules, retention, previous and next runs, and system health; and `stopahf` stops selected or all scheduler components, including active compliance scheduling and related services. Read More: [Running AHFCTL Commands to Manage the Scheduler for Oracle Autonomous Health Framework Components](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-manage-the-scheduler-for-oracle-autonomous-health-framework-components.html) ## Running AHFCTL Commands to Manage Cell Switches Databases and exacli Passwords This page documents privileged password-management commands for cells, switches, databases, and exacli users. `checkpassword` verifies passwords for selected nodes, databases, users, or exacli accounts; `setpassword` establishes passwords for the specified targets; and `unsetpassword` removes them. Node and database selections are supplied as comma-delimited lists, with `-user` identifying the account and `-exacli` targeting a cell’s exacli user. Read More: [Running AHFCTL Commands to Manage Cell Switches Databases and exacli Passwords](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-manage-cell-switches-databases-and-exacli-passwords.html) ## Running AHFCTL Commands to Get the Repository Locations of Oracle Autonomous Health Framework Components This page describes the privileged `ahfctl showrepo` command, which displays repository information for all AHF components or specifically for TFA or compliance components. Output includes each node’s repository location, maximum capacity, current and free space, and repository status, enabling administrators to inspect storage allocation and availability across the environment. Read More: [Running AHFCTL Commands to Get the Repository Locations of Oracle Autonomous Health Framework Components](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-get-the-repository-locations-of-oracle-autonomous-health-framework-components.html) ## Running AHFCTL Commands to Import Oracle Orachk or Oracle Exachk Wallet Details into Oracle Autonomous Health Framework Wallet and Configuration This page documents the privileged `ahfctl import` command for migrating Oracle Orachk or Oracle Exachk wallet details from versions 19.2.0 or earlier into the AHF wallet and configuration. The command accepts the `wallet` import type and the filesystem location of the source wallet, allowing existing authentication details to be incorporated into AHF. Read More: [Running AHFCTL Commands to Import Oracle Orachk or Oracle Exachk Wallet Details into Oracle Autonomous Health Framework Wallet and Configuration](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-import-oracle-orachk-or-oracle-exachk-wallet-details-into-oracle-autonomous-health-framework-wallet-and-configuration.html) ## Running AHFCTL Commands to Limit CPU and Memory Usage This page covers Linux 64 resource controls for TFA, requiring root or sudo privileges and, for setting limits, a full root installation of AHF. `getresourcelimit` displays CPU or memory limits, `setresourcelimit` applies CPU, kernel-memory, or combined memory-and-swap limits using cgroups v1 or v2, `unsetresourcelimit` removes them, and `printresourcestats` reports usage statistics for managed resources. CPU and memory values have defined minimums and maximums, while `-force` permits exceeding calculated maximums. Read More: [Running AHFCTL Commands to Limit CPU and Memory Usage](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-limit-cpu-and-memory-usage.html) ## Running AHFCTL Commands to Collect Storage Server Diagnostic Package This page documents the privileged `ahfctl celldiagcollect` command for collecting storage-server diagnostic packages. Administrators can specify the collection start time, duration of one to six hours, an eligibility timeframe, the destination path, and polling timeouts for newly submitted or previously submitted package requests. These options control which logs and traces are collected, where the package is copied, and how long AHF waits for package generation. Read More: [Running AHFCTL Commands to Collect Storage Server Diagnostic Package](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-collect-storage-server-diagnostic-package.html) ## Running AHFCTL Commands to Manage Service Upload Parameters This page documents the deprecated service-upload commands `getserviceupload`, `setserviceupload`, and `unsetserviceupload`, which were removed in AHF 23.3. They previously retrieved, configured, or cleared service upload credentials, HTTPS URLs, proxies, keystore types, and certificate-validation behavior, with root or non-root execution permitted. Administrators should use the newer named-endpoint commands `getupload`, `setupload`, and `unsetupload` instead. Read More: [Running AHFCTL Commands to Manage Service Upload Parameters](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-manage-service-upload-parameters.html) ## AHFCTL Compliance Framework Oracle Orachk and Oracle Exachk Command-Line Options The `ahfctl compliance` command runs compliance checks across Oracle Engineered and non-engineered systems, supporting check selection, database, node, cell, switch, and storage targeting, parallel or serial execution, discovery caching, profiles, upgrades, diagnostics, reporting, repair, encryption, email, remote execution, wallet configuration, and upload management. Deprecated upload and sanitization parameters were removed in release 23.3 and replaced by `ahfctl setupload`, `unsetupload`, `getupload`, `checkupload`, and `redact`; the command also includes specialized options for application continuity, CVU, Exadata, ORDS, pre- and post-upgrade checks, and autorun scheduling. Read More: [AHFCTL Compliance Framework Oracle Orachk and Oracle Exachk Command-Line Options](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/ahfctl-compliance-framework-oracle-orachk-and-oracle-exachk-command-line-options.html) ## Running AHFCTL Commands to Sanitize Sensitive Information and Reverse Map Sanitized Elements The `ahfctl redact` command sanitizes sensitive information in regular files, ZIP files, and directories using masking or substitution-map sanitization, optionally limited to system, database, or user-data entities and written to a specified output directory; it is unsupported on Microsoft Windows and does not redact automatic Service Request collections. The `ahfctl rmap` command reverse-maps sanitized values generated by Oracle Trace File Analyzer and Orachk, displaying either selected substituted strings or all available original values, and is also unsupported on Microsoft Windows. Read More: [Running AHFCTL Commands to Sanitize Sensitive Information and Reverse Map Sanitized Elements](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-sanitize-sensitive-information-and-reverse-map-sanitized-elements.html) ## Running AHFCTL Commands to Manage InfiniBand and RoCE Switches The `ahfctl switch` command enables privileged AHF installation users with root privileges to configure, inspect, deconfigure, and debug InfiniBand and RoCE switch settings, with optional switch lists and JSON status output. RoCE switches are not discovered automatically and must be supplied through `RAT_SWITCHES` or the configuration command; alternate connection users can be specified with `RAT_IBSWITCH_USER`, and configuration can either receive a comma-delimited list or prompt interactively for switch names. Read More: [Running AHFCTL Commands to Manage InfiniBand and RoCE Switches](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-manage-infiniband-and-roce-switches.html) ## Running AHFCTL Commands to Uninstall AHF The `ahfctl uninstall` command stops Oracle Orachk and Oracle Trace File Analyzer and removes the Oracle Autonomous Health Framework installation directory. By default, it uninstalls AHF across all configured nodes; `-local` limits removal to the local node, `-silent` suppresses uninstall prompts, and `-deleterepo` additionally deletes the AHF repository. Read More: [Running AHFCTL Commands to Uninstall AHF](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/ahfctl-command-reference/running-ahfctl-commands-to-uninstall-ahf.html) # TFACTL Command Reference Learn about the command-line tools and commands for installing, configuring, managing, monitoring, and running compliance checks with Oracle Autonomous Health Framework (AHF). ## Running Oracle Trace File Analyzer Administration Commands Oracle Trace File Analyzer administration commands require root access to `tfactl` or equivalent `sudo` privileges. Basic commands start, stop, enable, disable, uninstall, synchronize nodes, restrict protocols, and report daemon status on the local node. Read More: [Running Oracle Trace File Analyzer Administration Commands](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/running-oracle-trace-file-analyzer-administration-commands.html) ## tfactl access The `tfactl access` command manages controlled non-root access to Oracle Trace File Analyzer and diagnostic collections. It supports listing, adding, removing, blocking, unblocking, promoting, demoting, granting, revoking, resetting, and removing users, with optional local or JSON output. AHF provides platinum and privileged-compliance-checks roles with additional diagnostic, configuration, metadata, auto-upgrade, and root compliance-check privileges; Oracle Home owners, DBA groups, and ASM groups are added by default during installation or upgrade. Read More: [tfactl access](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-access.html) ## tfactl availability The `tfactl availability` command enables or disables Availability Score resources and searches telemetry-cache data. Resources can be selected by type, key, and value or listed for selection; disabling supports temporary periods specified in days, hours, or minutes, with a seven-day default. The `dumpcache` operation optionally filters results by data type. Read More: [tfactl availability](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-availability.html) ## tfactl blackout The `tfactl blackout` command adds, removes, or displays granular diagnostic-collection suppressions for hosts, Clusterware, ASM, databases, backups, Data Guard, tablespaces, PDBs, listeners, services, and operating-system records. Blackouts can target specific or all resources and events, apply locally or cluster-wide, include containers or PDBs, specify a reason and timeout, and optionally permit diagnostic collection; the default duration is 24 hours. Read More: [tfactl blackout](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-blackout.html) ## tfactl cell The `tfactl cell` command displays and manages storage-cell configuration, particularly for Exadata environments. `status` reports cell availability, `config` shows configuration and wallet details, `configure` enables cell collections that were not completed during installation or upgrade, and `deconfigure` removes all storage-cell configuration. Read More: [tfactl cell](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-cell.html) ## tfactl checkupload The deprecated `tfactl checkupload` command validates configured upload parameters and can be run by root or non-root users. It optionally accepts a configuration name, such as a My Oracle Support upload profile; Oracle recommends using `ahfctl checkupload` instead. Read More: [tfactl checkupload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-checkupload.html) ## tfactl dbcheck The `tfactl dbcheck` command collects diagnostic information from an Oracle Exadata machine to identify operating-system, filesystem, memory, and I/O issues. It is available only on Exadata machines running Oracle Linux and reports checks as successful or failed, including filesystem usage and kernel-parameter comparisons with expected values. Read More: [tfactl dbcheck](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-dbcheck.html) ## tfactl diagnosetfa The `tfactl diagnosetfa` command collects Oracle Trace File Analyzer diagnostic data from the local node to investigate TFA issues. Options specify a repository directory, a tag for the collection directory, and whether diagnostics should run only locally. Read More: [tfactl diagnosetfa](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-diagnosetfa.html) ## tfactl disable The `tfactl disable` command stops automatic restarting of the Oracle Trace File Analyzer daemon and prevents it from restarting after failures or system reboots. Read More: [tfactl disable](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-disable.html) ## tfactl enable The `tfactl enable` command enables automatic restarting of the Oracle Trace File Analyzer daemon after a failure or system reboot. Read More: [tfactl enable](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-enable.html) ## tfactl get The `tfactl get` command displays Oracle Trace File Analyzer configuration values for selected parameters and optionally across specified nodes, with matching output support. Available settings cover diagnostics, tracing, repositories, retention and purge policies, disk monitoring, compliance indexes, redaction, discovery, inventory, networking, and collection behavior. Read More: [tfactl get](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-get.html) ## tfactl floodcontrol The `tfactl floodcontrol` command controls repeated collection of identical events within a defined time window. It can print, update, or clear event rules and configure the event name, collection limit, initial limit interval in minutes, and pause interval in minutes. Read More: [tfactl floodcontrol](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-floodcontrol.html) ## tfactl getresourcelimit The deprecated `tfactl getresourcelimit` command reports Oracle Trace File Analyzer CPU and memory usage limits, optionally filtered by tool or resource type. Only TFA can currently be selected as the tool, and Oracle recommends using `ahfctl getresourcelimit` instead. Read More: [tfactl getresourcelimit](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-getresourcelimit.html) ## tfactl getupload The deprecated `tfactl getupload` command displays configured upload settings and can be run by root or non-root users. It supports retrieving all settings or selected connection, authentication, proxy, HTTPS, security, database, table, and header parameters for a named upload configuration; Oracle recommends using `ahfctl getupload` instead. Read More: [tfactl getupload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-getupload.html) ## tfactl host The `tfactl host` command adds or removes hosts from the Oracle Trace File Analyzer cluster configuration. Added hosts are authenticated through synchronized certificates, and their host lists are synchronized before registration; once successfully added, cluster-wide commands become available across registered nodes. The current host list is displayed with `tfactl print hosts`. Read More: [tfactl host](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-host.html) ## tfactl insight The `tfactl insight` command generates AHF Insights reports from selected or all cluster nodes over a specified time range. It supports refreshing data, retaining input collections, identifying the requestor, checking status, and uploading reports to a pre-authenticated URL; the `-onlyinsightsupload` option uploads only the Insights archive. Read More: [tfactl insight](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-insight.html) ## tfactl index The `tfactl index` command indexes Oracle ORAchk and EXAchk compliance data supplied as a JSON string or file. The `result` category indexes compliance-check results, while `metadata` indexes run metadata. Read More: [tfactl index](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-index.html) ## tfactl print The `tfactl print` command reads and displays Oracle Trace File Analyzer information from Berkeley DB, including status, components, configuration, scanned directories, cluster hosts, actions, repository usage, run mode, suspended collections, protocols, SMTP settings, and collections. Collection output can be filtered by status or time and formatted as standard text, JSON, pretty JSON, or CSV; configuration output includes operational limits, tracing, monitoring, retention, and purge settings. Read More: [tfactl print](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-print.html) ## tfactl print inventory The `tfactl print inventory` command displays metadata for inventoried files, optionally for a specified file path and selected nodes. Results identify the hostname, absolute path, component, filename, date pattern, and last-modified time. Read More: [tfactl print inventory](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-print-inventory.html) ## tfactl print syncstatus The `tfactl print syncstatus` command reports whether Oracle Trace File Analyzer is synchronized across cluster nodes. Normal output lists each node and its synchronization state, while `-short` returns a single TRUE or FALSE summary indicating whether all nodes are synchronized. Read More: [tfactl print syncstatus](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-print-syncstatus.html) ## tfactl purgeindex The `tfactl purgeindex` command deletes indexed Oracle ORAchk or EXAchk compliance results or metadata, optionally matching JSON content or data from a specified number of preceding hours or days. Compliance-index retention can also be controlled through maximum run-count and maximum-size thresholds, which remove older or recent data when limits are exceeded. Read More: [tfactl purgeindex](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-purgeindex.html) ## tfactl purgeinventory The `tfactl purgeinventory` command deletes file metadata from the Oracle Trace File Analyzer inventory for a specified file and node scope. The optional `-delayreload` flag postpones restoration of the file data until the next inventory operation. Read More: [tfactl purgeinventory](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-purgeinventory.html) ## tfactl queryindex The `tfactl queryindex` command searches indexed compliance results or metadata using filters such as check ID, target, severity, check name, selected fields, and time range. Results can be narrowed to targets or specific checks and returned in structured JSON, with result records containing compliance status, execution details, target information, and associated metadata. Read More: [tfactl queryindex](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-queryindex.html) ## tfactl rediscover The `tfactl rediscover` command discovers newly added components and updates Oracle Trace File Analyzer inventory. It performs a full discovery by default, or a lighter discovery when `-mode lite` is specified. Read More: [tfactl rediscover](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-rediscover.html) ## tfactl refreshconfig The `tfactl refreshconfig` command refreshes and manages Oracle Trace File Analyzer cron jobs. It can refresh background jobs, list configured entries and schedules, reload jobs after configuration changes, or specify the TFA configuration environment role. Read More: [tfactl refreshconfig](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-refreshconfig.html) ## tfactl refreshconfig modifycron The `tfactl refreshconfig modifycron` command modifies a specific Oracle Trace File Analyzer cron entry. It enables or disables the entry and sets or clears the environments where it is valid or excluded, using the cron identifier and supported deployment types. Read More: [tfactl refreshconfig modifycron](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-refreshconfig-modifycron.html) ## tfactl restrictprotocol The `tfactl restrictprotocol` command restricts a specified communication protocol, optionally forcing the change. For example, it can restrict TLSv1. Read More: [tfactl restrictprotocol](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-restrictprotocol.html) ## tfactl sendmail The `tfactl sendmail` command sends a test email to a specified address to verify that the configured SMTP server and email settings are functioning correctly. Read More: [tfactl sendmail](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-sendmail.html) ## tfactl set The `tfactl set` command enables, disables, or modifies Oracle Trace File Analyzer configuration settings, including automatic diagnostics, insights, trimming, logging, repository size and location, retention and purge policies, security, disk-usage monitoring, collection limits, Data Guard metrics, indexing, and network behavior. Options such as `-c` and `-local` control whether settings apply across the cluster or only to the local node; examples demonstrate configuring automatic collection, repository size, trace levels, log limits, ports, disk monitoring, snapshot intervals, alert-log trimming, and rediscovery. Read More: [tfactl set](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-set.html) ## tfactl setresourcelimit The deprecated `tfactl setresourcelimit` command restricts Oracle Trace File Analyzer CPU or memory consumption and should be replaced by `ahfctl setresourcelimit`. It supports CPU limits within defined minimum and maximum bounds, system memory limits through `kmem`, combined system and swap limits through `swmem`, and currently applies to the TFA tool. Read More: [tfactl setresourcelimit](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-setresourcelimit.html) ## tfactl setupload The deprecated `tfactl setupload` command configures upload endpoints and should be replaced by `ahfctl setupload`. It supports HTTPS, SFTP, and SQLNET destinations; credentials, servers, URLs, proxies, authentication behavior, security validation, tokens, headers, requests, database connect strings, and upload tables can be configured by root or non-root users. A named configuration, commonly `mos`, can then be used to upload collections to My Oracle Support. Read More: [tfactl setupload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-setupload.html) ## tfactl showrepo The deprecated `tfactl showrepo` command displays repository locations for Oracle Autonomous Health Framework components and should be replaced by `ahfctl showrepo`. Users can display repositories for all components, Oracle Trace File Analyzer only, or compliance tools such as Oracle ORAchk and Oracle EXAchk. Read More: [tfactl showrepo](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-showrepo.html) ## tfactl start The `tfactl start` command starts the Oracle Trace File Analyzer daemon on the local node and can also start a specified support tool. Read More: [tfactl start](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-start.html) ## tfactl startahf The deprecated `tfactl startahf` command starts schedulers for Oracle Autonomous Health Framework components and should be replaced by `ahfctl startahf`. It can start Oracle Trace File Analyzer, compliance daemons, or both, optionally passing supported TFA, Oracle ORAchk, and Oracle EXAchk startup arguments. Read More: [tfactl startahf](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-startahf.html) ## tfactl status The `tfactl status` command checks the current run status of Oracle Trace File Analyzer. Read More: [tfactl status](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-status.html) ## tfactl statusahf The deprecated `tfactl statusahf` command checks scheduler and daemon status for Oracle Autonomous Health Framework components and should be replaced by `ahfctl statusahf`. It reports the status of TFA, compliance components, or all supported components. Read More: [tfactl statusahf](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-statusahf.html) ## tfactl stop The `tfactl stop` command stops the Oracle Trace File Analyzer daemon on the local node and can also stop a specified support tool. Read More: [tfactl stop](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-stop.html) ## tfactl stopahf The deprecated `tfactl stopahf` command stops schedulers for Oracle Autonomous Health Framework components and should be replaced by `ahfctl stopahf`. It can stop TFA, compliance daemons, or all supported component daemons. Read More: [tfactl stopahf](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-stopahf.html) ## tfactl syncnodes The `tfactl syncnodes` command generates and distributes Oracle Trace File Analyzer certificates among TFA nodes. It can regenerate certificates with a specified key size, remove certificates, operate only on the local node, and run silently in the background without interactive prompts. Read More: [tfactl syncnodes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-syncnodes.html) ## tfactl uninstall The `tfactl uninstall` command removes Oracle Autonomous Health Framework by stopping Oracle ORAchk and TFA and deleting the installation directory. It can uninstall locally or across configured nodes, suppress confirmation prompts, and optionally delete the AHF repository. Read More: [tfactl uninstall](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-uninstall.html) ## tfactl upload The `tfactl upload` command uploads collections or files on demand and can be run by root or non-root users. It accepts an upload configuration name, Service Request or target identifier, and file name; configured destinations such as My Oracle Support can also be used through related diagnostic-collection workflows. Read More: [tfactl upload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-upload.html) ## tfactl unsetresourcelimit The deprecated `tfactl unsetresourcelimit` command removes CPU or memory restrictions previously applied to Oracle Trace File Analyzer and should be replaced by `ahfctl unsetresourcelimit`. It supports selecting the TFA tool and either CPU or memory resources. Read More: [tfactl unsetresourcelimit](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-unsetresourcelimit.html) ## tfactl unsetupload The deprecated `tfactl unsetupload` command removes configured upload parameters and should be replaced by `ahfctl unsetupload`. It can unset all settings or selected endpoint attributes, including configuration names, credentials, servers, URLs, proxies, authentication, tokens, headers, security settings, database connection strings, and upload tables. Read More: [tfactl unsetupload](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-unsetupload.html) ## tfactl version The `tfactl version` command reports the versions of Oracle Autonomous Health Framework components. It can display versions for all components, Oracle Trace File Analyzer, or compliance tools such as Oracle ORAchk and Oracle EXAchk. Read More: [tfactl version](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-version.html) ## Running Oracle Trace File Analyzer Summary and Analysis Commands This section introduces Oracle Trace File Analyzer commands for viewing deployment and operational summaries, checking status, and reviewing changes and events detected across the environment. Read More: [Running Oracle Trace File Analyzer Summary and Analysis Commands](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/running-oracle-trace-file-analyzer-summary-and-analysis-commands.html) ## tfactl analyze The `tfactl analyze` command analyzes database, ASM, Grid Infrastructure, ACFS, system, OSWatcher, and related logs. It can summarize common messages, search for text within specified time ranges, classify messages as errors, warnings, or generic events, analyze OSWatcher statistics, filter by component and node, produce verbose or file output, and generate timelines for selected logs. Time filters, component selection, message type, database context, JSON-like search behavior, and oratop options provide targeted investigation capabilities. Read More: [tfactl analyze](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-analyze.html) ## tfactl changes The `tfactl changes` command reports configuration and system changes detected by Oracle Trace File Analyzer over a specified interval or date. Reports can be filtered by change type and node and optionally generated in JSON format; supported categories include database and operating-system parameters, packages, Oracle homes, and patches. Read More: [tfactl changes](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-changes.html) ## tfactl events The `tfactl events` command displays detected database, ASM, Clusterware, and alert-log events. Users can filter by keyword, component, database, instance, source file, node-related time range, or date, and can request JSON output containing all or selected fields. TFA recognizes a broad set of Oracle error and failure events, including internal errors, instance failures, corruption, resource exhaustion, ASM issues, and Clusterware problems. Read More: [tfactl events](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-events.html) ## tfactl isa The `tfactl isa` command displays the Infrastructure Service Automation score. It can include the availability score, show all available details, and limit results to selected nodes, all nodes, or the local node. Read More: [tfactl isa](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-isa.html) ## tfactl param The `tfactl param` command displays operating-system and database parameter values and replaces `tfactl run param`. Users can filter by parameter type, parameter name, database, and node, request JSON output, or refresh the underlying parameter data; supported examples include SGA settings, database uniqueness, and shared-memory limits. Read More: [tfactl param](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-param.html) ## tfactl run The `tfactl run` command executes inventory, one-time scans, or Oracle Trace File Analyzer support tools, although `tfactl run param` is being replaced by `tfactl param`. Available tools include Oracle ORAchk, oratop, OSWatcher Analyzer, Procwatcher, alert summaries, Clusterware logs, grep, history, file searches, log management, menus, parameter inspection, process and stack inspection, system summaries, log tailing, triage, and file editing. Read More: [tfactl run](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-run.html) ## tfactl search The `tfactl search` command searches metadata stored in the Oracle Trace File Analyzer index. It accepts JSON search criteria, can restrict returned JSON fields, and can display available datatypes or the fields associated with a selected datatype. Read More: [tfactl search](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-search.html) ## tfactl summary The `tfactl summary` command provides a deployment and system-status summary for Oracle Trace File Analyzer. It can report overview, Clusterware, ASM, ACFS, database, Exadata, patch, listener, network, operating-system, TFA, and summary metadata information, with options for JSON or HTML output, console printing, silent operation, history, node selection, and help. Read More: [tfactl summary](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-summary.html) ## tfactl toolstatus The `tfactl toolstatus` command displays the deployment, version, and runtime status of Oracle Trace File Analyzer support tools across nodes. Results distinguish tools that are deployed and available, configured but not running, and currently running, covering development tools, support-tool bundles, and TFA utilities. Read More: [tfactl toolstatus](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-toolstatus.html) ## Running Oracle Trace File Analyzer Diagnostic Collection Commands This section introduces Oracle Trace File Analyzer commands used to collect diagnostic data for troubleshooting and support. Read More: [Running Oracle Trace File Analyzer Diagnostic Collection Commands](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/running-oracle-trace-file-analyzer-diagnostic-collection-commands.html) ## tfactl collection The `tfactl collection` command manages existing diagnostic collections. It can stop a collection by ID and list the contents of a specified collection archive or all archives within a named collection, including nested ZIP files. Read More: [tfactl collection](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-collection.html) ## tfactl diagcollect The `tfactl diagcollect` command performs on-demand diagnostic collections, including default, event-driven SRDC, custom, and AHF Insights collections. It supports component, node, cell, time-range, output, tagging, trimming, copying, dry-run, background, core-file, directory and file selection, redaction or sanitization, archive merging, upload, and foreground-log filtering options. Collections may require authorized users, and from AHF 25.3 diagnostic or insights periods must be at least 15 minutes; AHF also supports uploading Insights reports to pre-authenticated locations. Read More: [tfactl diagcollect](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-diagcollect.html) ## Smart Problem Classification to Help Oracle Support Resolve Service Requests Faster Smart Problem Classification helps AHF identify the specific problem associated with a diagnostic collection by analyzing relevant events and presenting selectable events or hierarchical problem categories. It records the selected problem, time, and location to support faster Service Request resolution, is enabled by default for applicable `tfactl diagcollect` operations, and can be disabled or bypassed with configuration or command options. The feature is unavailable on AIX and Microsoft Windows and is not used with several specialized collection switches and modules. Read More: [Smart Problem Classification to Help Oracle Support Resolve Service Requests Faster](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/smart-problem-classification-to-help-oracle-support-resolve-service-requests-faster.html) ## tfactl diagcollect -srdc The `tfactl diagcollect -srdc` command runs a Service Request Data Collection using a specified profile, database, time range, tag, and output filename. Profiles cover database, ASM, Clusterware, listener, Data Pump, RMAN, performance, installation, upgrade, Enterprise Manager, GoldenGate, operating-system, and many Oracle error scenarios. The command can also collect CRS, ASM, and cell information when cells are configured in TFA, including support for selected cell-related CRS errors and explicit cell-node targeting. Read More: [tfactl diagcollect -srdc](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-diagcollect-srdc.html) ## tfactl directory The `tfactl directory` command adds, removes, modifies, and lists directories whose trace or log files are analyzed and collected by Oracle Trace File Analyzer. Directory settings control public or private access, filename and time exclusions, collect-all behavior, and node scope. Added directories are recorded in TFA metadata, and when their component or database context cannot be inferred, the user must provide the appropriate classification details. Read More: [tfactl directory](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-directory.html) ## tfactl ips The `tfactl ips` command collects and manages Automatic Diagnostic Repository diagnostic data through Incident Packaging Service operations. It supports creating, populating, correlating, finalizing, generating, inspecting, deleting, and unpacking diagnostic packages; adding or removing incidents and files; copying files into or out of ADR; managing remote incident keys; viewing problems, incidents, files, package details, manifests, and metadata; and changing or displaying packaging configuration. Packages may be built from incidents, problems, problem keys, or time ranges, with BASIC, TYPICAL, or ALL correlation levels, and generated as complete or incremental ZIP archives. Read More: [tfactl ips](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-ips.html) ## tfactl managelogs The `tfactl managelogs` command manages ADR log and trace files by purging data or displaying storage usage and volume changes. Purging can target files older than a specified number of minutes, hours, or days, Oracle Grid Infrastructure logs, selected or all database logs, or HAMI trace and output directories; the `-dryrun` option estimates or reports files that would be removed without deleting them. Show operations provide corresponding usage or variation information for these scopes. Read More: [tfactl managelogs](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-managelogs.html) ## tfactl purge The `tfactl purge` command deletes aged collections and log files from AHF components on the local node. It can target TFA data, compliance data, component collections, OSWatcher files, managelogs files, or other support-tool directories, with age thresholds specified in hours or days. The default scope covers applicable purgeable data, while `-dryrun` lists files eligible for removal without deleting them; successful executions report the deleted paths. Read More: [tfactl purge](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/tfactl-command-reference/tfactl-purge.html) # Compliance Framework (Oracle Orachk and Oracle Exachk) Command-Line Options Review the list of Compliance Framework (Oracle Orachk and Oracle Exachk) command-line options. ## Syntax ``` $ orachk [options] ``` ``` [-h] [-a] [-b] [-v] [-p] [-m] [-u] [-f] [-o] [-clusternodes clusternames] [-failedchecks previous_result] [-nordbms] [-output path] [-dbnames dbnames] [-localonly] [-debug] [-dbnone | -dball] [-c] [-upgrade | -noupgrade] [-syslog] [-skip_usr_def_checks] [-checkfaileduploads] [-uploadfailed all | comma-delimited list of collections] [-fileattr [start | check | remove ] [-includedir path ] [-excludediscovery] [-baseline path [-fileattronly] [-testemail all | "NOTIFICATION_EMAIL=comma-delimited list of email addresses"] [-setdbupload all | db upload variable, for example, RAT_UPLOAD_CONNECT_STRING, RAT_UPLOAD_PASSWORD] [-unsetdbupload all | db upload variable, for example, RAT_UPLOAD_CONNECT_STRING, RAT_UPLOAD_PASSWORD] [-checkdbupload] [-getdbupload] [-cmupgrade] [-sendemail "NOTIFICATION_EMAIL=comma-delimited list of email addresses"] [-nopass] [-noscore] [-showpass] [-show_critical] [-diff Old Report New Report [-outfile Output HTML] [-force]] [-merge report 1 report 2 [-force]] [-tag tagname] [-nodaemon] [-profile asm | clusterware | corroborate | dba | ebs | emagent | emoms | em | goldengate | hardware | maa | oam | oim | oud | ovn | peoplesoft | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | zfs ] [-excludeprofile asm | clusterware | corroborate | dba | ebs | emagent | emoms | em | goldengate | hardware | maa | oam | oim | oud | ovn | peoplesoft | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | zfs ] [-includeprofile asm | clusterware | corroborate | dba | ebs | emagent | emoms | em | goldengate | hardware | maa | oam | oim | oud | ovn | peoplesoft | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | zfs ] [-acchk -javahome path to jdk8 -asmhome path to asm-all-5.0.3.jar -appjar directory where jar files are present for concrete class -apptrc directory where trace files are present for coverage class] [-check check ids | -excludecheck check ids] [-zfsnodes nodes] [-zfssa appliance names] [-dbserial | -dbparallel [n] | -dbparallelmax] [-idmpreinstall | -idmpostinstall | -idmruntime] [-topology topology.xml | -credconfig credconfig] | -idmdbpreinstall | -idmdbpostinstall | -idmdbruntime] [-idm_config IDMCONFIG] [-idmdiscargs IDMDISCARGS] [-idmhcargs IDMHCARGS | -h] ``` ## Syntax ``` $ exachk [options] ``` ``` [-h] [-a] [-b] [-v] [-p] [-m] [-u] [-f] [-o] [-clusternodes clusternames] [-failedchecks previous_result] [-nordbms] [-output path] [-dbnames dbnames] [-localonly] [-debug] [-dbnone | -dball] [-c] [-upgrade | -noupgrade] [-syslog] [-skip_usr_def_checks] [-checkfaileduploads] [-uploadfailed all | comma-delimited list of collections] [-fileattr start | check | remove [-includedir path [-excludediscovery] [-baseline path[-fileattronly] [-testemail all | "NOTIFICATION_EMAIL=comma-delimited list of email addresses"] [-setdbupload all | db upload variable, for example, RAT_UPLOAD_CONNECT_STRING, RAT_UPLOAD_PASSWORD] [-unsetdbupload all | db upload variable, for example, RAT_UPLOAD_CONNECT_STRING, RAT_UPLOAD_PASSWORD] [-checkdbupload] [-getdbupload] [-cmupgrade] [-sendemail "NOTIFICATION_EMAIL=comma-delimited list of email addresses"] [-nopass] [-noscore] [-showpass] [-show_critical] [-diff Old Report New Report [-outfile Output HTML] [-force]] [-merge report 1 report 2 [-force]] [-tag tagname] [-auto_restart -initsetup | -initdebugsetup | -initrmsetup | -initcheck | -h] [-d start|start -debug|stop|status|info|stop_client|nextautorun|-h] [-nodaemon] [-unlockcells all | -cells comma-delimited list of names or IPs of cells] [-lockcells all | -cells comma-delimited list of names or IPs of cells] [-usecompute] [-exadiff Exalogic collection1 Exalogic collection2] [-vmguest] [-hybrid [-phy nodes]] [-profile asm | bi_middleware | clusterware | compute_node | exatier1 | control_VM | corroborate | dba | ebs | el_extensive | el_lite | el_rackcompare | emagent | emoms | em | goldengate | hardware | maa | nimbula | obiee | ovn | peoplesoft | platinum | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | virtual_infra] [-excludeprofile asm | bi_middleware | clusterware | compute_node | exatier1 | control_VM | corroborate | dba | ebs | el_extensive | el_lite | el_rackcompare | emagent | emoms | em | goldengate | hardware | maa | nimbula | obiee | ovn | peoplesoft | platinum | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | virtual_infra] [-includeprofile asm | clusterware | corroborate | dba | ebs | emagent | emoms | em | goldengate | hardware | maa | oam | oim | oud | ovn | peoplesoft | preinstall | prepatch | security | siebel | solaris_cluster | storage | switch | sysadmin | timesten | user_defined_checks | zfs ] [-check check ids | -excludecheck check ids] [-cells cells] [-ibswitches switches] [-torswitches] [-extzfsnodes nodes] [-dbserial | -dbparallel [n] | -dbparallelmax | -allserial] [-allserial | -dbnodeserial |-cellserial | -switchserial] ``` # Running Unified AHF CLI Administration Commands Currently, the unified AHF CLI is supported only for Linux platforms. ## ahf The `ahf` command provides a unified CLI for generating diagnostic and AHF Balance reports, querying AHF software and MRP information, managing configuration and repositories, monitoring component status, and administering users and security. Its categories include `analysis`, `configuration`, `observer`, `software`, `data`, and `security`, with common options for help, version information, debugging, local-node scope, and JSON output. Supported operations include Insights and impact analysis, configuration updates, component status checks, software updates and rollbacks, repository management, data relocation, and user administration. Read More: [ahf](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf.html) ## ahf analysis The `ahf analysis` command generates AHF Insights, AHF Balance impact reports, and activity-specific Alert History reports. Insights supports bounded time-based analysis, refresh, tagging, and optional cell data; AHF Balance supports fleet, cluster, and database scopes, EM groups or cluster lists, output files, and limits on recommended database changes. Since AHF 25.11, Alert History consolidates component logs into activity timelines and supports ASM scenarios such as mount, dismount, forced dismount, and offline events, with filtering by instance, disk group, disk, severity, scenario, and time range limited to the previous 30 days. The deprecated exploratory Scope function should be replaced with Insights. Read More: [ahf analysis](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-analysis.html) ## ahf configuration The `ahf configuration` command sets, retrieves, validates, and removes AHF settings for repositories, uploads, cells, SMTP, updates, upgrades, resource limits, switches, GoldenGate, fleet insights, and AHF Balance. Recent capabilities include securely storing and checking switch and Exadata infrastructure details in the AHF wallet, automated propagation of excluded compliance-check IDs, and CLI management of update and upgrade parameters while legacy `ahfctl` commands transition to SDK CLI equivalents. Configuration supports interactive and property-based operations, JSON output, node-wide or targeted scope, repository connection details, upload endpoints, resource controls, and Exadata best-practice configuration. Read More: [ahf configuration](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-configuration.html) ## ahf observer The `ahf observer` command reports the status of AHF components through `ahf observer status`. It supports optional JSON output and identifies each component, host, and current state, such as whether Compliance is running or not running. Read More: [ahf observer](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-observer.html) ## ahf software The `ahf software` command provides AHF, TFA, and Compliance version details; queries installed MRP levels; compares Oracle homes with specified MRP levels to show installed and missing patches; identifies the latest applicable MRP; and manages update, upgrade, rollback, downgrade, backup deletion, and AHF Home relocation operations. It also exposes downgrade targets, validates downgrade installers, and retrieves update or upgrade histories. Several commands support JSON output, while software movement can optionally include the data directory. Read More: [ahf software](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-software.html) ## ahf data The `ahf data` command retrieves AHF repository information for TFA, Compliance, or all components, optionally restricted to the local installation and formatted as JSON. It can move the AHF Data directory to a specified destination and retrieve the latest Compliance reports by report type, including location, collection time, full-report status, and Compliance version. Read More: [ahf data](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-data.html) ## ahf security The `ahf security` command manages AHF users, roles, access states, credentials, and certificates. User operations include adding, removing, promoting, demoting, blocking, unblocking, listing, resetting, and granting or revoking roles. Credential operations securely store, retrieve, validate, and remove passwords and SSH keys for nodes, cells, databases, ASM, CDBs, and PDBs, with SSH keys protected in the AHF wallet and database credentials restricted from root users. AHF 26.8 adds customer CA-signed certificate support for root and non-root connections and certificate import, listing, updating, and removal for self-signed upload servers; certificates are distributed across cluster nodes and used for TLS validation. Read More: [ahf security](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-security.html) ## ahf schedule The `ahf schedule advise-time` command identifies a minimum-duration low-load window for running Exachk. It currently supports the Compliance component and can exclude specified busy periods using start and end times in `HH:MM` format. The required `--window` value defines the minimum available duration in minutes, enabling scheduling around production or maintenance activity. Read More: [ahf schedule](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/running-unified-ahf-cli-administration-commands/ahf-schedule.html) # OCLUMON Command Reference Use the command-line tool to query the Cluster Health Monitor repository to display node-specific metrics for a specific time period. Use OCLUMON to perform miscellaneous administrative tasks, such as changing the debug levels, querying the version of Cluster Health Monitor, and changing the metrics database size. ## oclumon analyze The `oclumon analyze` command analyzes Cluster Health Monitor (CHM) metrics and writes text or HTML reports to a specified output directory. It supports archived metric repositories, configurable logging, and optional start and end timestamps to limit the analysis period. Reports include system configuration and resource statistics, observed findings with a timeline, and detailed contextual information about detected problems. Read More: [oclumon analyze](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-analyze.html) ## oclumon dumpnodeview The `oclumon dumpnodeview` command displays system monitor data as node views for CPU, processes, aggregated processes, disks, network interfaces, filesystems, threads, Buddyinfo, NFS, and network protocols. It supports verbose and detailed output, filtering, sorting, row limits, sampling intervals, complete-sample selection, historical time ranges, duration-based queries, and reading metrics or logs from specified directories. Read More: [oclumon dumpnodeview](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-dumpnodeview.html) ## oclumon chmdiag The `oclumon chmdiag` command describes supported CHMDiag events and actions, queries event or action records, and collects diagnostic data for a selected time period or duration. Description and query reports can be generated in text or interactive HTML format, while queries and collections can be filtered by event IDs, action IDs, components, timestamps, or recent duration; collected data may also be compressed. Read More: [oclumon chmdiag](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-chmdiag.html) ## oclumon localrepo The `oclumon localrepo` command displays and changes local repository configuration across Cluster Health Monitor nodes. The `getconfig` operation reports repository size, path, and estimated retention time for all, local, or selected nodes, while `setconfig` changes the repository size in megabytes for all nodes. Read More: [oclumon localrepo](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-localrepo.html) ## oclumon version The `oclumon version` command displays the installed Cluster Health Monitor release and version information. Read More: [oclumon version](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-version.html) ## oclumon debug The `oclumon debug` command adjusts logging levels for supported Cluster Health Monitor daemons and modules or displays daemon versions. Logging levels range from 0, which provides minimal logging, to 3, which provides maximum logging; supported targets include `osysmond`, `client`, individual modules, and all components. Read More: [oclumon debug](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/oclumon-command-reference/oclumon-debug.html) # Querying Cluster Resource Activity Log Oracle Clusterware stores logs about resource state changes in the cluster resource activity log. Failures can occur as a result of a problem with a resource, a hosting node, or the network. The cluster resource activity log provides precise and specific information about a resource failure, separate from diagnostic logs. The cluster resource activity log also provides a unified view of the cause of resource failure. Use the following commands to view the contents of the cluster resource activity log. # CHACTL Command Reference The Oracle Cluster Health Advisor commands enable the Oracle Grid Infrastructure user to administer basic monitoring functionality on the targets. ## chactl monitor Starts Oracle Cluster Health Advisor monitoring for all instances of a specified RAC database or for the cluster, using the current, specified, or default Oracle-supplied model. The command stores monitoring status and automatically includes newly detected instances; use `-force` with `-model` to replace the active model without first unmonitoring the target. Common errors indicate that the CHA service is unavailable, the database is unconfigured, input is invalid, or the target is already monitored. Read More: [chactl monitor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-monitor.html) ## chactl unmonitor Stops Oracle Cluster Health Advisor monitoring for all instances of a specified database. The command requires the database unique name and reports when the database is not currently monitored. Read More: [chactl unmonitor](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-unmonitor.html) ## chactl status Displays Oracle Cluster Health Advisor monitoring status for all targets or for a specified cluster or database. Targets with positive status are shown by default, while explicitly specified targets may also show Not Monitoring; the `-verbose` option includes contained nodes or instances and their executing models, and the command can report when the CHA service is offline. Read More: [chactl status](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-status.html) ## chactl config Lists monitored targets and the model assigned to each target. For a specified database or cluster, it reports whether monitoring is enabled and identifies the configured model; multitenant container databases and clusters also expose configuration data status. Read More: [chactl config](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-config.html) ## chactl calibrate Creates and stores a target-specific Oracle Cluster Health Advisor model using selected calibration periods and optional KPI ranges, improving sensitivity and diagnostic accuracy for the operating environment. Database KPIs include CPU, disk reads and writes, throughput, and database time per call; cluster KPIs exclude database time per call. The `-force` option overwrites an existing model, while invalid time ranges, duplicate model names, or insufficient calibration data produce errors. Read More: [chactl calibrate](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-calibrate.html) ## chactl query diagnosis Reports abnormal problems, causes, incidents, and recommended corrective actions for monitored cluster nodes and databases, either for the current state or within a specified time range. Results are time-compressed and grouped by component; normal targets are omitted, recurring incidents are consolidated, and options can limit output to a database, cluster, interval, or HTML file. Messages distinguish normal operation, missing data, and targets that were inactive or unmonitored. Read More: [chactl query diagnosis](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-query-diagnosis.html) ## chactl query model Lists available Oracle Cluster Health Advisor models or displays metadata for a named model. Detailed output can include target type, version, operating system, calibration target and date, calibration ranges and KPIs, validation status, source data, and monitored targets. Read More: [chactl query model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-query-model.html) ## chactl query repository Displays Oracle Cluster Health Advisor repository capacity and usage information, including maximum and available retention time, entity counts, and allocated and total repository size. The command applies only when GIMR is configured. Read More: [chactl query repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-query-repository.html) ## chactl query calibration Displays calibration statistics for a specified database or cluster, optionally filtered by time ranges, KPI thresholds, and sampling interval. Output includes sample counts, filtered-data percentages, and descriptive statistics and distributions for supported CPU, I/O, throughput, and database-time metrics; without a time range, all collected calibration data for the target is shown. Read More: [chactl query calibration](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-query-calibration.html) ## chactl remove model Deletes a named Oracle Cluster Health Advisor model and its associated calibration data and metadata from the repository. A model cannot be removed while it is assigned to monitored targets, and the command reports an error if the specified model does not exist. Read More: [chactl remove model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-remove-model.html) ## chactl rename model Renames an Oracle Cluster Health Advisor model while preserving all links associated with it. The source name must exist and the destination name must be unique in the repository. Read More: [chactl rename model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-rename-model.html) ## chactl export model Exports a specified Oracle Cluster Health Advisor model to a file for external storage or transfer. The command requires the model name and output file path and is available only when GIMR is configured. Read More: [chactl export model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-export-model.html) ## chactl import model Imports an Oracle Cluster Health Advisor model from a file into the repository. If a model with the same name already exists, the `-force` option is required to overwrite it; the command applies only when GIMR is configured. Read More: [chactl import model](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-import-model.html) ## chactl set maxretention Sets the maximum retention period, in hours, for Oracle Cluster Health Advisor diagnostic data. The default and minimum retention is 72 hours, although storage constraints can reduce retention for all targets; monitoring stops if retention falls below 24 hours. Read More: [chactl set maxretention](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-set-maxretention.html) ## chactl resize repository Resizes the Oracle Cluster Health Advisor repository tablespace according to the current retention period and requested number of hosts and database instances. The operation can fail because of insufficient disk space or data exceeding the requested size, and it is available only when GIMR is configured. Read More: [chactl resize repository](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/chactl-command-reference/chactl-resize-repository.html) # Behavior Changes Deprecated and Desupported Features Learn about behavior changes and features, commands, and functionality that are deprecated or desupported in Oracle Autonomous Health Framework (AHF). ## Oracle E-Business Suite (EBS) Support is Deprecated in Release 18.3.0 Starting with release 18.3.0, Oracle Orachk and Oracle Exachk EBS checks are deprecated but remain supported until approximately release 19.3.0, when they will be desupported and removed. Use the EBS Analyzers available through My Oracle Support for all EBS health checks. Read More: [Oracle E-Business Suite Support is Deprecated in Release 1830](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/oracle_e-business_suite_support_is_deprecated_in_release_1830.md?ref_type=heads) ## Oracle Database Quality of Service (QoS) Management is Deprecated and Desupported in Release 19c Oracle Database Quality of Service Management is deprecated and desupported beginning with Oracle Database 19c because modern systems provide comparable resource-management capabilities and Autonomous Health Framework offers enhanced health recommendations and mitigation. Read More: [Oracle Database Quality of Service Management is Deprecated and Desupported in Oracle Database 19c](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/behavior-changes-deprecated-and-desupported-features/oracle-database-quality-of-service-management-is-deprecated-and-desupported-in-oracle-database-19c.html) ## Deprecated tfactl Upload Commands in Release 20.2 In release 20.2, wallet-based and user-based tfactl upload commands, along with MOS and database upload configuration commands, were deprecated. Oracle recommends using the newer generic upload mechanism for diagnostic data. Read More: [Deprecated tfactl Upload Commands In Release 202](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_tfactl_upload_commands_in_release_202.md?ref_type=heads) ## Deprecated SRDC in Release 20.2 The dbblockcorruption SRDC was deprecated in AHF release 20.2. Read More: [Deprecated SRDC In Release 202](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_srdc_in_release_202.md?ref_type=heads) ## Deprecated tfactl Commands in Release 21.1 Beginning with release 21.1, AHF functionality exposed through the tfactl command-line interface was deprecated and scheduled for removal in release 22.1. Users should use ahfctl instead for operations including patching, service control, upgrades, uploads, passwords, resource limits, and related administration. Read More: [Deprecated tfactl Commands In Release 211](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_tfactl_commands_in_release_211.md?ref_type=heads) ## Deprecated Oracle Orachk and Oracle Exachk Commands to Manage Patches in Release 21.1 Beginning with release 21.1, the Oracle Orachk and Oracle Exachk patch-management options applypatch, querypatch, and rollbackpatch were deprecated and scheduled for removal in release 22.1. Read More: [Deprecated Oracle Orachk and Oracle Exachk Commands to Manage Patches in Release 211](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_oracle_orachk_and_oracle_exachk_commands_to_manage_patches_in_release_211.md?ref_type=heads) ## Deprecated Oracle Trace File Analyzer Utilities in Release 21.1 The Oracle Trace File Analyzer summary and dbcheck utilities were deprecated in release 21.1 and planned for replacement by new command-line utilities with enhanced functionality. Read More: [Deprecated Oracle Trace File Analyzer Utilities in Release 211](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_oracle_trace_file_analyzer_utilities_in_release_211.md?ref_type=heads) ## Deprecated Oracle Trace File Analyzer Receiver in Release 21.1 Beginning with release 21.1, the Oracle Trace File Analyzer Receiver was deprecated and replaced by the enhanced Oracle Autonomous Health Framework Collections Manager. Read More: [Deprecated Oracle Trace File Analyzer Receiver in Release 211](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_oracle_trace_file_analyzer_receiver_in_release_211.md?ref_type=heads) ## Deprecated tfactl Commands in Release 22.1.0 In release 22.1.0, tfactl commands for starting, stopping, and checking AHF, sending mail, and displaying the repository were deprecated and removed. Their replacements are the corresponding ahfctl startahf, stopahf, statusahf, sendmail, and showrepo commands. Read More: [Deprecated tfactl Commands in Release 2210](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_tfactl_commands_in_release_2210.md?ref_type=heads) ## Deprecated Legacy Oracle Orachk and Oracle Exachk Scheduler Commands in 22.2 Starting with AHF 22.2, legacy Oracle Orachk and Oracle Exachk scheduler options and daemon commands were deprecated, with removal completed in AHF 23.8. Use the autostart, autostop, autostatus, and related replacement commands; obsolete commands may display guidance and invoke equivalents, while scheduler cleanup is supported during upgrades and through the new options. Read More: [Deprecated Legacy Oracle Orachk And Oracle Exachk Scheduler Commands In 222](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_legacy_oracle_orachk_and_oracle_exachk_scheduler_commands_in_222.md?ref_type=heads) ## Deprecated tfactl diagcollect Component in Release 22.3 The tfactl diagcollect dataguard component was deprecated in AHF 22.3. Oracle recommends collecting Data Guard diagnostics with the dbdataguard SRDC instead. Read More: [Deprecated tfactl diagcollect Component in Release 223](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_tfactl_diagcollect_component_in_release_223.md?ref_type=heads) ## Deprecated ahfctl Commands in Release 23.1.0 Starting with release 23.1.0, ahfctl applypatch, querypatch, and rollbackpatch were deprecated and removed. Use ahfctl applyupdate, queryupdate, and rollbackupdate as their replacements. Read More: [Deprecated ahfctl Commands in Release 2310](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_ahfctl_commands_in_release_2310.md?ref_type=heads) ## Deprecated AHF REST Services AHF REST services are deprecated and scheduled for desupport in AHF release 24.3.0. To start the services, download ORDS and provide the path to its ords.war file. Read More: [Deprecated AHF REST Services](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/behavior-changes-deprecated-and-desupported-features/deprecated-ahf-rest-services.html) ## Deprecated Oracle Trace File Analyzer Masking in Release 24.1 Beginning with AHF 24.1, the Oracle Trace File Analyzer masking feature was deprecated and may be desupported in a future release. Oracle recommends Adaptive Classification and Redaction for masking or sanitizing sensitive data in collections, enabled globally through tfactl configuration or per collection with the appropriate diagnostic-collection option. Read More: [Deprecated Oracle Trace File Analyzer Masking In Release 241](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_oracle_trace_file_analyzer_masking_in_release_241.md?ref_type=heads) ## Oracle Database Quality of Service (QoS) Management is Deprecated and Desupported in Release 21c Oracle Database Quality of Service Management is deprecated and desupported beginning with Oracle Database 21c because comparable resource-management capabilities are increasingly available in deployment platforms and Autonomous Health Framework provides enhanced health analysis and mitigation recommendations. Read More: [Oracle Database Quality of Service Management is Deprecated and Desupported in Oracle Database 21c](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/behavior-changes-deprecated-and-desupported-features/oracle-database-quality-of-service-management-is-deprecated-and-desupported-in-oracle-database-21c.html) ## Autonomous Heath Framework Scope (AHF Scope) Deprecated The Autonomous Health Framework Scope feature of Cluster Health Advisor is deprecated in Oracle AI Database 26ai as of April 2025. Oracle is discontinuing AHF Scope and recommends using Autonomous Health Framework Insights instead. Read More: [Autonomous Heath Framework Scope Deprecated](https://docs.oracle.com/en/engineered-systems/health-diagnostics/autonomous-health-framework/ahfug/behavior-changes-deprecated-and-desupported-features/autonomous-heath-framework-scope-deprecated.html) ## Deprecated and Desupported tfactl dbglevel command in Release 25.4.0 The tfactl dbglevel command, formerly used to set Oracle Grid Infrastructure trace levels, was deprecated and desupported in AHF release 25.4.0. Read More: [Deprecated and Desupported tfactl dbglevel command in Release 2540](https://orahub.oci.oraclecorp.com/db-ua-dev/text-editor-poc/-/tree/no-doc-repo/behavior_changes_deprecated_and_desupported_features/26.9/deprecated_and_desupported_tfactl_dbglevel_command_in_release_2540.md?ref_type=heads)