Oracle Trace File Analyzer is automatically configured as part of the Oracle Grid Infrastructure configuration when running
tfadirectories are created when Oracle Trace File Analyzer is installed as part of the Oracle Grid Infrastructure.
Grid_home/tfa: This directory contains the Oracle Trace File Analyzer executables and some configuration files.
ORACLE_BASE is the Oracle Grid Infrastructure owner’s
ORACLE_BASE. This directory contains the Oracle Trace File Analyzer metadata files and logs.
ORACLE_BASE can be on a shared file system because Oracle Trace File Analyzer creates a node-specific directory under the
Oracle Trace File Analyzer uses the JRE version 1.8, which is shipped as part of the Oracle Grid Infrastructure 12.2 or Oracle Database 12.2 Home.
By default, Oracle Trace File Analyzer is configured to start automatically. The automatic start implementation is platform-dependent.
Linux systems: Automatic restart is accomplished by using,
init replacement such as
Automatic restart is implemented as a Windows service.
Oracle Trace File Analyzer is not managed as one of the Cluster Ready Services (CRS) because it must be available if CRS is down.
$ /u01/app/12.2.0/grid/tfa/bin/tfactl start Starting TFA.. start: Job is already running: oracle-tfa Waiting up to 100 seconds for TFA to be started.. . . . . . Successfully started TFA Process.. . . . . . TFA Started and listening for commands
$ /u01/app/12.2.0/grid/tfa/bin/tfactl stop Stopping TFA from the Command Line Stopped OSWatcher TFA is running - Will wait 5 seconds (up to 3 times) TFA-00518 Oracle Trace File Analyzer (TFA) is not running (stopped) TFA Stopped Successfully . . . Successfully stopped TFA..
In the preceding example output, "Stopped OSWatcher" is seen only if you are using the download from My Oracle Support. Since
OSWatcher is included only in the download and not in the Oracle Grid Infrastructure or Oracle Database install.