@@@@Platform-“OnPrem”

@@@@Product-“Database”

@@@@ReleaseVersion-“26.11”

@@@@info-map-label-“tfactl analyze”

tfactl analyze

Use the tfactl analyze command to obtain analysis of your system by parsing the database, Oracle Automatic Storage Management (Oracle ASM), and Oracle Grid Infrastructure alert logs, system message logs, OSWatcher Top, and OSWatcher Slabinfo files.

Filter the output of the command by component, error type, and time.

With the tfactl analyze command, you can choose from the following types of log file analysis:

Syntax

tfactl analyze
[-search "pattern"]
[-comp db|asm|crs|acfs|os|osw|oswslabinfo|oratop|all]
[-type error|warning|generic]
[-last n[h|d]]
[-from time]
[-to time]
[-for time]
[-node all|local|n1,n2,...]
[-verbose]
[-o file]
[timeline [-l n] f1 f2...fn]
[-examples]

Parameters

tfactl analyze Command Parameters

Parameter Description
-search " pattern "

Searches for a pattern enclosed in double quotation marks ("") in system and alert logs within a specified time range. This parameter supports both case-sensitive and case-insensitive search in alert and system message files across the cluster within the specified filters. Default is case insensitive.

If you do not specify the -search parameter, then Oracle Trace File Analyzer provides a summary of messages within specified filters from alert and system log messages across the cluster.

Oracle Trace File Analyzer displays message counts grouped by type (error, warning, and generic) and shows unique messages in a table organized by message type selected for analysis. The generic message type is assigned to all messages which are not either an error or warning message type.

[-comp db|asm|crs|acfs|os|osw|oswslabinfo|oratop|all]

Select which components you want Oracle Trace File Analyzer to analyze. Default is all.

  • db: Database alert logs
  • asm: Oracle ASM alert logs
  • crs: Oracle Grid Infrastructure alert logs
  • acfs: Oracle ACFS alert logs
  • os: System message files
  • osw: OSW Top output
  • oswlabinfo: OSW Slabinfo output

When OSWatcher data is available, OSW and OSWSLABINFO components provide summary views of OSWatcher data.

-type error | warning | generic Select what type of messages Oracle Trace File Analyzer analyzes. Default is error.
[-last n [ h | d ]] Specify an amount of time, in hours or days, before current time that you want Oracle Trace File Analyzer to analyze.
-from | -to | -for time

Specify a time interval, using the -from and -to parameters together.

Supported time formats:

"Mon/dd/yyyy hh:mm:ss""yyyy-mm-dd hh:mm:ss""yyyy-mm-ddThh:mm:ss""yyyy-mm-dd"

Or, a specific time using the -for parameter that you want Oracle Trace File Analyzer to analyze.

Supported time formats:

"Mon/dd/yyyy""yyyy-mm-dd"
[-node all|local| n1 , n2 ,...] Specify a comma-separated list of host names. Use -local to analyze files on the local node. Default is all.
-verbose Displays verbose output.
-o file Specify a file where Oracle Trace File Analyzer writes the output instead of displaying on the screen.
timeline

Displays timeline for the specified trace or alert log files.

-ln: Specify debug level, for example, l 3.

Debug levels:

  • 1 - FATAL
  • 2 - ERROR
  • 3 - WARNING
  • 4 - INFO (default)
  • 5 - DEBUG
  • 6 - TRACE

f1f2...fn: Specify a space-delimited list of file names.

[-examples] Specify this parameter to view analyze usage examples.

-type Parameter Arguments

The tfactl analyze command classifies all the messages into different categories when you specify the -type parameter. The analysis component provides count of messages by the message type you configure and lists all unique messages grouped by count within specified filters. The message type patterns for each argument are listed in the following table.

tfactl analyze -type Parameter Arguments

Argument Description
error

Error message patterns for Oracle Database and Oracle ASM alert logs:

.ORA-00600:..ORA-07445:..IPC Send timeout detected. Sender: ospid..Direct NFS: channel id . path .* to filer .* PING timeout..Direct NFS: channel id . path . to filer .* is DOWN..ospid: . has not called a wait for . secs..IPC Send timeout to . inc . for msg type .* from opid..IPC Send timeout: Terminating pid..Receiver: inst . binc . ospid.. terminating instance due to error..: terminating the instance due to error.*.*Global Enqueue Services Deadlock detected.ORA-031(13|37):..ORA-00603:..ORA-0035(3|5|6):..ORA-00700:..ORA-040(20|36):..ORA-0403(0|1):..ORA-002(27|39|40|55):..ORA-01578:..ORA-2(5319|4982):..ORA-56729:..ORA-00445:.

Error message patterns for Oracle Grid Infrastructure alert logs:

.CRS-8011:..CRS-8013:..CRS-1607:..CRS-1615:..CRS-1714:..CRS-1656:..PRVF-5305:..CRS-1601:..CRS-1610:..PANIC. CRSD exiting:..Fatal Error from AGFW Proxy:..CRS-1603:..CRS-10051:..CRS-2409:..CRS-1625:.
warning

Warning message patterns for database and Oracle ASM alert logs:

NOTE: process .* initiating offline of disk .*.WARNING: cache read a corrupted block group..*NOTE: a corrupted block from group FRA was dumped to
generic Any messages that do not match any of the preceding patterns.

oratop options

The options available when using -comp oratop:

-database dbname oratop options logon

tfactl analyze -comp oratop options

Argument Description
-database dbname Specify the name of the Oracle Database to run oratop.
logon

Default is / as sysdba.

Specify a different user using,

{username[/password][@connect_identifier] | / } [AS {SYSDBA|SYSOPER}]

Connect Identifier:

host[:port]/[service_name]

oratop options

Argument Description
-b Specify the batch mode. Default: text-based user interface.
-n Specify the maximum number of iterations.
-o Writes console output to a file (in batch mode).
-i Specify the interval delay in seconds. Default: 5 seconds.
-r Real-time (RT) wait events. (sec 3, default: Cumulative)
-m Specify MODULE / ACTION (section 4). Default: USERNAME / PROGRAM.
-s Specify the SQL mode (section 4). Default: process mode.
-f Specify the detailed format (132 columns). Default: standard (80 columns).
-v Displays oratop release version number.

Examples

The following command examples demonstrate how to use Oracle Trace File Analyzer to search collected data:

The following command examples demonstrate how to use Oracle Trace File Analyzer to analyze collected data:

The following command examples demonstrate how to use Oracle Trace File Analyzer to analyze OSWatcher Top and Slabinfo: