Skip navigation

We haven't updated you on the Autonomous Health Framework in a few months.  AHF is a bundle of TFA, ORAchk and EXAchk.  Just this past week, the newest release was made available for download here: TFA, ORAchk & EXAchk 20.2

 

What are the new features in this release:

 

Resource savings through fewer repeat collections

Each event which TFA automatically generates a collection for now has a flood control limit defined.

The flood control limit instructs TFA to only collect a certain amount of times for the same event and then pause collection for that event for a set duration.

Flood control avoids unnecessary repeat collections for similar events and helps conserve system resources and can be managed via tfactl floodcontrol.

Confidence that TFA won't use too much CPU

On Linux the CPU usage of TFA can be limited with the command tfactl setresourcelimit [-value value]

For example to limit TFA to a maximum of 50% of a single CPU use: tfactl setresourcelimit -value 0.5

CPU resource limits for TFA can be set between a minimum of 0.5 and maximum of 4 or 75% of available CPUs, whichever is lower. By default the TFA CPU limit is set to the maximum.

 

Easier to upload diagnostic collections

The command tfactl setupload -name config_name -type config_type can be used to configure where diagnostic collections from TFA, ORAchk and EXAchk are automatically uploaded. Collection configurations can also be used on-demand via tfactl upload. Multiple upload configurations can be stored by giving them unique names.

For example to configure ORAchk uploads to be stored in a database you can use: tfactl setupload -name mysqlnetconfig -type sqlnet TFA will then prompt you for the required values.

Along with setupload, you can also use:

  • tfactl getupload -name config_name to retrieve all values
  • tfactl checkupload -name config_name to check if the values can be used to make a connection to the resource
  • tfactl unsetupload -name config_name [-parameter parameter | -all] to unset one or all the values for the configuration

Latest most secure python stack

  style="margin:0.5em"

  • Ensure that the non-root user has been promoted by querying using tfactl access lsusers and verify promoted is true.

Once the non-root user has been promoted, non-root user can run Oracle ORAchk with the -runasroot option to run root privileged checks.

Welcome to the My Oracle Support Community! We highly encourage you to personalize your community display name to make your activity more memorable. Please see https://community.oracle.com/docs/DOC-1022508 for instructions.