TFA 19.2 updates and features

1. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Oracle Trace File Analyzer (TFA)
With Database Support Tools Bundle
What’s New in 19.2

2. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Temporarily restrict automatic collections for specific events
New Service Request Data Collections (SRDCs)
Event specific collection for default diagnostic collection
Option to restrict the collection of excessively large files
1
2
3
4

3. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Temporarily restrict automatic collections for specific events
New Service Request Data Collections (SRDCs)
Event specific collection for default diagnostic collection
Option to restrict the collection of excessively large files
1
2
3
4

4. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Temporarily restrict automatic collections for specific events
• blackout option added to tfactl command
• Temporarily prevents automatic diagnostic collections for specific events
• Can be set for certain targets, events & durations
• Examples:
– Do not collect ORA-00600 events on mydb for the next 24hrs (default time)
– Do not collect ORA-04031 events on any database for the next hour
– Do not collect any events (during patching)
tfactl blackout add -targettype database -target mydb -event "ORA-00600"
tfactl blackout add -targettype database -target mydb -event "ORA-04031"
tfactl blackout add -targettype all -event all -target all -timeout 1h -reason "Disabling all
events during patching"

5. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
• Use the print option to see all blackouts in place:
• Use remove to take away a blackout
Temporarily restrict automatic collections for specific events
.-------------------------------------------------------------------------------------------------------------------------------------------------------.
| Target Type | Target | Events | Start Time | End Time | Do Collection | Reason |
+-------------+--------+-----------+------------------------------+------------------------------+---------------+--------------------------------------+
| ALL | ALL | ALL | Tue Feb 19 00:23:47 PST 2019 | Tue Feb 19 01:23:47 PST 2019 | false | Disabling all events during patching |
| DATABASE | ALL | ORA-04030 | Tue Feb 19 00:22:39 PST 2019 | Sun Feb 19 00:22:39 PST 2119 | false | NA |
| DATABASE | ALL | ORA-04031 | Tue Feb 19 00:21:27 PST 2019 | Tue Feb 19 01:21:27 PST 2019 | false | NA |
| DATABASE | MYDB | ORA-00600 | Tue Feb 19 00:20:34 PST 2019 | Wed Feb 20 00:20:34 PST 2019 | false | NA |
'-------------+--------+-----------+------------------------------+------------------------------+---------------+--------------------------------------'
tfactl blackout print
tfactl blackout remove -targettype database -event "ORA-00600" -target mydb

6. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Temporarily restrict automatic collections for specific events
Manage TFA Blackouts
Usage : tfactl blackout add|remove|print -targettype all|crs|asm|asmdg|database|listener|service|os -
target all|name -event all|"event_str1,event_str2" [-timeout nh|nd|none] [-c|-local] [-reason "reason
for blackout"] [-docollection]
add|remove|print Adds or removes or print blackout conditions
-targettype <type> Limits the blackout to only the target type given
[all||crs|asm|asmdg|database|listener|service|os](default all)
-target all|name Target for blackout (default all)
-events all|"str1,str2" Limits blackout to only availability events or event strings which should
not trigger auto collections or be marked as backed out in telemetry JSON
-timeout nh|nd|none Duration for blackout in number of hours or days before timing out
(default 24h)
-c|-local Cluster wide or Local (default local)
-reason <comment> Comment describing the reason for the blackout
-docollection Even though a blackout is set still do an auto collection for this target
tfactl blackout -help

7. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Temporarily restrict automatic collections for specific events
New Service Request Data Collections (SRDCs)
Event specific collection for default diagnostic collection
Option to restrict the collection of excessively large files
1
2
3
4

8. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
New SRDCs (Service Request Diagnostic Collections)
• The following new SRDCs are now available:
– dbrac: Oracle RAC-related data collection for Oracle Clusterware and Oracle ASM
problems
– dbracinst: Oracle RAC-related data collection for Oracle Database problems
– gridinfra: Oracle RAC-related data collection for Oracle Clusterware problems
– gridinfrainst: Data collection for Oracle RAC upgrade and patching problems
– exsmartscan: Oracle Exadata - Smart Scan not working problems
– zlgeneric: Data collection for Zero Data Loss Recovery Appliance (ZDLRA) problems
As with all other SRDCs use tfactl diagcollect -srdc srdc_name

9. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Enter the Database Name [Required for this SRDC] : zdlra8
Enter the password for the user rasys: [Required for this
SRDC]:
Scripts to be run by this srdc: get_ra_version get_ra_status
get_ra_release_info get_cluster_status srdc_collect_ra_inciden
t_info.sql zip_radump_files
SystemActivityReport12_1_1_1_8_and_12_2_1_1_2.sql
SystemActivityReport12_1_1_1_7.sql
Components included in this srdc: OS CRS DATABASE NOCHMOS
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
WARNING: User 'oracle' is not allowed to run Collections on
Storage Cells (Run diagcollect as root user to collect files fr
om Storage Cells).
Collecting data for all nodes
Collection Id : 20190307065416scao09adm03
Detailed Logging at :
/u01/app/oracle/tfa/repository/srdc_zlgeneric_collection_Thu_Mar
_07_06_54_17_PST_2019_node_all/diagco
llect_20190307065416_scao09adm03.log
……
….
/u01/app/oracle/tfa/repository/srdc_zlgeneric_collection_Thu_Mar
_07_06_54_17_PST_2019_node_all/scao09adm04.tfa_srdc_zlgener
ic_Thu_Mar_07_06_54_17_PST_2019.zip
Example: ZDLRA SRDC
Etc…
tfactl diagcollect –srdc zlgeneric

10. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Temporarily restrict automatic collections for specific events
New Service Request Data Collections (SRDCs)
Event specific collection for default diagnostic collection
Option to restrict the collection of excessively large files
1
2
3
4

11. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Event specific collection for default diagnostic collection
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
tfactl diagcollect

12. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Event specific collection for default diagnostic collection
Collecting data for all nodes
Scanning files from mar/11/2019 18:02:19 to mar/11/2019 23:02:19
Collection Id : 20190312162708myserver
Detailed Logging at :
/scratch/app/product/18c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all/diagcollect_20190312162708_myse
rver.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 : [myserver]
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 |
+----------+-----------+------+------+
| myserver | Completed | 10MB | 21s |
'----------+-----------+------+------'
Logs are being collected to: /scratch/app/product/18c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all
/scratch/app/product/18c/tfa/repository/collection_Tue_Mar_12_16_27_09_PDT_2019_node_all/myserver.tfa_Tue_Mar_12_16_27_0
9_PDT_2019.zip

13. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Event specific collection for default diagnostic collection
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
Event with an existing SRDC – SRDC will be used for collection
The user running the collection needs to be in the dbagroup of the database chosen in the event list
tfactl diagcollect

14. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Event with an existing SRDC – SRDC will be used for collection
Event specific collection for default diagnostic collection
Scripts to be run by this srdc: srdc_db_sid_memorysizes_10glower.sql srdc_db_sid_memorysizes_11gplus.sql ipspack rdahcve1210
rdahcve1120 rdahcve1110
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 : 20190312163524myserver
Detailed Logging at :
/scratch/app/product/18c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local/diagcollect_20190312163524
_myserver.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 |
+----------+-----------+-------+------+
| myserver | Completed | 2.9MB | 24s |
'----------+-----------+-------+------'
Logs are being collected to:
/scratch/app/product/18c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local
/scratch/app/product/18c/tfa/repository/srdc_ora4030_collection_Tue_Mar_12_16_35_25_PDT_2019_node_local/myserver.tfa_srdc_ora4030_
Tue_Mar_12_16_35_25_PDT_2019.zip

15. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Running a default non event specific collection
Event specific collection for default diagnostic collection
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

16. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Program Agenda
Temporarily restrict automatic collections for specific events
New Service Request Data Collections (SRDCs)
Event specific collection for default diagnostic collection
Option to restrict the collection of excessively large files
1
2
3
4

17. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Option to restrict the collection of excessively large files
• During collection (both on-demand and automated) TFA will verify the size
of each file to be collected
– If file is greater than MaxFileCollectSize MB only the last 1,000 lines will be collected
– Creates a new file to the TFA Collection called skipped_files.txt showing all the files
that were too large
tfactl set MaxFileCollectSize <size_mb>

18. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
Option to restrict the collection of excessively large files
tfactl print config
.------------------------------------------------------------------------------------.
| myserver |
+-----------------------------------------------------------------------+------------+
| Configuration Parameter | Value |
+-----------------------------------------------------------------------+------------+
| TFA Version | 19.1.0.0.0 |
…
…
| Max Collection Size of Core Files (MB) | 500 |
| Max File Collection Size (MB) | 5120 |
| Minimum Free Space to enable Alert Log Scan (MB) | 500 |
| Time interval between consecutive Disk Usage Snapshot(minutes) | 60 |
| Age of Purging Collections (Hours) | 12 |
| TFA IPS Pool Size | 5 |
…
…
| AUTO Collection will be generated for CHA EVENTS | false |
'-----------------------------------------------------------------------+------------'

19. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |
For more info see
Document: 1513912.1

20. Copyright © 2018, Oracle and/or its affiliates. All rights reserved. |