Gather diagnostic Information using TFA in Oracle Database

Oracle Trace File Analyzer (TFA) provides a number of diagnostic tools in a single bundle, making it easy to gather diagnostic information about the Oracle database and clusterware, which in turn helps with problem resolution when dealing with Oracle Support.

If possible we should install Oracle Trace File Analyzer as root. This will give you the highest capabilities. If Oracle Trace File Analyzer is already installed, reinstalling will perform an upgrade to the existing location. If it is not already installed, the recommended location is /opt/oracle.tfa

To install as root:

Download the appropriate Oracle Trace File Analyzer zip, copy to required machine and unzip.

Run the installTFA command: $ ./installTFA

To install as an ORACLE_HOME owner use the –extractto option. This tells Oracle Trace File Analyzer where to install to. The installer includes a JVM, but if you want to use one already installed use the –javahome option to point to it.

./installTFA -extractto -javahome

If we do not want to use ssh, we can install on each host using a local install. Then we use tfactl syncnodes to generate and deploy the relevant SSL certificates.

Now the time to collect TFA.

Please run TFA which collects all clusterware logs from all nodes (needs to be done as root from node1's gi_home): 

TFA from each node: 

==> TFA Collector- The Preferred Tool for Automatic or ADHOC Diagnostic Gathering Across All Cluster Nodes ( Doc ID 1513912.1 ) 

Examples: 

/bin/tfactl diagcollect -all -from "" -to "" 

/bin/tfactl diagcollect -all -since [2d|8h] 

/bin/tfactl diagcollect -for "" <--- 12hrs="" after="" and="" before="" collect="" font="" given="" nbsp="" the="" time="" will="">

bash-4.3# pwd
/orafs/app/11.2.0/grid/tfa/bin
bash-4.3# ./tfactl diagcollect -all -from "AUG/25/2019 14:30:00" -to "AUG/25/2019 16:30:00"
The -all switch is being deprecated as collection of all components is the default behavior. TFA will continue to collect all components.
Collecting data for all nodes
Scanning files from AUG/25/2019 14:30:00 to AUG/25/2019 16:30:00

Collection Id : 20190903104603sdbablv1

Detailed Logging at : /orafs/app/grid/tfa/repository/collection_Tue_Sep_03_16_46_04_GMT_2019_node_all/diagcollect_20190903104603_sdbablv1.log
2019/09/03 10:46:11 GMT : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
2019/09/03 10:46:11 GMT : Collection Name : tfa_Tue_Sep_03_16_46_04_GMT_2019.zip
2019/09/03 10:46:12 GMT : Collecting diagnostics from hosts : [sdbablv2, sdbablv1]
2019/09/03 10:46:13 GMT : Scanning of files for Collection in progress...
2019/09/03 10:46:13 GMT : Collecting additional diagnostic information...
2019/09/03 10:46:38 GMT : Getting list of files satisfying time range [08/25/2019 14:30:00 GMT, 08/25/2019 16:30:00 GMT]
2019/09/03 10:47:29 GMT : Completed collection of additional diagnostic information...
2019/09/03 10:48:19 GMT : Collecting ADR incident files...
2019/09/03 10:48:20 GMT : Completed Local Collection
2019/09/03 10:48:20 GMT : Remote Collection in Progress...
.-------------------------------------.
|          Collection Summary         |
+----------+-----------+-------+------+
| Host     | Status    | Size  | Time |
+----------+-----------+-------+------+
| sdbablv2 | Completed | 1.8MB |  80s |
| sdbablv1 | Completed | 3.5MB | 128s |
'----------+-----------+-------+------'

Logs are being collected to: /orafs/app/grid/tfa/repository/collection_Tue_Sep_03_16_46_04_GMT_2019_node_all
/orafs/app/grid/tfa/repository/collection_Tue_Sep_03_16_46_04_GMT_2019_node_all/sdbablv1.tfa_Tue_Sep_03_16_46_04_GMT_2019.zip
/orafs/app/grid/tfa/repository/collection_Tue_Sep_03_16_46_04_GMT_2019_node_all/sdbablv2.tfa_Tue_Sep_03_16_46_04_GMT_2019.zip