SHOW INCIDENT

Purpose

Lists all of the incidents associated with the current ADR home. Includes both open and closed incidents.

Syntax and Description

show incident [-p "predicate_string"] [-mode {BASIC|BRIEF|DETAIL}]          [-orderby field1, field2, ... [ASC|DSC]]

Table 17-15 describes the flags for SHOW INCIDENT.

Table 17-15 Flags for SHOW INCIDENT command

Flag Description

Flag	Description
`-p` "`predicate_string`"	Use a predicate string to show only the incidents for which the predicate is true. The predicate string must be enclosed in double quotation marks. Table 17-16 lists the fields that can be used in the predicate string.
`-mode {BASIC\|BRIEF\|DETAIL}`	Choose an output mode for incidents. `BASIC` is the default. `BASIC` displays only basic incident information (the `INCIDENT_ID`, `PROBLEM_ID`, and `CREATE_TIME` fields). It does not display flood-controlled incidents. `BRIEF` displays all information related to the incidents, as given by the fields in Table 17-16. It includes flood-controlled incidents. `DETAIL` displays all information for the incidents (as with `BRIEF` mode) as well as information about incident dumps. It includes flood-controlled incidents.
`-orderby` `field1,` `field2, ...` [`ASC\|DSC`]	Show results sorted by field in the given order, as well as in ascending (`ASC`) and descending order (`DSC`). By default, results are shown in ascending order.

-p "predicate_string"

Use a predicate string to show only the incidents for which the predicate is true. The predicate string must be enclosed in double quotation marks.

Table 17-16 lists the fields that can be used in the predicate string.

-mode {BASIC|BRIEF|DETAIL}

Choose an output mode for incidents. BASIC is the default.

BASIC displays only basic incident information (the INCIDENT_ID, PROBLEM_ID, and CREATE_TIME fields). It does not display flood-controlled incidents.
BRIEF displays all information related to the incidents, as given by the fields in Table 17-16. It includes flood-controlled incidents.
DETAIL displays all information for the incidents (as with BRIEF mode) as well as information about incident dumps. It includes flood-controlled incidents.

-orderby field1, field2, ... [ASC|DSC]

Show results sorted by field in the given order, as well as in ascending (ASC) and descending order (DSC). By default, results are shown in ascending order.

Table 17-16 Incident Fields for SHOW INCIDENT

Field	Type	Description
`INCIDENT_ID`	`number`	ID of the incident
`PROBLEM_ID`	`number`	ID of the problem to which the incident belongs
`CREATE_TIME`	`timestamp`	Time when the incident was created
`CLOSE_TIME`	`timestamp`	Time when the incident was closed
`STATUS`	`number`	Status of this incident
`FLAGS`	`number`	Flags for internal use
`FLOOD_CONTROLLED`	`number` (decoded to a text status by ADRCI)	Encodes the flood control status for the incident
`ERROR_FACILITY`	`text(10)`	Error facility for the error that caused the incident
`ERROR_NUMBER`	`number`	Error number for the error that caused the incident
`ERROR_ARG1`	`text(64)`	First argument for the error that caused the incident Error arguments provide additional information about the error, such as the code location that issued the error.
`ERROR_ARG2`	`text(64)`	Second argument for the error that caused the incident
`ERROR_ARG3`	`text(64)`	Third argument for the error that caused the incident
`ERROR_ARG4`	`text(64)`	Fourth argument for the error that caused the incident
`ERROR_ARG5`	`text(64)`	Fifth argument for the error that caused the incident
`ERROR_ARG6`	`text(64)`	Sixth argument for the error that caused the incident
`ERROR_ARG7`	`text(64)`	Seventh argument for the error that caused the incident
`ERROR_ARG8`	`text(64)`	Eighth argument for the error that caused the incident
`SIGNALLING_COMPONENT`	`text(64)`	Component that signaled the error that caused the incident
`SIGNALLING_SUBCOMPONENT`	`text(64)`	Subcomponent that signaled the error that caused the incident
`SUSPECT_COMPONENT`	`text(64)`	Component that has been automatically identified as possibly causing the incident
`SUSPECT_SUBCOMPONENT`	`text(64)`	Subcomponent that has been automatically identified as possibly causing the incident
`ECID`	`text(64)`	Execution Context ID
`IMPACT`	`number`	Encodes the impact of the incident
`ERROR_ARG9`	`text(64)`	Ninth argument for the error that caused the incident
`ERROR_ARG10`	`text(64)`	Tenth argument for the error that caused the incident
`ERROR_ARG11`	`text(64)`	Eleventh argument for the error that caused the incident
`ERROR_ARG12`	`text(64)`	Twelfth argument for the error that caused the incident

Examples

This example shows all incidents for this ADR home:

show incident

Output:

ADR Home = /u01/app/oracle/log/diag/rdbms/emdb/emdb:
*************************************************************************
INCIDENT_ID          PROBLEM_KEY                                  CREATE_TIME
-------------------- -------------------------------------------- ----------------------------
3808                 ORA 603                                      2010-06-18 21:35:49.322161 -07:00
3807                 ORA 600 [4137]                               2010-06-18 21:35:47.862114 -07:00
3806                 ORA 603                                      2010-06-18 21:35:26.666485 -07:00
3805                 ORA 600 [4136]                               2010-06-18 21:35:25.012579 -07:00
3804                 ORA 1578                                     2010-06-18 21:35:08.483156 -07:00
3713                 ORA 600 [4136]                               2010-06-18 21:35:44.754442 -07:00
3633                 ORA 600 [4136]                               2010-06-18 21:35:35.776151 -07:00
7 rows fetched

This example shows the detail view for incident 3805:

adrci> show incident -mode DETAIL -p "incident_id=3805"

Output:

ADR Home = /u01/app/oracle/log/diag/rdbms/emdb/emdb:
*************************************************************************
 
**********************************************************
INCIDENT INFO RECORD 1
**********************************************************
   INCIDENT_ID                   3805
   STATUS                        closed
   CREATE_TIME                   2010-06-18 21:35:25.012579 -07:00
   PROBLEM_ID                    2
   CLOSE_TIME                    2010-06-18 22:26:54.143537 -07:00
   FLOOD_CONTROLLED              none
   ERROR_FACILITY                ORA
   ERROR_NUMBER                  600
   ERROR_ARG1                    4136
   ERROR_ARG2                    2
   ERROR_ARG3                    18.0.628
   ERROR_ARG4                    <NULL>
   ERROR_ARG5                    <NULL>
   ERROR_ARG6                    <NULL>
   ERROR_ARG7                    <NULL>
   ERROR_ARG8                    <NULL>
   SIGNALLING_COMPONENT          <NULL>
   SIGNALLING_SUBCOMPONENT       <NULL>
   SUSPECT_COMPONENT             <NULL>
   SUSPECT_SUBCOMPONENT          <NULL>
   ECID                          <NULL>
   IMPACTS                       0
   PROBLEM_KEY                   ORA 600 [4136]
   FIRST_INCIDENT                3805
   FIRSTINC_TIME                 2010-06-18 21:35:25.012579 -07:00
   LAST_INCIDENT                 3713
   LASTINC_TIME                  2010-06-18 21:35:44.754442 -07:00
   IMPACT1                       0
   IMPACT2                       0
   IMPACT3                       0
   IMPACT4                       0
   KEY_NAME                      Client ProcId
   KEY_VALUE                     oracle@dbhost1 (TNS V1-V3).23716_3083142848
   KEY_NAME                      SID
   KEY_VALUE                     127.52237
   KEY_NAME                      ProcId
   KEY_VALUE                     23.90
   KEY_NAME                      PQ
   KEY_VALUE                     (0, 1182227717)
   OWNER_ID                      1
   INCIDENT_FILE                 /.../emdb/emdb/incident/incdir_3805/emdb_ora_23716_i3805.trc
   OWNER_ID                      1
   INCIDENT_FILE                 /.../emdb/emdb/trace/emdb_ora_23716.trc
   OWNER_ID                      1
   INCIDENT_FILE                 /.../emdb/emdb/incident/incdir_3805/emdb_m000_23767_i3805_a.trc
1 rows fetched