Use the tfactl set
command to adjust the manner in which TFA runs.
Syntax
tfactl set [autodiagcollect=ON | OFF | cookie=UID | trimfiles=ON | OFF | tracelevel=1 | 2 | 3 | 4 | reposizeMB=number | repositorydir=directory] [-c]
Parameters
Table J-14 tfactl set Command Parameters
Parameter | Description |
---|---|
autodiagcollect=ON | OFF |
When set to To set automatic collection for all nodes of the TFA cluster, you must specify the |
cookie=UID |
Use the |
trimfiles=ON | OFF |
When set to Note: When using |
tracelevel=1 | 2 | 3 | 4 |
Do not change the tracing level unless you are directed to do so by My Oracle Support. |
-c |
Specify this parameter to propagate these settings to all nodes in the TFA configuration. |
Automatic Diagnostic Collection
After TFA initially gathers trace file metadata, the daemon monitors all files that are determined to be alert logs using tail
, so that TFA can take action when certain strings occur.
By default, these logs are database alert logs, Oracle ASM alert logs, and Oracle Clusterware alert logs. When specific patterns occur in the logs saved to the Berkeley database, automatic diagnostic collection may take place.
Exactly what is collected depends on the pattern that is matched. TFA may just store information on the pattern matched or may initiate local diagnostic collection. Although TFA always monitors the logs and collects information into its database, automatic diagnostic collection only happens if it is enabled first using the tfactl set
command.