4.3 Automatically Collecting Diagnostic Data Using the Oracle Trace File Analyzer Collector
Manage Oracle Trace File Analyzer Collector daemon, diagnostic collections, and the collection repository.
In addition, add hosts to the Oracle Trace File Analyzer Collector configuration, modify default communication ports, and configure SSL protocol.
Topics:
- Managing the Oracle Trace File Analyzer Daemon
Oracle Trace File Analyzer Collector runs out ofinit
on UNIX systems orinit/upstart/systemd
on Linux systems so that Oracle Trace File Analyzer Collector starts automatically whenever a node starts. - Viewing the Status and Configuration of Oracle Trace File Analyzer
View the status of Oracle Trace File Analyzer across all the nodes in the cluster using eithertfactl print status
ortfactl print config
commands. - Configuring the Host
You must haveroot
orsudo
access totfactl
to add hosts to Oracle Trace File Analyzer configuration. - Configuring the Ports
The Oracle Trace File Analyzer daemons in a cluster communicate securely over ports 5000 to 5005. - Configuring SSL and SSL Certificates
View and restrict SSL/TLS protocols. Configure Oracle Trace File Analyzer to use self-signed or CA-signed certificate. - Managing Collections
Manage directories configured in Oracle Trace File Analyzer and diagnostic collections. - Managing the Repository
Oracle Trace File Analyzer stores all diagnostic collections in the repository.
4.3.1 Managing the Oracle Trace File Analyzer Daemon
Oracle Trace File Analyzer Collector runs out of init
on UNIX systems or init/upstart/systemd
on Linux systems so that Oracle Trace File Analyzer Collector starts automatically whenever a node starts.
To manage Oracle Trace File Analyzer daemon:
init
control file /etc/init.d/init.tfa
is platform dependant.
4.3.2 Viewing the Status and Configuration of Oracle Trace File Analyzer
View the status of Oracle Trace File Analyzer across all the nodes in the cluster using either tfactl print status
or tfactl print config
commands.
To view the status and configuration settings of Oracle Trace File Analyzer:
Related Topics
4.3.3 Configuring the Host
You must have root
or sudo
access to tfactl
to add hosts to Oracle Trace File Analyzer configuration.
To add, remove, and replace SSL certificates:
4.3.4 Configuring the Ports
The Oracle Trace File Analyzer daemons in a cluster communicate securely over ports 5000 to 5005.
If the port range is not available on your system, then replace it with the ports available on your system.
The $TFA_HOME/internal/usableports.txt
file looks as follows:
$ cat $TFA_HOME/internal/usableports.txt
5000
5001
5002
5003
5004
5005
To change the ports:
4.3.5 Configuring SSL and SSL Certificates
View and restrict SSL/TLS protocols. Configure Oracle Trace File Analyzer to use self-signed or CA-signed certificate.
Topics:
- Configuring SSL/TLS Protocols
The Oracle Trace File Analyzer daemons in a cluster communicate securely using the SSL/TLS protocols. - Configuring Self-Signed Certificates
UseJava keytool
to replace self-signed SSL certificates with personal self-signed certificates. - Configuring CA-Signed Certificates
UseJava keytool
andopenssl
to replace self-signed SSL certificates with the Certificate Authority (CA) signed certificates.
4.3.5.1 Configuring SSL/TLS Protocols
The Oracle Trace File Analyzer daemons in a cluster communicate securely using the SSL/TLS protocols.
The SSL protocols available for use by Oracle Trace File Analyzer are:
-
TLSv1.2
-
TLCv1.1
-
TLSv1
Oracle Trace File Analyzer always restricts use of older the protocols SSLv3
and SSLv2Hello
.
To view and restrict protocols:
4.3.6 Managing Collections
Manage directories configured in Oracle Trace File Analyzer and diagnostic collections.
Topics:
- Including Directories
Add directories to the Oracle Trace File Analyzer configuration to include the directories in diagnostic collections. - Managing the Size of Collections
Use the Oracle Trace File Analyzer configuration optionstrimfiles
,maxcorefilesize
,maxcorecollectionsize
, anddiagcollect
-nocores
to reduce the size of collections.
4.3.6.1 Including Directories
Add directories to the Oracle Trace File Analyzer configuration to include the directories in diagnostic collections.
Oracle Trace File Analyzer then stores diagnostic collection metadata about the:
-
Directory
-
Subdirectories
-
Files in the directory and all sub directories
All Oracle Trace File Analyzer users can add directories they have read access to.
To manage directories:
4.3.7 Managing the Repository
Oracle Trace File Analyzer stores all diagnostic collections in the repository.
The repository size is the maximum space Oracle Trace File Analyzer is able to use on disk to store collections.
4.3.7.1 Purging the Repository Automatically
Oracle Trace File Analyzer closes the repository, if:
-
Free space in
TFA_HOME
is less than 100 MB, also stops indexing -
Free space in
ORACLE_BASE
is less than 100 MB, also stops indexing -
Free space in the repository is less than 1 GB
-
Current size of the repository is greater than the repository max size (
reposizeMB
)
The Oracle Trace File Analyzer daemon monitors and automatically purges the repository when the free space falls below 1 GB or before closing the repository. Purging removes collections from largest size through to smallest until the repository has enough space to open.
Oracle Trace File Analyzer automatically purges only the collections that are older than minagetopurge
. By default, minagetopurge
is 12 hours.
To purge the repository automatically