Troubleshooting 'TFA-00002 Oracle Trace File Analyzer (TFA) is not running'
(Doc ID 2883741.1)
Last updated on JULY 20, 2022
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
The purpose of this document to help diagnosing issue 'TFA-00002 Oracle Trace File Analyzer (TFA) is not running'.
Oracle Support strongly recommends using Trace File Analyzer (TFA) Collector for collecting data.
1. TFA Collector collects only relevant information based on the time of the event, so the size of collected data will be much smaller.
2. TFA Collector collects all CRS log files, ASM trace files, database trace files, OSWatcher output, and CHM (Cluster Health Monitor) output.
In case, if you have the latest TFA Collector already installed then upload TFA logs while creating/raising an SR, this will save considerable time for the entire triage process.
1) Doc ID 2550798.1 - Autonomous Health Framework (AHF) - Including TFA and ORAchk/EXAchk
2) Doc ID 2291661.1 - SRDC - Grid Infrastructure / Clusterware Administration and Management
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Case: Incorrect permission on tfactl causing TFA-00002|
|Case: '<Grid Home>/bin/tfactl print status' reports TFA-00002 but TFAMain process is running well|
|Case: On SuperCluster TFA-00002 is reported for a non-root user but TFAMain process is running well|