Professional Documents
Culture Documents
Recently I posted about the upgrade of AHF/TAF from version 19 to 21 at Exadata and also for ODA. But with version 21 of AHF,
some collections are made automatically and this can impact your space usage. Here you can see how to check this and
disable/modify some of these.
The automatic collection for AHF/TFA is a feature that generates the diagnostic packages (to send to Oracle) when some specifics
errors appear in the database. The collected errors follow some patterns like ORA-0600, ORA-07445, and several others. The basic
idea can be seen in the official doc here and in the image below (retried directly from the official doc).
In my case, the automatic collection generates a problem with space usage. Look below the space consumption for AHF:
As you can see, more than 9GB for data collection at AHF. This occurred because one database error generated a lot of ORA-600,
and made AHF/TFA collect and generate traces for each one of these errors. This is designed for AHF/TFA, but unfortunately not
desired here in my case. As the documentation says: Automatic collections are ON by default (look in my server):
If you already collected a lot of diagnostics packages (like me) you can easily delete it directly from AHF/TFA with the “purge”
command (but remember to purge in each node of your cluster, there is no option to call just from one node and delete at all):
And to delete everything older than 5 hours here is the example (you can use the “-force” to avoid the “Y/N” question:
But is not just that we can do, there are several other things that we can check and enable/disable with commands “get” and “set”:
Other important commands are related to the print of current collections and configs. Look below that I collect the report+changed
the collection+generate the report again (and correctly show the change):
Another important change is related to CPU usage for AHF/TFA. At several places, we can see relates/doubts/posts/forums telling
about high CPU usage due to TFA. And if you link with the automatic collection you can pass several problems due to the limits. My
example:
As you can see above the CPU limit is 4. This means that TFA can use 4 CPUs of my servers to collect and generate data. This
value can be changed to a more reasonable value. The way to think is that 1 represents 100% of single CPU usage. 4, means
100% for 4 CPU usage. So, to set to 50% of only one cpu you define the value as 0.5 (example from the doc): ahfctl
setresourcelimit -value 0.5.
There are several other things to change and to set for AHF/TFA. The documentation is good and full of examples. Another good
source of information is the Markus Flechtner presentation from 2019.
Disclaimer: “The postings on this site are my own and don’t necessarily represent my actual employer positions, strategies or
opinions. The information here was edited to be useful for general purpose, specific data and identifications were removed to allow
reach the generic audience and to be useful for the community. Post protected by copyright.”