Oracle Autonomous Health Framework (AHF) works autonomously 24x7 to keep database systems healthy and running while minimizing human reaction time. Utilizing applied machine-learning technologies, AHF provides early warnings or automatically solves operational runtime issues faced by Database and System administrators in the areas of availability and performance.
It's the same technology Oracle uses in the cloud to keep the Autonomous Database running, and it's available for you at no extra cost as part of your existing software support agreement.
Insights in Diagnostic Collections
AHF now collects Insights data with diagnostic collections.
AHF Insights provides a bird's-eye view of the entire system. It helps spot problems, drill into the root cause and understand how to resolve.
AHF insights provides a view of:
- Configuration
- Environment topology
- Metric
- Logs
Data is viewable in reports covering:
- System Configuration
- System State
- Anomalies in Operating System
- Best Practice Compliance
- System Traces
- Root cause for issues and fixes in some anomalous cases
AHF diagnostic collection zips now include a sub-zip named <machine>_insights_<time>.zip containing the Insights report. This makes it quicker and easier to understand and resolve problems.
Insights for Single Instance Systems
AHF Insights are now available on single instance Linux systems.
AHF is on a mission to make it easier to maintain Oracle Databases.
Customers rely on AHF Insights to turn complex diagnostic data into simple actionable steps. However, until now it has only been available on Grid Infrastructure systems.
With AHF 24.2 Insights now adds support for single instance Linux systems, bringing this much-loved ease and simplicity to even more customers.
To generate an Insights report simply run:
ahf analysis create --type insights
Transfer the resulting zip to a system with browser support, extract it and open index.html.
Component Diagnostic Purging
AHF now supports component level diagnostic purging.
For many years, AHF has had automatic purging capability, which removes diagnostic collections and log files based on a purge policy.
However, there are some situations where diagnostics within one area grow faster than others, so it can be useful to be able to purge on a component-by-component basis for files that don’t meet the purge policy.
AHF has now extended the purge capability to enable cleaning at a component level, as well as to purge even if TFA is not running.
Available purge options can be seen with the command:
tfactl purge -h
Exadata Netdiag in Diagnostic Collections
AHF now captures Exadata netdiag output as part of the OS component in diagnostic collections.
Oracle Exadata systems have a tool called netdiag, which generates diagnostics for Nvidia/Mellanox. Output from netdiag is often required by Oracle Support to help resolve network specific issues.
AHF now collects Exadata netdiag output as part of the OS component of TFA collection. If the file modified date falls in the collection range, then the file will be included in the collection.
To ensure netdiag files are included within a collection use the command:
tfactl diagcollect -os -last 1h
Combine Diagnostics From All Machines in a Single Zip File
TFA diagcollect introduces the command option -singlearchive to combine zips from all nodes into a single diagnostic collection zip.
AHF has a long-standing ability to collect diagnostics from all Grid Infrastructure (GI) nodes using the tfactl diagcollect. This creates a series of zips, one for each node on the originating machine. However for customers with a large cluster, this can result in needing to provide many different zip files to Oracle Support.
AHF can now combine all files into a single zip archive on the initiating node by added the option -singlearchive.
For example:
tfactl diagcollect -last 1d -os -singlearchive
Source: oracle.com
Posts
0 comments:
Post a Comment