Incident Logs and Trace Files

This article lists all the files that can be collected by Oracle Support if you opt-in for incident logs and trace collection.

Note:

Oracle will create a service request (SR) against the infrastructure Customer Support Identifier (CSI) when an issue is detected and needs customer interaction to resolve.
The customer's Oracle Cloud Infrastructure tenancy admin email will be used as the CSI contact to create SR and attach logs to it. Ensure tenancy admin email is added as a CSI contact in My Oracle Support (MOS).

Oracle Trace File Analyze (TFA) Component Driven Logs Collections

The directories are generally assigned to a component and that component can then be used to guide TFA to the files it needs to collect, for example, requesting the Cluster Ready Services (CRS) component would tell TFA to look at directories mapped to the CRS component and find files that match the required collection time frame.

Note:

If have previously opted-in for incident log and trace file collection and decide to opt-out when Oracle Cloud operations run a log collection job, then the job will run its course and will not cancel. Future log collections won't happen until you opt-in again to the incident logs and trace file collection option.
TFA is shipped with scripts that run when a particular component is requested, for example, for CRS component, crscollect.pl will run a number of crsctl commands and gather the input. By default, TFA does not redact collected logs.

Component	Script	Files/Directories
`OS`: Operating system logs	`oscollect.pl`	`/var/log/messages` OSWatcher archive
`CRS`: Grid Infrastructure and cluster logs	`crscollect.pl`	`/etc/oracle` `GIHOME/crf/db/HOSTNAME1` `GIHOME/crs/log` `GIHOME/css/log` `GIHOME/cv/log` `GIHOME/evm/admin/log` `GIHOME/evm/admin/logger` `GIHOME/evm/log` `GIHOME/log/-/client` `GIHOME/log/HOSTNAME1` `GIHOME/log/HOSTNAME1/admin` `GIHOME/log/HOSTNAME1/client` `GIHOME/log/HOSTNAME1/crflogd` `GIHOME/log/HOSTNAME1/crfmond` `GIHOME/log/HOSTNAME1/crsd` `GIHOME/log/HOSTNAME1/cssd` `GIHOME/log/HOSTNAME1/ctssd` `GIHOME/log/HOSTNAME1/diskmon` `GIHOME/log/HOSTNAME1/evmd` `GIHOME/log/HOSTNAME1/gipcd` `GIHOME/log/HOSTNAME1/gnsd` `GIHOME/log/HOSTNAME1/gpnpd` `GIHOME/log/HOSTNAME1/mdnsd` `GIHOME/log/HOSTNAME1/ohasd` `GIHOME/log/HOSTNAME1/racg` `GIHOME/log/HOSTNAME1/srvm` `GIHOME/log/HOSTNAME1/xag` `GIHOME/log/diag/asmtool` `GIHOME/log/diag/clients` `GIHOME/log/procwatcher/PRW_SYS_HOSTNAME1` `GIHOME/network/log` `GIHOME/opmn/logs` `GIHOME/racg/log` `GIHOME/scheduler/log` `GIHOME/srvm/log` `GRIDBASE/crsdata/@global/cvu` `GRIDBASE/crsdata/HOSTNAME1/core` `GRIDBASE/crsdata/HOSTNAME1/crsconfig` `GRIDBASE/crsdata/HOSTNAME1/crsdiag` `GRIDBASE/crsdata/HOSTNAME1/cvu` `GRIDBASE/crsdata/HOSTNAME1/evm` `GRIDBASE/crsdata/HOSTNAME1/output` `GRIDBASE/crsdata/HOSTNAME1/ovmmwallets` `GRIDBASE/crsdata/HOSTNAME1/scripts` `GRIDBASE/crsdata/HOSTNAME1/trace` `GRIDBASE/diag/crs/-/crs/cdump` `GRIDBASE/diag/crs/HOSTNAME1/crs/cdump` `GRIDBASE/diag/crs/HOSTNAME1/crs/incident` `GRIDBASE/diag/crs/HOSTNAME1/crs/trace`
`Database`: Oracle Database logs	No database specific script - runs `opatch lsinventory` for the `ORACLE_HOME` the database runs from TFA will run `ipspack` based on the time range for certain database incidents.	`ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/cdump` `ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/trace` `ORACLE_BASE/diag/rdbms/<dbname>/<instance_name>/incident`

DCS Agent Logs

/opt/oracle/dcs/log/

Tooling-Related Grid Infrastructure/Database Logs

Grid Infrastructure: GI_HOME/cfgtoollogs
Database alertlog: /u02/app/oracle/diag/rdbms/*/*/alert*.log