6.6 Oracle Trace File Analyzer Service Request Data Collections (SRDCs)

Oracle Trace File Analyzer Service Request Data Collections (SRDCs) enable you to quickly collect the right diagnostic data.

To perform Service Request Data Collections:

$ tfactl diagcollect -srdc srdc_name

Running the command trims and collects all important log files updated in the past n hours across the whole cluster. The default number of hours for log collection varies from SRDC to SRDC. You can change the diagcollect timeframe with the –last n h|d option.

Oracle Support often asks you to run a Service Request Data Collection (SRDC). The SRDC depends on the type of problem that you experienced. An SRDC is a series of many data gathering instructions aimed at diagnosing your problem. Collecting the SRDC manually can be difficult with many different steps required.

Oracle Trace File Analyzer can run SRDC collections with a single command:

$ tfactl diagcollect 
[-srdc srdc_profile] 
[–sr sr_number]
[-tag tagname] 
[-z filename] 
[-last nh|d | -from time -to time | -for date] 
[-database database]
Option Description

[-srdc srdc_profile]

Specify the SRDC profile.

-tag description

Use this parameter to create a subdirectory for the resulting collection in the Oracle Trace File Analyzer repository.

-z file_name

Use this parameter to specify an output file name.

[-last nh|d | -from time -to time | -for date]

  • Specify the -last parameter to collect files that have relevant data for the past specific number of hours (h) or days (d). By default, using the command with this parameter also trims files that are large and shows files only from the specified interval.

    You can also use -since, which has the same functionality as -last. This option is included for backward compatibility.

  • Specify the -from and -to parameters (you must use these two parameters together) to collect files that have relevant data during a specific time interval, and trim data before this time where files are large.

    Supported time formats:

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

    "yyyy-mm-dd hh:mm:ss"

    "yyyy-mm-ddThh:mm:ss"

    "yyyy-mm-dd"

  • Specify the -for parameter to collect files that have relevant data for the date specified. The files tfactl collects will have timestamps in between which the time you specify after -for is included. No data trimming is done for this option.

    Supported time formats:

    "Mon/dd/yyyy"

    "yyyy-mm-dd"

Note:

If you specify both date and time, then you must enclose both the values in double quotation marks (""). If you specify only the date or the time, then you do not have to enclose the single value in quotation marks.

-database database

Specify the name of the database.

Note:

To upload collections to the SR as part of diag collection:

If you have already set MOS configuration using the tfactl setupmos command, then you can use the -sr option along with the diag collection command.

If you have not set MOS configuration using the tfactl setupmos command, then set up MOS configuration using the new generic command, tfactl setupload -name mos -type https and follow the instructions.

For example: tfactl diagcollect -srdc srdc_type –sr sr_number

To run SRDCs, use one of the Oracle privileged user accounts:

  • ORACLE_HOME owner

  • GRID_HOME owner

Table 6-3 One Command Service Request Data Collections

Available SRDCs Type of Problem Collection Scope

ahf

Oracle ORAchk and Oracle EXAchk problems (to be run after running with -debug)

Local only

dbacl

Problems with Access Control Lists (ACLs)

Local only

dbaqgen

Problems in an Oracle Advanced Queuing Environment

Local only

dbaqmon

Queue Monitor (QMON) problems

Local only

dbaqnotify

Notification problems in an Oracle Advanced Queuing Environment

Local only

dbaqperf

Performance problems in an Oracle Advanced Queuing Environment

Local only

dbasm

Oracle Database storage problems

Local only

dbaudit

Standard information for Oracle Database auditing

Local only

dbawrspace

Excessive SYSAUX space is used by the Automatic Workload Repository (AWR)

Local only

dbdatapatch

Datapatch problems

Local only

dbexp

dbexpdp

dbexpdpapi

dbexpdpperf

dbexpdptts

Original Oracle Database Export (exp)

Local only

dbfs

Oracle Automatic Storage Management (Oracle ASM) / Database File System (DBFS) / Direct NFS / Oracle Automatic Storage Management Cluster File System (Oracle ACFS) problems

Local only

dbggclassicmode

dbggintegratedmode

Oracle GoldenGate

Local only

dbimp

dbimpdp

dbimpdpperf

Original Oracle Database Import (imp)

Local only

dbimpdpperf

Data Pump Import performance problems

Local only

dbinstall

dbupgrade

dbpreupgrade

Oracle Database install / upgrade problems

Local only

dbparameters

Oracle Database single instance shutdown problems

Local only

dbpartition

Create or maintain partitioned table, subpartitioned table, and index problems

Local only

dbpartitionperf

Slow Create, Alter, or Drop commands against partitioned table or index

Local only

dbpatchinstall

dbpatchconflict

Oracle Database patching problems

Local only

dbperf

Oracle Database performance problems

Cluster-wide

dbrac

Oracle RAC-related data collection for Oracle Clusterware and Oracle ASM problems

Local only

dbracinst

Oracle RAC-related data collection for Oracle Database problems

Local only

dbrman

dbrman600

dbrmanperf

Recovery Manager (RMAN) problems

Local only

dbscn

System change number

Local only

dbshutdown

dbstartup

Oracle Database startup or shutdown problems

Local only

dbspatialexportimport

Oracle Spatial export or import problems

Local only

dbspatialinstall

Oracle Spatial installation problems

Local only

dbsqlperf

SQL performance problems

Local only

dbstandalonedbca

Database Configuration Assistant problems

Local only

dbtde

Transparent Data Encryption (TDE) problems

Local only

dbtextupgrade

dbtextinstall

Oracle Text version 12.1.0.1 and later upgrade problems

Local only

dbundocorruption

UNDO corruption problems

Local only

dbunixresources

Oracle Database resource problems

Local only

dbxdb

XDB Installation or invalid object problems

Local only

emagentperf

Enterprise Manager 13c Agent performance problems

Local only

emagentstartup

Enterprise Manager 13c Agent startup problems

Local only

emagtpatchdeploy

Enterprise Manager 13c Agent patch deployment problems

Local only

emagtupgpatch

Enterprise Manager 13c Agent upgrade or local installation or patching problems.

Local only

emcliadd

emclusdisc

emdbsys

emgendisc

emprocdisc

Enterprise Manager target discovery or add problems

Local only

emdbaasdeploy

Database As A Service (DBaaS): Collect trace or log information for failures during DBaaS deployment.

Enterprise Manager OMS and remote DBaaS deployment server.

emdebugon

emdebugoff

Enterprise Manager debug log collection

Run emdebugon, reproduce the problem then run emdebugoff, which disables debug again and collects debug logs

Local only (on Enterprise Manager Agent target and Oracle Management Service)

emfleetpatching

Enterprise Manager Fleet Maintenance Patching problems

Local only

emmetricalert

Enterprise Manager general metrics page or threshold problems

Local only (on Enterprise Manager Agent target and repository database)

emomscrash

Enterprise Manager OMS Crash problems

Local only

emomsheap

Enterprise Manager Java heap usage or performance problems

Local only

emomshungcpu

Enterprise Manager OMS crash, restart or performance problems

Local only

empatchplancrt

Enterprise Manager patch plan creation problems

Local only

emrestartoms

Enterprise Manager OMS restart problems

Local only

emtbsmetrics

Enterprise Manager tablespace usage metric problems

Local only (on Enterprise Manager Agent target)

esexalogic

Oracle Exalogic full Exalogs data collection information

Local only

exservice

Oracle Exadata: Storage software service or offload server service problems

Local only

exsmartscan

Oracle Exadata: Smart Scan not working problems

Local only

gridinfra

Oracle RAC-related data collection for Oracle Clusterware problems

Local only

gridinfrainst

Oracle RAC upgrade and patching problems

Local only

instterm

Collect traces for ORA-004nn errors.

Local only

internalerror

Other internal Oracle Database errors

Local only

listener_services

Listener errors: TNS12516 / TNS12518 / TNS12519 / TNS12520

Local only

naming_services

Naming service errors: TNS12154 / TNS12528

Local only

ORA-00020

ORA-00060

ORA-00600

ORA-00700

ORA-01031

ORA-01555

ORA-01578

ORA-01628

ORA-04020

ORA-04021

ORA-04030

ORA-04023

ORA-04031

ORA-04063

ORA-07445

ORA-08102

ORA-08103

ORA-27300

ORA-27301

ORA-27302

ORA-30036

ORA Errors

Local only

ORA-01000

Open Cursors problems

Local only

ORA-00018

ORA-00018 or sessions parameter problems

Local only

ORA-25319

ORA-25319 problems in an Oracle Advanced Queuing Environment

Local only

zlgeneric

Zero Data Loss Recovery Appliance (ZDLRA) problems

Local only

For more information about SRDCs, run tfactl diagcollect –srdc -help.

The types of information that the SRDCs collect varies for each type, for example, the following table lists and describes what the SRDCs collect for each type.

Table 6-4 SRDC collections

Command What gets collected

$ tfactl diagcollect –srdc ORA-04031

  • Incident Packaging Service (IPS) package

  • Patch listing

  • Automatic Workload Repository (AWR) report

  • Memory information

$ tfactl diagcollect –srdc dbperf

  • Automatic Database Diagnostic Monitor (ADDM) report

  • Automatic Workload Repository (AWR) for good period and problem period

  • Automatic Workload Repository (AWR) Compare Period report

  • Active Session History (ASH) report for good and problem period

  • OSWatcher

  • Incident Packaging Service (IPS) package (if there are any errors during problem period)

  • Oracle ORAchk (performance-related checks)

Oracle Trace File Analyzer prompts you to enter the information required based on the SRDC type.

For example, when you run ORA-4031 SRDC:

$ tfactl diagcollect –srdc ORA-04031

Oracle Trace File Analyzer:

  1. Prompts to enter event date, time, and database name.

  2. Scans the system to identify recent events in the system (up to 10).

  3. Proceeds with diagnostic collection after you choose the relevant event.

  4. Identifies all the required files.

  5. Trims all the files where applicable.

  6. Packages all data in a zip file ready to provide to support.

You can also run an SRDC collection in non-interactive silent mode. Provide all the required parameters up front as follows:

$ tfactl diagcollect –srdc srdc_type -database db -from "date time" -to "date time"