Managing Collections

Manage directories configured in Oracle Trace File Analyzer and diagnostic collections.

Including Directories

Add directories to the Oracle Trace File Analyzer configuration to include their diagnostic data in collections.

For each configured directory, Oracle Trace File Analyzer stores diagnostic collection metadata about:

• The directory
• Its subdirectories
• Files in the directory and its subdirectories

Oracle Trace File Analyzer users can add directories for which they have read access.

To manage directories:

1. View the directories currently configured in Oracle Trace File Analyzer:

   tfactl print directories [-node all|local|<n1,n2,...>] [-comp <component_name1,component_name2,...>] [-policy exclusions|noexclusions] [-permission public|private]

2. Add a directory:

   tfactl directory add <dir> [-public] [-exclusions|-noexclusions|-collectall] [-node all|<n1,n2,...>]

3. Remove a directory from diagnostic collection:

   tfactl directory remove <dir> [-node all|<n1,n2,...>]

Managing the Size of Collections

Use the Oracle Trace File Analyzer configuration options trimfiles, maxcorefilesize, and maxcorecollectionsize, and the tfactl diagcollect -cores option to control the size of diagnostic collections and the inclusion of core files.

To manage collection size:

1. Configure whether Oracle Trace File Analyzer trims files during diagnostic collection:

   tfactl set trimfiles=ON|OFF

   • ON - Oracle Trace File Analyzer trims files to include data around the time of the event. This is the default.
   • OFF - Oracle Trace File Analyzer collects the entire file if the file was written to at the time of the event.
2. Set the maximum size, in MB, of an individual core file that can be collected:

   tfactl set maxcorefilesize=<n>

   The default value is 50 MB.

   Oracle Trace File Analyzer skips core files larger than the configured maxcorefilesize.

3. Set the maximum total size, in MB, of core files that can be included in a collection:

   tfactl set maxcorecollectionsize=<n>

   The default value is 500 MB.

   Oracle Trace File Analyzer stops collecting additional core files after the total size reaches maxcorecollectionsize.

4. Include core files in a diagnostic collection:

   tfactl diagcollect -cores

Temporarily Restricting Automatic Diagnostic Collections for Specific Events

Use the tfactl blackout command to temporarily suppress automatic diagnostic collections for specific targets or events.

When a blackout is configured for a target, Oracle Trace File Analyzer does not initiate an automatic diagnostic collection when it detects a matching event in the target's alert logs.

You can configure a blackout at different levels of granularity. For example, you can suppress collections for all events associated with a database, for a specific event such as ORA-00600, or for an ORA-00600 event with specific arguments.

For example, to suppress automatic collections for ORA-00600 events for the database mydb:

tfactl blackout add -targettype database -target mydb -event "ORA-00600"

Example output:

Event "ORA-00600" is blacked out until Wed Feb 20 00:20:34 PST 2019 on targettype : database, target : mydb

You can also configure a blackout for a resource that does not yet exist. This can be useful during provisioning when you do not want Oracle Trace File Analyzer to initiate automatic diagnostic collections until the resource is ready.

For example, when provisioning a new database:

1. Configure a blackout for the database that you plan to create.
2. Create and provision the database.
3. Remove the blackout after provisioning is complete.