tfactl diagcollect -srdc

Use the tfactl diagcollect -srdc command to run a Service Request Data Collection (SRDC).

Syntax

tfactl diagcollect -srdc srdc_profile
[-tag tagname]
[-z filename]
[-last nh|d | -from time -to time | -for date]
-database database

Parameters

Each option must be prefixed with a minus sign (-).

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` `n` `h` `\|` `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.

SRDC Profiles

SRDC Profile	Description
`listener_services`	Collects data for listener services errors: `TNS-12514` / `TNS-12516` / `TNS-12518` / `TNS-12519` / `TNS-12520` / `TNS-12528`.
`naming_services`	Collects data for naming services errors: `ORA-12514` / `ORA-12528`.
`ORA-00020`	Collects data regarding maximum number of processes exceeded.
`ORA-00060`, `ORA-00600`	Collects data for internal errors.
`ORA-00700`	Collects data for soft internal error.
`ORA-01031`	Collects standard information for `ORA-1031` / `ORA-1017` during SYSDBA connections
`ORA-01555`	Collects data for Oracle Database Snapshot too old error.
`ORA-01578`	Collects data for `NOLOGGING ORA-1578` / `ORA-26040 DBV-00201`.
`ORA-01628`	Collects data for Oracle Database Snapshot too old error.
`ORA-04030`	Collects data for `OS process private memory was exhausted` error.
`ORA-04031`	Collects data for More shared memory is needed in the shared/streams pool. error.
`ORA-07445`	Collects data for Exception encountered, core dump. error.
`ORA-08102`	Collects data for ORA error `ORA-08102`.
`ORA-08103`	Collects data for ORA error `ORA-08103`.
`ORA-27300`	Collects data for OS system dependent operation: open failed with status: (status). error.
`ORA-27301`	Collects data for OS failure message: (message). error.
`ORA-27302`	Collects data for Failure occurred at: (module). error.
`ORA-30036`	Collects data for Oracle Database Unable to extend Undo Tablespace error.
`crsasmcell`	Collects data for ASM CRS CELL-related problems. The cell related errors handled by `crsasmcell` are: `CRS-1604` `CRS-1606` `CRS-1613` `CRS-1614` `CRS-1615` `CRS-1649`
`dbasm`	Collects data for Oracle Database storage problems.
`dbaudit`	Collects standard information for Oracle Database auditing.
`dbawrspace`	Collects data for Oracle Database Automatic Workload Repository (AWR) space problems.
`dbexp`	Collects information for troubleshooting original Export (exp) related problems.
`dbexpdp`	Collects data for Data Pump Export generic issues.
`dbexpdpapi`	Collects data for Data Pump Export API Issues.
`dbexpdpperf`	Collects data for Data Pump Export performance issues.
`dbexpdptts`	Collects data to supply for Transportable Tablespace Data Pump and original EXPORT, IMPORT.
`dbfs`	Collects data for `dbfs` issues.
`dbggclassicmode`	Collects data for Oracle GoldenGate Classic Mode issues.
`dbggintegratedmode`	Collects data for Oracle GoldenGate Extract / Replicat abends problems.
`dbimp`	Collects data for troubleshooting original Import (imp) releated problems.
`dbimpdp`	Collects data for Data Pump Import generic issues.
`dbimpdpperf`	Collects data for Data Pump Import performance issues.
`dbinstall`	Collects data for Oracle Database install / upgrade problems.
`dbpartition`	Collects data for `Create` / maintain partitioned / subpartitioned table / index problems.
`dbpartitionperf`	Collects data for slow `Create` / `Alter` / `Drop` commands against partitioned table / index problems.
`dbpatchconflict`	Collects data for Oracle Database patch conflict problems.
`dbpatchinstall`	Collects data for Oracle Database patch install problems.
`dbperf`	Collects data for Oracle Database performance problems.
`dbpreupgrade`	Collects data for Oracle Database preupgrade problems.
`dbrman`	Collects data for RMAN related issues, such as backup, maintenance, restore and recover, `RMAN-08137`, or `RMAN-08120`.
`dbrman600`	Collects data for `RMAN-00600` error (My Oracle Support note 2045195.1).
`dbrmanperf`	Collects data for RMAN Performance error (My Oracle Support note 1671509.1).
`dbscn`	Collects data for Oracle Database SCN problems.
`dbshutdown`	Collects data for single instance Oracle Database shutdown problems.
`dbsqlperf`	Collects data for an SQL performance problem using Oracle Trace File Analyzer Collector.
`dbstartup`	Collects data for single instance Oracle Database startup problems.
`dbtde`	Collects data for Transparent Data Encryption (TDE) (My Oracle Support note 1905607.1)
`dbunixresources`	Collects data for Oracle Database issues related to operating system resources.
`dbupgrade`	Collects data for Oracle Database upgrade problems.
`dbxdb`	Collects data Oracle Database XDB installation and invalid object problems.
`dnfs`	Collects data for DNFS problems.
`emagentperf`	Collects data for Enterprise Manager Agent performance issues.
`emcliadd`	Collects data for Enterprise Manager errors while adding an Oracle Database, a listener, or an ASM target using Enterprise Manager command-line.
`emclusdisc`	Collects data for cluster target, cluster (RAC) Oracle Database, or an ASM target is not discovered issue.
`emdbsys`	Collects data for Enterprise Manager Oracle Database system target is not discovered, detected, removed, or renamed correctly issue.
`emdebugoff`	Collects data for unsetting Enterprise Manager debug.
`emdebugon`	Collects data for setting Enterprise Manager debug.
`emgendisc`	Collects data for Enterprise Manager generic error while discovering, or removing an Oracle Database, a listener, or an ASM target.
`emmetricalert`	Collects data for Enterprise Manager metric events not raised and general metric alert related issues.
`emomscrash`	Collects for all Enterprise Manager OMS crash or restart performance issues.
`emomsheap`	Collects data for Enterprise Manager OMS heap usage alert performance issues.
`emomshungcpu`	Collects data for Enterprise Manager OMS hung or high CPU usage performance issues.
`emprocdisc`	Collects data for Enterprise Manager Oracle Database, listener, or an ASM target is not discovered or detected by the discovery process issues.
`emrestartoms`	Collects data for Enterprise Manager restart OMS crash problems.
`emtbsmetric`	Collects data for Enterprise Manager Tablespace space used metric issues.
`esexalogic`	Collects data for Oracle Exalogic Full Exalogs problems.
`ggintegratedmodenodb`	Collects data for Oracle GoldenGate Extract/Replicat abends problems.
`internalerror`	Collects data for all other types of internal Oracle Database errors.

To collect CRS, ASM, and cell data from the compute nodes

You can use the `tfactl diagcollect -cellnode <*comma delimited list of names*>|all command to collect cell data. If there is a cell related error on the compute node, use the tfactl diagcollect -srdc crsasmcell command to collect CRS, ASM, and cell data. The cell related errors handled by crsasmcell` are:

CRS-1604
CRS-1606
CRS-1613
CRS-1614
CRS-1615
CRS-1649

The cells must be configured within tfa to collect from the cells. To determine if the cell is configured, run:

# tfactl cell status

If the cells are not configured, run:

# tfactl cell configure

After configuring, you can collect from the cells.

For example:

```
# tfactl diagcollect -srdc crsasmcell
```

# tfactl diagcollect -srdc crsasmcell -cellnode mycell1,mycell2,mycell3

# tfactl diagcollect -srdc crsasmcell -cellnode all

# tfactl diagcollect -srdc dbperf -cellnode all

```
# tfactl diagcollect -cellnode all
```

For more information, see: