Use the tfactl dbglevel command to set Oracle Grid Infrastructure trace levels.

tfactl [run] dbglevel 
[ {-set|-unset} profile_name 
-dependency [dep1,dep2,...|all] 
-dependency_type [type1,type2,type3,...|all] 
| {-view|-drop} profile_name 
| -lsprofiles 
| -lsmodules 
| -lscomponents [module_name] 
| -lsres 
| -create profile_name [ -desc description 
| [-includeunset] [-includetrace] 
| -debugstate | -timeout time ] 
| -modify profile_name [-includeunset] [-includetrace] 
| -getstate [ -module module_name ] 
| -active [profile_name] 
| -describe [profile_name] ] ]

Oracle Trace File Analyzer trims and collects any important logs updated in the past one hour.

If you know that you only want logs for a smaller window, then you can cut this collection period. Cutting the collection period helps you make collections as small and quick as possible.

There are four different ways you can specify the period for collection:

Perform default diagnostic collection or choose an event from the list of recent incidents to collect diagnostic data for that event alone.

1. To run a default diagnostic collection:

   tfactl diagcollect

   For example:

   $ tfactl diagcollect
   Choose the event you want to perform a diagnostic collection for:
   1. Mar/12/2019 16:08:20 [ db.orcl.orcl ]  ORA-04030: out of process memory when trying to allocate
   2. Mar/12/2019 16:08:18 [ db.orcl.orcl ]  ORA-04031: unable to allocate 8 bytes of shared memory
   3. Mar/12/2019 16:08:16 [ db.orcl.orcl ]  ORA-00494: enqueue held for too long more than seconds by osid
   4. Mar/12/2019 16:08:14 [ db.orcl.orcl ]  ORA-29709: Communication failure with Cluster Synchronization
   5. Mar/12/2019 16:08:04 [ db.orcl.orcl ]  ORA-29702: error occurred in Cluster Group Service operation
   6. Mar/12/2019 16:07:59 [ db.orcl.orcl ]  ORA-32701: Possible hangs up to hang ID= detected
   7. Mar/12/2019 16:07:51 [ db.orcl.orcl ]  ORA-07445: exception encountered: core dump [] [] [] [] [] []
   8. Mar/12/2019 16:07:49 [ db.orcl.orcl ]  ORA-00700: soft internal error, arguments: [700], [], [],[]
   9. Mar/11/2019 22:02:19 [ db.oradb.oradb ]  DIA0 Critical Database Process Blocked: Hang ID 1 blocks 5 sessions
   10. Default diagnostic collection, for no specific event
   
   Please choose the event : 1-10 [] 10
   
   By default TFA will collect diagnostics for the last 12 hours. This can result in large collections
   For more targeted collections enter the time of the incident, otherwise hit <RETURN> to collect for the last 12 hours
   [YYYY-MM-DD HH24:MI:SS,<RETURN>=Collect for last 12 hours] :
   
   Collecting data for the last 12 hours for all components...
   Collecting data for all nodes
   
   Collection Id : 20190312163846node1
   
   Detailed Logging at : /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_38_47_PDT_2019_node_all/diagcollect_20190312163846_node1.log
   2019/03/12 16:38:50 PDT : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
   2019/03/12 16:38:50 PDT : Collection Name : tfa_Tue_Mar_12_16_38_47_PDT_2019.zip
   2019/03/12 16:38:50 PDT : Collecting diagnostics from hosts : [node1]
   2019/03/12 16:38:50 PDT : Scanning of files for Collection in progress...
   2019/03/12 16:38:50 PDT : Collecting additional diagnostic information...
   2019/03/12 16:38:55 PDT : Getting list of files satisfying time range [03/12/2019 04:38:50 PDT, 03/12/2019 16:38:55 PDT]
   2019/03/12 16:39:02 PDT : Collecting ADR incident files...
   2019/03/12 16:39:06 PDT : Completed collection of additional diagnostic information...
   2019/03/12 16:39:07 PDT : Completed Local Collection
   .------------------------------------.
   |         Collection Summary         |
   +----------+-----------+------+------+
   | Host     | Status    | Size | Time |
   +----------+-----------+------+------+
   | node1 | Completed | 21MB |  17s |  |    
   '----------+-----------+------+------'
   
   Logs are being collected to: /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_38_47_PDT_2019_node_all
   /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_38_47_PDT_2019_node_all/node1.tfa_Tue_Mar_12_16_38_47_PDT_2019.zip

   $ tfactl diagcollect
   Choose the event you want to perform a diagnostic collection for:
   1. Mar/12/2019 16:08:20 [ db.orcl.orcl ]  ORA-04030: out of process memory when trying to allocate
   2. Mar/12/2019 16:08:18 [ db.orcl.orcl ]  ORA-04031: unable to allocate 8 bytes of shared memory
   3. Mar/12/2019 16:08:16 [ db.orcl.orcl ]  ORA-00494: enqueue held for too long more than seconds by osid
   4. Mar/12/2019 16:08:14 [ db.orcl.orcl ]  ORA-29709: Communication failure with Cluster Synchronization
   5. Mar/12/2019 16:08:04 [ db.orcl.orcl ]  ORA-29702: error occurred in Cluster Group Service operation
   6. Mar/12/2019 16:07:59 [ db.orcl.orcl ]  ORA-32701: Possible hangs up to hang ID= detected
   7. Mar/12/2019 16:07:51 [ db.orcl.orcl ]  ORA-07445: exception encountered: core dump [] [] [] [] [] []
   8. Mar/12/2019 16:07:49 [ db.orcl.orcl ]  ORA-00700: soft internal error, arguments: [700], [], [],[]
   9. Mar/11/2019 22:02:19 [ db.oradb.oradb ]  DIA0 Critical Database Process Blocked: Hang ID 1 blocks 5 sessions
   10. Default diagnostic collection, for no specific event
   
   Please choose the event : 1-10 [] 1
   User root does not have permissions to run SRDC 'ora4030' for database 'orcl'.

2. To run a diagnostic collection for a specific event that does not have an SRDC:

   tfactl diagcollect

   For example:

   $ tfactl diagcollect
   Choose the event you want to perform a diagnostic collection for:
   1. Mar/12/2019 16:08:20 [ db.orcl.orcl ]  ORA-04030: out of process memory when trying to allocate
   2. Mar/12/2019 16:08:18 [ db.orcl.orcl ]  ORA-04031: unable to allocate 8 bytes of shared memory
   3. Mar/12/2019 16:08:16 [ db.orcl.orcl ]  ORA-00494: enqueue held for too long more than seconds by osid
   4. Mar/12/2019 16:08:14 [ db.orcl.orcl ]  ORA-29709: Communication failure with Cluster Synchronization
   5. Mar/12/2019 16:08:04 [ db.orcl.orcl ]  ORA-29702: error occurred in Cluster Group Service operation
   6. Mar/12/2019 16:07:59 [ db.orcl.orcl ]  ORA-32701: Possible hangs up to hang ID= detected
   7. Mar/12/2019 16:07:51 [ db.orcl.orcl ]  ORA-07445: exception encountered: core dump [] [] [] [] [] []
   8. Mar/12/2019 16:07:49 [ db.orcl.orcl ]  ORA-00700: soft internal error, arguments: [700], [], [],[]
   9. Mar/11/2019 22:02:19 [ db.oradb.oradb ]  DIA0 Critical Database Process Blocked: Hang ID 1 blocks 5 sessions
   10. Default diagnostic collection, for no specific event
   
   Please choose the event : 1-10 [] 9
   Collecting data for all nodes
   Scanning files from mar/11/2019 18:02:19 to mar/11/2019 23:02:19
   
   Collection Id : 20190312162708node1
   
   Detailed Logging at : /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all/diagcollect_20190312162708_node1.log
   2019/03/12 16:27:12 PDT : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
   2019/03/12 16:27:12 PDT : Collection Name : tfa_Tue_Mar_12_16_27_09_PDT_2019.zip
   2019/03/12 16:27:12 PDT : Collecting diagnostics from hosts : [node1]
   2019/03/12 16:27:12 PDT : Scanning of files for Collection in progress...
   2019/03/12 16:27:12 PDT : Collecting additional diagnostic information...
   2019/03/12 16:27:17 PDT : Getting list of files satisfying time range [03/11/2019 18:02:19 PDT, 03/11/2019 23:02:19 PDT]
   2019/03/12 16:27:23 PDT : Collecting ADR incident files...
   2019/03/12 16:27:28 PDT : Completed collection of additional diagnostic information...
   2019/03/12 16:27:33 PDT : Completed Local Collection
   .------------------------------------.
   |         Collection Summary         |
   +----------+-----------+------+------+
   | Host     | Status    | Size | Time |
   +----------+-----------+------+------+
   | node1 | Completed | 10MB |  21s |
   '----------+-----------+------+------'
   
   Logs are being collected to: /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all
   /scratch/app/product/19c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all/node1.tfa_Tue_Mar_12_16_27_09_PDT_2019.zip

3. To run a diagnostic collection for a specific event that has an SRDC:

   Note:

   When choosing an SRDC the user running the collection needs to be in the dba group of the database chosen in the event.

   tfactl diagcollect

   For example:

   $ tfactl diagcollect
   Choose the event you want to perform a diagnostic collection for:
   1. Mar/12/2019 16:08:20 [ db.orcl.orcl ]  ORA-04030: out of process memory when trying to allocate
   2. Mar/12/2019 16:08:18 [ db.orcl.orcl ]  ORA-04031: unable to allocate 8 bytes of shared memory
   3. Mar/12/2019 16:08:16 [ db.orcl.orcl ]  ORA-00494: enqueue held for too long more than seconds by osid
   4. Mar/12/2019 16:08:14 [ db.orcl.orcl ]  ORA-29709: Communication failure with Cluster Synchronization
   5. Mar/12/2019 16:08:04 [ db.orcl.orcl ]  ORA-29702: error occurred in Cluster Group Service operation
   6. Mar/12/2019 16:07:59 [ db.orcl.orcl ]  ORA-32701: Possible hangs up to hang ID= detected
   7. Mar/12/2019 16:07:51 [ db.orcl.orcl ]  ORA-07445: exception encountered: core dump [] [] [] [] [] []
   8. Mar/12/2019 16:07:49 [ db.orcl.orcl ]  ORA-00700: soft internal error, arguments: [700], [], [],[]
   9. Mar/11/2019 22:02:19 [ db.oradb.oradb ]  DIA0 Critical Database Process Blocked: Hang ID 1 blocks 5 sessions
   10. Default diagnostic collection, for no specific event
   
   Please choose the event : 1-10 [] 1
   Scripts to be run by this srdc: srdc_db_sid_memorysizes_10glower.sql srdc_db_sid_memorysizes_11gplus.sql ipspack 
   Components included in this srdc: OS DATABASE CHMOS
   Collecting data for local node(s)
   Scanning files from Mar/12/2019 14:08:20 to Mar/12/2019 18:08:20
   WARNING: End time entered is after the current system time.
   
   Collection Id : 20190312163524node1
   
   Detailed Logging at : /scratch/app/product/19c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local/diagcollect_20190312163524_node1.log
   2019/03/12 16:35:30 PDT : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
   2019/03/12 16:35:30 PDT : Collection Name : tfa_srdc_ora4030_Tue_Mar_12_16_35_25_PDT_2019.zip
   2019/03/12 16:35:30 PDT : Scanning of files for Collection in progress...
   2019/03/12 16:35:30 PDT : Collecting additional diagnostic information...
   2019/03/12 16:35:35 PDT : Getting list of files satisfying time range [03/12/2019 14:08:20 PDT, 03/12/2019 16:35:30 PDT]
   2019/03/12 16:35:49 PDT : Collecting ADR incident files...
   2019/03/12 16:35:52 PDT : Completed collection of additional diagnostic information...
   2019/03/12 16:35:54 PDT : Completed Local Collection
   .-------------------------------------.
   |          Collection Summary         |
   +----------+-----------+-------+------+
   | Host     | Status    | Size  | Time |
   +----------+-----------+-------+------+
   | node1 | Completed | 2.9MB |  24s |
   '----------+-----------+-------+------'
   
   Logs are being collected to: /scratch/app/product/19c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local
   /scratch/app/product/19c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local/node1.tfa_srdc_ora4030_Tue_Mar_12_16_35_25_PDT_2019.zip

Prevent excessively large files from delaying or stalling collections.

1. To set the maximum file size:

   tfactl set maxfilecollectionsize=size_in_MB

2. To collect diagnostic data:

   tfactl diagcollect

1. To collect from specific nodes:

   tfactl diagcollect –node list of nodes

   For example:

   $ tfactl diagcollect -last 1d -node myserver65

1. To collect from specific components:

   tfactl diagcollect component

   For example:

   To trim and collect all files from the databases hrdb and fdb in the last 1 day:

   tfactl –diagcollect -database hrdb,fdb -last 1d

   To trim and collect all Oracle Clusterware files, operating system logs, and CHMOS/OSW data from node1 and node2 updated in the last 6 hours:

   tfactl diagcollect -crs -os -node node1,node2 -last 6h

   To trim and collect all Oracle ASM logs from node1 updated between from and to time:

   tfactl diagcollect -asm -node node1 -from "2016-08-15" -to "2016-08-17"

   Following are the available component options.

   Table 4-12 Component Options

   Component Option	Description
   -cha	Collects Oracle Cluster Health Advisor logs.
   -ips	Collects Incident Packaging Service logs.
   -database database_names	Collects database logs from databases specified in a comma-separated list.
   -asm	Collects Oracle ASM logs.
   -crsclient	Collects Client Logs that are under GIBASE/diag/clients.
   -dbclient	Collects Client Logs that are under DB ORABASE/diag/clients.
   -dbwlm	Collects Database Workload Management (DBWLM) logs.
   -tns	Collects TNS logs.
   -rhp	Collects Rapid Home Provisioning (RHP) logs.
   -procinfo	Collects Gathers stack and fd from /proc for all processes.
   -afd	Collects AFD logs.
   -crs	Collects Oracle Clusterware logs.
   -wls	Collects Oracle WebLogic Server (WLS) logs.
   -emagent	Collects Oracle Enterprise Manager Agent (EMAGENT) logs.
   -oms	Collects Oracle Management Service (OMS) logs.
   -ocm	Collects Oracle Configuration Manager (OCM) logs.
   -emplugins	Collects Oracle Enterprise Manager Plug-ins (EMPLUGINS) logs.
   -em	Collects Oracle Enterprise Manager (EM) logs.
   -acfs	Oracle Advanced Cluster File System (Oracle ACFS).
   -install	Collects Oracle Installation related files.
   -cfgtools	Collects configuration tools logs.
   -os	Collects operating system files such as /var/log/messages and /var/log/exadatatmp/*netdiag* files only on Exadata systems.
   -ashhtml	Collects Generate Active Session History (ASH) HTML report.
   -ashtext	Collects Generate Active Session History (ASH) text report.
   -awrhtml	Collects Automatic Workload Repository (AWR) HTML logs.
   -awrtext	Collects Automatic Workload Repository (AWR) text report.
   -avs	Collects Audit Vault Server logs.

1. To include all files updated in the last one hour:

   tfactl diagcollect –collectdir dir1,dir2,...dirn

   For example:

   To trim and collect all Oracle Clusterware files updated in the last one hour as well as all files from /tmp_dir1 and /tmp_dir2 at the initiating node:

   $ tfactl diagcollect –crs –collectdir /tmp_dir1,/tmpdir_2

2. To configure Oracle Trace File Analyzer to collect all files from a directory, first configure it with the -collectall option:

   $ tfactl add dir -collectall

   or

   tfactl modify dir -collectall

   Start a diagnostic collection using the -collectalldirs option:

   $ tfactl diagcollect -collectalldirs

   Note:

   If the -collectalldirs option is not used normal, then the file type, name, and time range restrictions are applied.

repository/collection_date_time/node_all/node.tfa_date_time.zip

1. To use your own naming to organize collections:

   –tag tagname

   The files are collected into tagname directory inside the repository.

2. To rename the zip file:

   –z zip name

1. To prevent copying the zip file back to the initiating node:

   –nocopy

   For example:

   $ tfactl diagcollect -last 1d -nocopy

2. To avoid trimming files:

   –notrim

   For example:

   $ tfactl diagcollect -last 1d -notrim

1. To initiate a silent collection:

   –silent

   The diagcollect command is submitted as a background process.

   For example:

   $ tfactl diagcollect -last 1d -silent

1. To collect core files:

   –cores

   For example:

   $ tfactl diagcollect -last 1d -cores

Incident Packaging Service packages details of problems stored by Oracle Database in ADR for later diagnosis.

tfactl ips option