19 Managing and Configuring Oracle Trace File Analyzer
This section helps you manage Oracle Trace File Analyzer daemon, diagnostic collections, and the collection repository.
- Querying Oracle Trace File Analyzer Status and Configuration
Use theprint
command to query the status or configuration. - Managing the Oracle Trace File Analyzer Daemon
Oracle Trace File Analyzer runs frominit
on UNIX systems orinit/upstart/systemd
on Linux, or Microsoft Windows uses a Windows Service so that Oracle Trace File Analyzer starts automatically whenever a node starts. - Managing the Repository
Oracle Trace File Analyzer stores all diagnostic collections in the repository. - Managing Collections
Manage directories configured in Oracle Trace File Analyzer and diagnostic collections. - 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 certificates. - Configuring Email Notification Details
Configure Oracle Trace File Analyzer to send an email to the registered email address after an automatic collection completes.
19.1 Querying Oracle Trace File Analyzer Status and Configuration
Use the print
command to query the status or configuration.
Table 19-1 Configuration Listing and Descriptions
Configuration Listing | Default Value | Description |
---|---|---|
Automatic diagnostic collection |
ON |
Triggers a collection if a significant problem occurs. Possible values:
|
Trimming of files during diagnostic collection |
ON |
Trims the log files to only entries within the time range of the collection. Possible values:
|
Repository maximum size in MB |
Smaller of either 10GB or 50% of free space in the file system. |
The largest size the repository can be. |
Trace Level |
1 |
Increases the level of verbosity. Possible values:
A value of 1 results in the least amount of trace. A value of 4 results in the most amount of trace. Oracle recommends changing the trace level value only at the request of Oracle Support. |
Automatic Purging |
ON |
Purges collections when: Free space in the repository falls below 1GB. Or Before closing the repository. Purging removes collections from largest size through to smallest. Purging continues until the repository has enough space to open. |
Minimum Age of Collections to Purge (Hours) |
12 |
The least number of hours to keep a collection, after which it is eligible for purging. |
Minimum Space free to enable Alert Log Scan (MB) |
500 |
Suspends log scanning if free space in the |
Example 19-1 Print Configuration
$ tfactl print config
.------------------------------------------------------------------------.
| node1 |
+-----------------------------------------------------------+------------+
| Configuration Parameter | Value |
+-----------------------------------------------------------+------------+
| TFA Version |12.2.1.0.0 |
| Java Version | 1.8 |
| Public IP Network | true |
| Automatic Diagnostic Collection | true |
| Alert Log Scan | true |
| Disk Usage Monitor | true |
| Managelogs Auto Purge | false |
| Trimming of files during diagcollection | true |
| Inventory Trace level | 1 |
| Collection Trace level | 1 |
| Scan Trace level | 1 |
| Other Trace level | 1 |
| Repository current size (MB) | 447 |
| Repository maximum size (MB) | 10240 |
| Max Size of TFA Log (MB) | 50 |
| Max Number of TFA Logs | 10 |
| Max Size of Core File (MB) | 20 |
| Max Collection Size of Core Files (MB) | 200 |
| Minimum Free Space to enable Alert Log Scan (MB) | 500 |
| Time interval between consecutive Disk Usage Snapshot(minutes) | 60 |
| Time interval between consecutive Managelogs Auto Purge(minutes)| 60 |
| Logs older than the time period will be auto purged(days[d]|hours[h])|30d|
| Automatic Purging | true |
| Age of Purging Collections (Hours) | 12 |
| TFA IPS Pool Size | 5 |
'-----------------------------------------------------------+------------'
Related Topics
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.2 Managing the Oracle Trace File Analyzer Daemon
Oracle Trace File Analyzer runs from init
on UNIX systems or init/upstart/systemd
on Linux, or Microsoft Windows uses a Windows Service so that Oracle Trace File Analyzer starts automatically whenever a node starts.
To manage Oracle Trace File Analyzer daemon:
init
control file /etc/init.d/init.tfa
is platform dependant.
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.3 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.
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.3.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
Related Topics
Parent topic: Managing the Repository
19.3.2 Purging the Repository Manually
To purge the repository manually:
Related Topics
Parent topic: Managing the Repository
19.4 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 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.
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.4.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:
Related Topics
Parent topic: Managing Collections
19.4.2 Managing the Size of Collections
Use the Oracle Trace File Analyzer configuration options trimfiles
, maxcorefilesize
, maxcorecollectionsize
, and diagcollect
-nocores
to reduce the size of collections.
To manage the size of collections:
Related Topics
Parent topic: Managing Collections
19.5 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:
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.6 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.
To change the ports:
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.7 Configuring SSL and SSL Certificates
View and restrict SSL/TLS protocols. Configure Oracle Trace File Analyzer to use self-signed or CA-signed certificates.
- 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. - Configuring SSL Cipher Suite
The cipher suite is a set of cryptographic algorithms used by the TLS/SSL protocols to create keys and encrypt data.
Parent topic: Managing and Configuring Oracle Trace File Analyzer
19.7.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:
Parent topic: Configuring SSL and SSL Certificates
19.7.2 Configuring Self-Signed Certificates
Use Java keytool
to replace self-signed SSL certificates with personal self-signed certificates.
To configure Oracle Trace File Analyzer to use self-signed certificates:
Parent topic: Configuring SSL and SSL Certificates
19.7.3 Configuring CA-Signed Certificates
Use Java keytool
and openssl
to replace self-signed SSL certificates with the Certificate Authority (CA) signed certificates.
To configure Oracle Trace File Analyzer to use CA-signed certificates:
Parent topic: Configuring SSL and SSL Certificates
19.7.4 Configuring SSL Cipher Suite
The cipher suite is a set of cryptographic algorithms used by the TLS/SSL protocols to create keys and encrypt data.
Oracle Trace File Analyzer supports any of the cipher suites used by JRE 1.8.
The default cipher suite used is TLS_RSA_WITH_AES_128_CBC_SHA256
.
Parent topic: Configuring SSL and SSL Certificates
19.8 Configuring Email Notification Details
Configure Oracle Trace File Analyzer to send an email to the registered email address after an automatic collection completes.
To configure email notification details:
Example 19-2 tfactl set smtp
# /u01/app/11.2.0.4/grid/bin/tfactl set smtp
.---------------------------.
| SMTP Server Configuration |
+---------------+-----------+
| Parameter | Value |
+---------------+-----------+
| smtp.auth | false |
| smtp.from | tfa |
| smtp.user | - |
| smtp.cc | - |
| smtp.port | 25 |
| smtp.bcc | - |
| smtp.password | ******* |
| smtp.host | localhost |
| smtp.to | - |
| smtp.debug | true |
| smtp.ssl | true |
'---------------+-----------'
Enter the SMTP property you want to update : smtp.host
Enter value for smtp.host : myhost.domain.com
SMTP Property smtp.host updated with myhost.domain.com
Do you want to continue ? [Y]|N : N
#
Parent topic: Managing and Configuring Oracle Trace File Analyzer