Use the custom collection options to change the diagnostic collections from the default.
Oracle Trace File Analyzer trims and collects any important logs updated in the past 12 hours.
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:
Table 6-1 Ways to Specify the Collection Period
Command | Description |
---|---|
|
Collects since the previous n hours or days. |
|
Collects from the date and optionally time specified. Valid date and time formats:
|
|
Collects between the date and optionally time specified. Valid date and time formats:
|
|
Collects for the specified date. Valid date formats:
|
Parent topic: Performing Custom Collections
To collect from specific nodes:
Related Topics
Parent topic: Performing Custom Collections
To collect from specific components:
Related Topics
Parent topic: Performing Custom Collections
Oracle Trace File Analyzer discovers all Oracle diagnostics and collects relevant files based on the type and last time updated.
If you want to collect other files, then you can specify extra directories. Oracle Trace File Analyzer collects only the files updated in the relevant time range (12 hours by default).
You can configure collection of all files irrespective of the time last updated. Configure on a directory by directory basis using the -collectall
option.
To collect from specific directories:
Related Topics
Parent topic: Performing Custom Collections
Oracle Trace File Analyzer zips collections and puts the zip files in the repository directory, using the following naming format:
repository/collection_date_time/node_all/node.tfa_date_time.zip
You must only change the name of the zipped files using the following options. Manually changing the file name prevents you from using collections with various Oracle Support self-service tools.
To change the collection name:
Related Topics
Parent topic: Performing Custom Collections
By default, Oracle Trace File Analyzer Collector:
Copies back all zip files from remote notes to the initiating node
Trims files around the relevant time
To prevent copying zip files and trimming files:
Related Topics
Parent topic: Performing Custom Collections
Incident Packaging Service packages details of problems stored by Oracle Database in ADR for later diagnosis.
Syntax
Oracle Trace File Analyzer runs IPS to query and collect these packages.
tfactl ips option
Table 6-3 tfactl ips Command Parameters
Command | Description |
---|---|
|
Runs the IPS. |
|
Shows all IPS incidents. |
|
Shows all IPS problems. |
|
Shows all IPS Packages. |
|
Shows all available |
|
Performs an IPS collection following prompts. You can use all the standard |
|
Performs an IPS collection in silent mode. |
|
Collects ADR details about a specific incident id. |
|
Collect ADR details about a specific problem id. |
You can change the contents of the IPS package. Use the following options:
Start the collection.
Suspend the collection using the -manageips
option.
For example:
$ tfactl diagcollect -ips -incident incident_id -manageips -node local
Find the suspended collection using the print suspendedips
option.
For example:
$ tfactl print suspendedips
Manipulate the package.
Resume the collection using the -resumeips
option.
For example:
$ tfactl diagcollect -resumeips collection_id
Example 6-1 Show Incidents
$ tfactl ips show incidents ADR Home = /scratch/app/crsusr/diag/clients/user_crsusr/host_622665046_106: ************************************************************************* 0 rows fetched ADR Home = /scratch/app/crsusr/diag/afdboot/user_root/host_622665046_106: ************************************************************************* 0 rows fetched ADR Home = /scratch/app/crsusr/diag/rdbms/_mgmtdb/-MGMTDB: ************************************************************************* INCIDENT_ID PROBLEM_KEY CREATE_TIME -------------------- ----------------------------------------------------------- ---------------------------------------- 12913 ORA 700 [kskvmstatact: excessive swapping observed] 2016-06-30 14:05:48.491000 -07:00 12914 ORA 700 [kskvmstatact: excessive swapping observed] 2016-06-30 15:06:16.545000 -07:00 13161 ORA 445 2016-06-30 15:10:53.756000 -07:00 ADR Home = /scratch/app/crsusr/diag/asm/+asm/+ASM1: ************************************************************************* INCIDENT_ID PROBLEM_KEY CREATE_TIME -------------------- ----------------------------------------------------------- ---------------------------------------- 1177 ORA 445 2016-06-30 15:10:12.930000 -07:00 ADR Home = /scratch/app/crsusr/diag/asm/user_root/host_622665046_106: *************************************************************************
Example 6-2 Show Problems
$ tfactl ips show problems ADR Home = /scratch/app/crsusr/diag/afdboot/user_root/host_622665046_106: ************************************************************************* 0 rows fetched ADR Home = /scratch/app/crsusr/diag/rdbms/_mgmtdb/-MGMTDB: ************************************************************************* PROBLEM_ID PROBLEM_KEY LAST_INCIDENT LASTINC_TIME -------------------- ----------------------------------------------------------- -------------------- 1 ORA 700 [kskvmstatact: excessive swapping observed] 12914 2016-06-30 15:06:16.545000 -07:00 2 ORA 445 13161 2016-06-30 15:10:53.756000 -07:00 ADR Home = /scratch/app/crsusr/diag/asm/+asm/+ASM1: ************************************************************************* PROBLEM_ID PROBLEM_KEY LAST_INCIDENT LASTINC_TIME -------------------- ----------------------------------------------------------- -------------------- 1 ORA 445 1177 2016-06-30 15:10:12.930000 -07:00
Example 6-3 Show Packages
$ tfactl ips show package Multiple ADR homepaths were found for /scratch/app/crsusr, please select one ... ( ) option[0] diag/asmtool/user_root/host_622665046_106 ( ) option[1] diag/asmtool/user_crsusr/host_622665046_106 ( ) option[2] diag/clients/user_root/host_622665046_106 ( ) option[3] diag/clients/user_crsusr/host_622665046_106 ( ) option[4] diag/afdboot/user_root/host_622665046_106 ( ) option[5] diag/rdbms/_mgmtdb/-MGMTDB option[6] Done Pls select a homepath [6] ?5 diag/rdbms/_mgmtdb/-MGMTDB was selected PACKAGE_ID 1 PACKAGE_NAME ORA700kge_20160731211334 PACKAGE_DESCRIPTION DRIVING_PROBLEM 2 DRIVING_PROBLEM_KEY ORA 700 [kgerev1] DRIVING_INCIDENT 42605 DRIVING_INCIDENT_TIME 2016-07-05 07:53:28.578000 -07:00 STATUS Generated (4) CORRELATION_LEVEL Typical (2) PROBLEMS 2 main problems, 0 correlated problems INCIDENTS 2 main incidents, 0 correlated incidents INCLUDED_FILES 84 PACKAGE_ID 2 PACKAGE_NAME IPSPKG_20160801203518 PACKAGE_DESCRIPTION DRIVING_PROBLEM N/A DRIVING_PROBLEM_KEY N/A DRIVING_INCIDENT N/A DRIVING_INCIDENT_TIME N/A STATUS Generated (4) CORRELATION_LEVEL Typical (2) PROBLEMS 0 main problems, 0 correlated problems INCIDENTS 0 main incidents, 0 correlated incidents INCLUDED_FILES 27
Example 6-4 IPS Collect
$ tfactl diagcollect -ips Collecting data for the last 12 hours for this component ... Collecting data for all nodes Creating ips package in master node ... Multiple ADR homepaths were found for /scratch/app/crsusr, please select one or more... ( ) option[0] diag/asmtool/user_root/host_622665046_106 ( ) option[1] diag/asmtool/user_crsusr/host_622665046_106 ( ) option[2] diag/clients/user_root/host_622665046_106 ( ) option[3] diag/clients/user_crsusr/host_622665046_106 ( ) option[4] diag/afdboot/user_root/host_622665046_106 ( ) option[5] diag/rdbms/_mgmtdb/-MGMTDB option[6] Done Pls select a homepath [6] ?5 diag/rdbms/_mgmtdb/-MGMTDB was selected Please select at least one ADR homepath. Multiple ADR homepaths were found for /scratch/app/crsusr, please select one or more... ( ) option[0] diag/asmtool/user_root/host_622665046_106 ( ) option[1] diag/asmtool/user_crsusr/host_622665046_106 ( ) option[2] diag/clients/user_root/host_622665046_106 ( ) option[3] diag/clients/user_crsusr/host_622665046_106 ( ) option[4] diag/afdboot/user_root/host_622665046_106 (*) option[5] diag/rdbms/_mgmtdb/-MGMTDB option[6] Done Pls select a homepath [6] ? Trying ADR basepath /scratch/app/crsusr Trying to use ADR homepath diag/rdbms/_mgmtdb/-MGMTDB ... Submitting request to generate package for ADR homepath /scratch/app/crsusr/diag/rdbms/_mgmtdb/-MGMTDB Master package completed for ADR homepath /scratch/app/crsusr/diag/rdbms/_mgmtdb/-MGMTDB Created package 15 based on time range 2016-08-21 15:58:00.000000 -07:00 to 2016-08-22 03:58:00.000000 -07:00, correlation level basic Remote package completed for ADR homepath(s) /diag/rdbms/_mgmtdb/-MGMTDB Collection Id : 20160822035856myserver65 Detailed Logging at : /scratch/app/crsusr/tfa/repository/collection_Mon_Aug_22_03_58_56_PDT_2016_node_all/ diagcollect_20160822035856_myserver65.log 2016/08/22 03:59:40 PDT : Collection Name : tfa_Mon_Aug_22_03_58_56_PDT_2016.zip 2016/08/22 03:59:40 PDT : Collecting diagnostics from hosts : [myserver65, myserver66] 2016/08/22 03:59:40 PDT : Getting list of files satisfying time range [08/21/2016 15:59:40 PDT, 08/22/2016 03:59:40 PDT] 2016/08/22 03:59:40 PDT : Collecting additional diagnostic information... 2016/08/22 03:59:51 PDT : Completed collection of additional diagnostic information... 2016/08/22 03:59:51 PDT : Completed Local Collection 2016/08/22 03:59:51 PDT : Remote Collection in Progress... .---------------------------------------. | Collection Summary | +------------+-----------+-------+------+ | Host | Status | Size | Time | +------------+-----------+-------+------+ | myserver66 | Completed | 254kB | 16s | | myserver65 | Completed | 492kB | 11s | '------------+-----------+-------+------' Logs are being collected to: /scratch/app/crsusr/tfa/repository/collection_Mon_Aug_22_03_58_56_PDT_2016_node_all /scratch/app/crsusr/tfa/repository/collection_Mon_Aug_22_03_58_56_PDT_2016_node_all/ myserver66.tfa_Mon_Aug_22_03_58_56_PDT_2016.zip /scratch/app/crsusr/tfa/repository/collection_Mon_Aug_22_03_58_56_PDT_2016_node_all/ myserver65.tfa_Mon_Aug_22_03_58_56_PDT_2016.zip
Related Topics
Parent topic: Performing Custom Collections