16 ADRCI: ADR Command Interpreter

Using ADRCI in Interactive Mode

Interactive mode prompts you to enter individual commands one at a time. Each entered command is followed by its output.

To use ADRCI in interactive mode:

1. Ensure that the ORACLE_HOME and PATH environment variables are set properly.

   On the Windows platform, these environment variables are set in the Windows registry automatically upon installation. On other platforms, you must set and check environment variables with operating system commands.

   The PATH environment variable must include ORACLE_HOME/bin.

2. Enter the following command at the operating system command prompt:

   ADRCI
   

   The utility starts and displays the following prompt:

   adrci>
   

3. Enter ADRCI commands, following each with the Enter key.

4. Enter one of the following commands to exit ADRCI:

   EXIT
   QUIT
   

Getting Help

With the ADRCI help system, you can:

• View a list of ADR commands.

• View help for an individual command.

• View a list of ADRCI command line options.

To view a list of ADRCI commands:

1. Start ADRCI in interactive mode.

   See "Using ADRCI in Interactive Mode" for instructions.

2. At the ADRCI prompt, enter the following command:

   HELP
   

To get help for a specific ADRCI command:

1. Start ADRCI in interactive mode.

   See "Using ADRCI in Interactive Mode" for instructions.

2. At the ADRCI prompt, enter the following command:

   HELP command
   

   For example, to get help on the SHOW TRACEFILE command, enter the following:

   HELP SHOW TRACEFILE
   

To view a list of command line options:

• Enter the following command at the operating system command prompt:

  ADRCI -HELP
  

  The utility displays output similar to the following:

  Syntax:
     adrci [-help] [script=script_filename] [exec="command [;command;...]"]
   
  Options      Description                     (Default)
  -----------------------------------------------------------------
  script       script file name                (None)
  help         help on the command options     (None)
  exec         exec a set of commands          (None)
  -----------------------------------------------------------------
  

Using ADRCI in Batch Mode

Batch mode enables you to run a series of ADRCI commands at once, without being prompted for input. To use batch mode, you add a command line parameter to the ADRCI command when you start ADRCI. Batch mode enables you to include ADRCI commands in shell scripts or Windows batch files. Like interactive mode, the ORACLE_HOME and PATH environment variables must be set before starting ADRCI.

The following command line parameters are available for batch operation:

To submit ADRCI commands on the command line:

• Enter the following command at the operating system command prompt:

  ADRCI EXEC="COMMAND[; COMMAND]..."
  

  For example, to run the SHOW HOMES command in batch mode, enter the following command at the operating system command prompt:

  ADRCI EXEC="SHOW HOMES"
  

  To run the SHOW HOMES command followed by the SHOW INCIDENT command, enter the following:

  ADRCI EXEC="SHOW HOMES; SHOW INCIDENT"
  

To run ADRCI scripts:

• Enter the following command at the operating system command prompt:

• ADRCI SCRIPT=SCRIPT_FILE_NAME
  

  For example, to run a script file named adrci_script.txt, enter the following command at the operating system command prompt:

  ADRCI SCRIPT=adrci_script.txt
  

  A script file contains a series of commands separated by semicolons (;) or line breaks, such as:

• SET HOMEPATH diag/rdbms/orcl/orcl; SHOW ALERT -term
  

About Packaging Incidents

Packaging incidents is a three-step process:

Step 1—Create a logical incident package.

The incident package (package) is denoted as logical because it exists only as metadata in the automatic diagnostic repository (ADR). It has no content until you generate a physical package from the logical package. The logical package is assigned a package number, and you refer to it by that number in subsequent commands.

You can create the logical package as an empty package, or as a package based on an incident number, a problem number, a problem key, or a time interval. If you create the package as an empty package, you can add diagnostic information to it in step 2.

Creating a package based on an incident means including diagnostic data—dumps, health monitor reports, and so on—for that incident. Creating a package based on a problem number or problem key means including in the package diagnostic data for incidents that reference that problem number or problem key. Creating a package based on a time interval means including diagnostic data on incidents that occurred in the time interval.

Step 2—Add diagnostic information to the incident package

If you created a logical package based on an incident number, a problem number, a problem key, or a time interval, this step is optional. You can add additional incidents to the package or you can add any file within the ADR to the package. If you created an empty package, you must use ADRCI commands to add incidents or files to the package.

Step 3—Generate the physical incident package

When you submit the command to generate the physical package, ADRCI gathers all required diagnostic files and adds them to a zip file in a designated directory. You can generate a complete zip file or an incremental zip file. An incremental file contains all the diagnostic files that were added or changed since the last zip file was created for the same logical package. You can create incremental files only after you create a complete file, and you can create as many incremental files as you want. Each zip file is assigned a sequence number so that the files can be analyzed in the correct order.

Zip files are named according to the following scheme:

packageName_mode_sequence.zip

where:

• packageName consists of a portion of the problem key followed by a timestamp

• mode is either 'COM' or 'INC', for complete or incremental

• sequence is an integer

For example, if you generate a complete zip file for a logical package that was created on September 6, 2006 at 4:53 p.m., and then generate an incremental zip file for the same logical package, you would create files with names similar to the following:

ORA603_20060906165316_COM_1.zip
ORA603_20060906165316_INC_2.zip

Creating Incident Packages

The following sections present the ADRCI commands that you use to create a logical incident package (package) and generate a physical package:

• Creating a Logical Incident Package

• Adding Diagnostic Information to a Logical Incident Package

• Generating a Physical Incident Package

IPS CREATE PACKAGE

IPS CREATE PACKAGE PROBLEM problem_ID

IPS CREATE PACKAGE PROBLEMKEY "problem_key"

IPS CREATE PACKAGE SECONDS sec

IPS CREATE PACKAGE TIME 'start_time' TO 'end_time'

IPS CREATE PACKAGE TIME '2009-07-24 00:00:00 -07:00' to '2009-07-30 23.59.59 -07:00'

CREATE REPORT

Purpose

Creates a report for the specified report type and run ID and stores the report in the ADR. Currently, only the hm_run (Health Monitor) report type is supported.

Syntax and Description

create report report_type run_name

report_type must be hm_run. run_name is a Health Monitor run name. Obtain run names with the SHOW HM_RUN command.

If the report already exists it is overwritten. Use the SHOW REPORT command to view the report.

Example

This example creates a report for the Health Monitor run with run name hm_run_1421:

create report hm_run hm_run_1421

ECHO

Purpose

Prints the input string. You can use this command to print custom text from ADRCI scripts.

Syntax and Description

echo quoted_string

The string must be enclosed in single or double quotes.

This command does not require an ADR home to be set before you can use it.

Example

These examples print the string "Hello, world!":

echo "Hello, world!"

echo 'Hello, world!'

EXIT

Purpose

Exits the ADRCI utility.

Syntax and Description

exit

EXIT is a synonym for the QUIT command.

This command does not require an ADR home to be set before you can use it.

HOST

Purpose

Execute operating system commands without leaving ADRCI.

Syntax and Description

host ["host_command_string"]

Use host by itself to enter an operating system shell, which allows you to enter multiple operating system commands. Enter EXIT to leave the shell and return to ADRCI.

You can also specify the command on the same line (host_command_string) enclosed in double quotes.

This command does not require an ADR home to be set before you can use it.

Examples

host

host "ls -l *.pl"

IPS

Purpose

Invokes the Incident Packaging Service (IPS) command set. The IPS command provides options for creating logical incident packages (packages), adding diagnostic data to packages, and generating physical packages for transmission to Oracle Support.

The IPS command set contains the following commands:

ips add file <ADR_HOME>/trace/orcl_ora_13579.trc package 12

ips add file <ADR_BASE>/diag/rdbms/orcl/orcl/trace/orcl_ora_13579.trc package 12

ips add {incident inc_id | problem prob_id | problemkey pr_key | 
     seconds secs | time start_time to end_time}         
     package pkg_id

ips add incident 22 package 12

ips add problem 6 package 2

ips add seconds 60 package 5

ips add  time '2009-05-01 10:00:00.00 -07:00' to '2009-05-01 23:00:00.00 -07:00'

ips add file file_name package pkg_id

ips add file <ADR_HOME>/trace/orcl_ora_13579.trc package 12

ips add new incidents package package_id

ips add new incidents package 12

ips copy in file filename [to new_name][overwrite] package pkgid
     [incident incid]

ips copy in file /home/nick/trace/orcl_ora_13579.trc to <ADR_HOME>/trace/orcl_ora_13579.trc package 2 incident 4

ips copy out file source to target [overwrite]

ips copy out file <ADR_HOME>/trace/orcl_ora_13579.trc to /home/nick/trace/orcl_ora_13579.trc

ips create package {incident inc_id | problem prob_id |
     problemkey prob_key | seconds secs | time start_time to end_time} 
     [correlate {basic |typical | all}]

ips create package

Created package 5 without any contents, correlation level typical

ips create package time '2009-05-01 10:00:00.00 -07:00' to '2009-05-01 23:00:00.00 -07:00'

Created package 6 based on time range 2009-05-01 10:00:00.00 -07:00 to 2009-05-01 23:00:00.00 -07:00, correlation level typical

ips create package problem 3

Created package 7 based on problem id 3, correlation level typical

ips delete package pkg_id

ips delete package 12

ips finalize package pkg_id

ips finalize package 12

ips generate package package_id [in path] [complete | incremental]

ips generate package 12 in /home/steve

ips generate package 14 incremental

ips get manifest from file filename

ips get manifest from file /home/steve/ORA603_20060906165316_COM_1.zip

ips get metadata {from file filename | from adr}

ips get metadata from file /home/steve/ORA603_20060906165316_COM_1.zip

set base /scratch/oracle/package1
ips get metadata from adr

ips pack [incident inc_id | problem prob_id | problemkey prob_key |
     seconds secs | time start_time to end_time]
     [correlate {basic |typical | all}] [in path]

ips pack

ips pack incident 861

ips pack seconds 60 correlate all

ips remove {incident inc_id | problem prob_id | problemkey prob_key} 
     package pkg_id

ips remove incident 22 package 12

ips remove file file_name package pkg_id

ips remove file <ADR_HOME>/trace/orcl_ora_13579.trc package 12
Removed file <ADR_HOME>/trace/orcl_ora_13579.trc from package 12
ips show files package 12

.
.
.
FILE_ID                4
FILE_LOCATION          <ADR_HOME>/trace
FILE_NAME              orcl_ora_13579.trc
LAST_SEQUENCE          0
EXCLUDE                Explicitly excluded
.
.
.

ips set configuration parameter_id value

ips set configuration 3 10

ips show configuration [parameter_id]

ips show configuration

PARAMETER INFORMATION:
   PARAMETER_ID           1
   NAME                   CUTOFF_TIME
   DESCRIPTION            Maximum age for incident to be considered for inclusion
   UNIT                   Days
   VALUE                  90
   DEFAULT_VALUE          90
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0
 
PARAMETER INFORMATION:
   PARAMETER_ID           2
   NAME                   NUM_EARLY_INCIDENTS
   DESCRIPTION            How many incidents to get in the early part of the range
   UNIT                   Number
   VALUE                  3
   DEFAULT_VALUE          3
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0
 
PARAMETER INFORMATION:
   PARAMETER_ID           3
   NAME                   NUM_LATE_INCIDENTS
   DESCRIPTION            How many incidents to get in the late part of the range
   UNIT                   Number
   VALUE                  3
   DEFAULT_VALUE          3
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0
 
PARAMETER INFORMATION:
   PARAMETER_ID           4
   NAME                   INCIDENT_TIME_WINDOW
   DESCRIPTION            Incidents this close to each other are correlated
   UNIT                   Minutes
   VALUE                  5
   DEFAULT_VALUE          5
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0
 
PARAMETER INFORMATION:
   PARAMETER_ID           5
   NAME                   PACKAGE_TIME_WINDOW
   DESCRIPTION            Time window for content inclusion is from x hours...
   UNIT                   Hours
   VALUE                  24
   DEFAULT_VALUE          24
   MINIMUM                1
   MAXIMUM                4294967295
   FLAGS                  0
 
PARAMETER INFORMATION:
   PARAMETER_ID           6
   NAME                   DEFAULT_CORRELATION_LEVEL
   DESCRIPTION            Default correlation level for packages
   UNIT                   Number
   VALUE                  2
   DEFAULT_VALUE          2
   MINIMUM                1
   MAXIMUM                4
   FLAGS                  0

ips show configuration 3

ips show files package pkg_id

ips show files package 1

FILE_ID                1
   FILE_LOCATION          <ADR_HOME>/incpkg/pkg_1
   FILE_NAME              ocm_guid.txt
   LAST_SEQUENCE          0
   EXCLUDE                Included
 
   FILE_ID                2
   FILE_LOCATION          <ADR_HOME>/incident/incdir_4985
   FILE_NAME              orcl_ora_22081_i4985.trc
   LAST_SEQUENCE          0
   EXCLUDE                Included
 
   FILE_ID                3
   FILE_LOCATION          <ADR_HOME>/incident/incdir_4985
   FILE_NAME              orcl_ora_22081_i4985.trm
   LAST_SEQUENCE          0
   EXCLUDE                Included
 
   FILE_ID                4
   FILE_LOCATION          <ADR_HOME>/trace
   FILE_NAME              orcl_ora_22081.trc
   LAST_SEQUENCE          0
   EXCLUDE                Included
 
   FILE_ID                5
   FILE_LOCATION          <ADR_HOME>/trace
   FILE_NAME              orcl_ora_22081.trm
   LAST_SEQUENCE          0
   EXCLUDE                Included

ips show incidents package pkg_id

ips show incidents package 1

MAIN INCIDENTS FOR PACKAGE 1:
   INCIDENT_ID            4985
   PROBLEM_ID             1
   EXCLUDE                Included
 
CORRELATED INCIDENTS FOR PACKAGE 1:

ips unpack file file_name [into path]

ips unpack file /tmp/ORA603_20060906165316_COM_1.zip into /tmp/newadr

PURGE

Purpose

Purges diagnostic data in the current ADR home, according to current purging policies. Only ADR contents that are due to be purged are purged.

Diagnostic data in the ADR has a default lifecycle. For example, information about incidents and problems is subject to purging after one year, whereas the associated dump files (dumps) are subject to purging after only 30 days.

Some Oracle products, such Oracle Database, automatically purge diagnostic data at the end of its lifecycle. Other products and components require you to purge diagnostic data manually with this command. You can also use this command to purge data that is due to be automatically purged.

The SHOW CONTROL command displays the default purging policies for short-lived ADR contents and long-lived ADR contents.

Syntax and Description

purge [-i {id | start_id end_id} | 
  -age mins [-type {ALERT|INCIDENT|TRACE|CDUMP|HM}]]

Table 16-9 describes the flags for PURGE.

Examples

This example purges all diagnostic data in the current ADR home based on the default purging policies:

purge

This example purges all diagnostic data for all incidents between 123 and 456:

purge -i 123 456

This example purges all incident data from the last hour:

purge -age 60 -type incident

QUIT

See "EXIT"

RUN

Purpose

Runs an ADRCI script.

Syntax and Description

run script_name

@ script_name

@@ script_name

script_name is the file containing the ADRCI commands to execute. ADRCI looks for the script in the current directory unless a full pathname is supplied. If the file name is given without a file extension, ADRCI uses the default extension ".adi".

The run and @ commands are synonyms. The @@ command is similar to run and @ except that when used inside a script, @@ uses the path of the calling script to locate script_name, rather than the current directory.

This command does not require an ADR home to be set before you can use it.

Example

run my_script

@my_script

SET BASE

Purpose

Sets the ADR base to use in the current ADRCI session.

Syntax and Description

set base base_str

base_str is a full path to a directory. The format for base_str depends on the operating system. If there are valid ADR homes under the base directory, these homes are added to the homepath of the current ADRCI session.

This command does not require an ADR home to be set before you can use it.

Example

set base /u01/app/oracle

SET BROWSER

Purpose

Sets the default browser for displaying reports.

Syntax and Description

set browser browser_program

browser_program is the browser program name (it is assumed the browser can be started from the current ADR working directory). If no browser is set, ADRCI will display reports to the terminal or spool file.

This command does not require an ADR home to be set before you can use it.

Example

set browser mozilla

SET CONTROL

Purpose

Sets purging policies for ADR contents.

Syntax and Description

set control (purge_policy = value, ...)

purge_policy is either SHORTP_POLICY or LONGP_POLICY. See "SHOW CONTROL" for more information.

value is the number of hours after which the ADR contents become eligible for purging.

This command works with a single ADR home only.

Example

set control (SHORTP_POLICY = 360)

SET ECHO

Purpose

Turns command output on or off. This command only affects output being displayed in a script or using the spool mode.

Syntax and Description

set echo on|off

This command does not require an ADR home to be set before you can use it.

Example

set echo off

SET EDITOR

Purpose

Sets the editor for displaying the alert log and the contents of trace files.

Syntax and Description

set editor editor_program

editor_program is the editor program name. If no editor is set, ADRCI uses the editor specified by the operating system environment variable $EDITOR. If $EDITOR is not set, ADRCI uses vi as the default editor.

This command does not require an ADR home to be set before you can use it.

Example

set editor xemacs

SET HOMEPATH

Purpose

Makes one or more ADR homes current. Many ADR commands work with the current ADR homes only.

Syntax and Description

set homepath homepath_str1 homepath_str2 ...

The homepath_strn strings are the paths of the ADR homes relative to the current ADR base. The "diag" in the directory name can be omitted. If the specified path contains multiple ADR homes, all of the homes are added to the homepath.

If a desired new ADR home is not within the current ADR base, use SET BASE to set a new ADR base and then use SET HOMEPATH.

This command does not require an ADR home to be set before you can use it.

Example

set homepath diag/rdbms/orcldw/orcldw1  diag/rdbms/orcldw/orcldw2

SET TERMOUT

Purpose

Turns output to the terminal on or off.

Syntax and Description

set termout on|off

This setting is independent of spooling. That is, the output can be directed to both terminal and a file at the same time.

This command does not require an ADR home to be set before you can use it.

Example

set termout on

SHOW ALERT

Purpose

Shows the contents of the alert log in the default editor.

Syntax and Description

show alert [-p predicate_string] [-tail [num] [-f]] [-term]
  [-file alert_file_name]

Except when using the -term flag, this command works with only a single current ADR home. If more than one ADR home is set, ADRCI prompts you to choose the ADR home to use.

Example

This example shows all alert messages for the current ADR home in the default editor:

show alert

This example shows all alert messages for the current ADR home and directs the output to the terminal instead of the default editor:

show alert -term

This example shows all alert messages for the current ADR home with message text describing an incident:

show alert -p "message_text like '%incident%'"

This example shows the last twenty alert messages, and then keeps the alert log open, displaying new alert log entries as they arrive:

show alert -tail 20 -f

This example shows all alert messages for a single ADR home in the default editor when multiple ADR homes have been set:

show alert

Choose the alert log from the following homes to view:

1: diag/tnslsnr/dbhost1/listener
2: diag/asm/+asm/+ASM
3: diag/rdbms/orcl/orcl
4: diag/clients/user_oracle/host_9999999999_11
Q: to quit

Please select option:
3

SHOW BASE

Purpose

Shows the current ADR base.

Syntax and Description

show base [-product product_name]

Optionally, you can show the product's ADR base location for a specific product. The products currently supported are "CLIENT" and "ADRCI".

This command does not require an ADR home to be set before you can use it.

Example

This example shows the current ADR base:

show base

Output:

ADR base is "/u01/app/oracle"

This example shows the current ADR base for Oracle Database clients:

show base -product client

SHOW CONTROL

Purpose

Displays information about the Automatic Diagnostic Repository (ADR), including the purging policy.

Syntax and Description

show control

Displays various attributes of the ADR, including the following purging policy attributes:

SHOW HM_RUN

Purpose

Shows all information for Health Monitor runs.

Syntax and Description

show hm_run [-p predicate_string]

[-p predicate_string] is a SQL-like predicate specifying the field names to select. Table 16-12 displays the list of field names you can use.

Example

This example displays data for all Health Monitor runs:

show hm_run

This example displays data for the Health Monitor run with ID 123:

show hm_run -p "run_id=123"

SHOW HOMEPATH

Purpose

Identical to the SHOW HOMES command.

Syntax and Description

show homepath | show homes | show home

This command does not require an ADR home to be set before you can use it.

Example

show homepath

Output:

ADR Homes:
diag/tnslsnr/dbhost1/listener
diag/asm/+asm/+ASM
diag/rdbms/orcl/orcl
diag/clients/user_oracle/host_9999999999_11

SHOW HOMES

Purpose

Show the ADR homes in the current ADRCI session.

Syntax and Description

show homes | show home | show homepath

This command does not require an ADR home to be set before you can use it.

Example

show homes

Output:

ADR Homes:
diag/tnslsnr/dbhost1/listener
diag/asm/+asm/+ASM
diag/rdbms/orcl/orcl
diag/clients/user_oracle/host_9999999999_11

SHOW INCDIR

Purpose

Shows trace files for the specified incident.

Syntax and Description

show incdir [id | id_low id_high]

You can provide a single incident ID (id) or a range of incidents (id_low to id_high). If no incident ID is given, trace files for all incidents are listed.

Example

This example shows all trace files for all incidents:

show incdir

Output:

ADR Home = /u01/app/oracle/log/diag/rdbms/emdb/emdb:
*************************************************************************
diag/rdbms/emdb/emdb/incident/incdir_3801/emdb_ora_23604_i3801.trc
diag/rdbms/emdb/emdb/incident/incdir_3801/emdb_m000_23649_i3801_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3802/emdb_ora_23604_i3802.trc
diag/rdbms/emdb/emdb/incident/incdir_3803/emdb_ora_23604_i3803.trc
diag/rdbms/emdb/emdb/incident/incdir_3804/emdb_ora_23604_i3804.trc
diag/rdbms/emdb/emdb/incident/incdir_3805/emdb_ora_23716_i3805.trc
diag/rdbms/emdb/emdb/incident/incdir_3805/emdb_m000_23767_i3805_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3806/emdb_ora_23716_i3806.trc
diag/rdbms/emdb/emdb/incident/incdir_3633/emdb_pmon_28970_i3633.trc
diag/rdbms/emdb/emdb/incident/incdir_3633/emdb_m000_23778_i3633_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3713/emdb_smon_28994_i3713.trc
diag/rdbms/emdb/emdb/incident/incdir_3713/emdb_m000_23797_i3713_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3807/emdb_ora_23783_i3807.trc
diag/rdbms/emdb/emdb/incident/incdir_3807/emdb_m000_23803_i3807_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3808/emdb_ora_23783_i3808.trc

This example shows all trace files for incident 3713

show incdir 3713

Output:

ADR Home = /u01/app/oracle/log/diag/rdbms/emdb/emdb:
*************************************************************************
diag/rdbms/emdb/emdb/incident/incdir_3713/emdb_smon_28994_i3713.trc
diag/rdbms/emdb/emdb/incident/incdir_3713/emdb_m000_23797_i3713_a.trc

This example shows all tracefiles for incidents between 3801 and 3804:

show incdir 3801 3804

Output:

ADR Home = /u01/app/oracle/log/diag/rdbms/emdb/emdb:
*************************************************************************
diag/rdbms/emdb/emdb/incident/incdir_3801/emdb_ora_23604_i3801.trc
diag/rdbms/emdb/emdb/incident/incdir_3801/emdb_m000_23649_i3801_a.trc
diag/rdbms/emdb/emdb/incident/incdir_3802/emdb_ora_23604_i3802.trc
diag/rdbms/emdb/emdb/incident/incdir_3803/emdb_ora_23604_i3803.trc
diag/rdbms/emdb/emdb/incident/incdir_3804/emdb_ora_23604_i3804.trc

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 16-13 describes the flags for SHOW 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                                      2009-06-18 21:35:49.322161 -07:00
3807                 ORA 600 [4137]                               2009-06-18 21:35:47.862114 -07:00
3806                 ORA 603                                      2009-06-18 21:35:26.666485 -07:00
3805                 ORA 600 [4136]                               2009-06-18 21:35:25.012579 -07:00
3804                 ORA 1578                                     2009-06-18 21:35:08.483156 -07:00
3713                 ORA 600 [4136]                               2009-06-18 21:35:44.754442 -07:00
3633                 ORA 600 [4136]                               2009-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                   2009-06-18 21:35:25.012579 -07:00
   PROBLEM_ID                    2
   CLOSE_TIME                    2009-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                 2009-06-18 21:35:25.012579 -07:00
   LAST_INCIDENT                 3713
   LASTINC_TIME                  2009-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

SHOW PROBLEM

Purpose

Show problem information for the current ADR home.

Syntax and Description

show problem [-p predicate_string] [-last num | -all]
    [-orderby field1, field2, ... [ASC|DSC]]

Table 16-15 describes the flags for SHOW PROBLEM.

Example

This example lists all the problems in the current ADR home:

show problem -all

This example shows the problem with ID 4:

show problem -p "problem_id=4"

SHOW REPORT

Purpose

Show a report for the specified report type and run name. Currently, only the hm_run (Health Monitor) report type is supported, and only in XML formatting. To view HTML-formatted Health Monitor reports, use Oracle Enterprise Manager or the DBMS_HM PL/SQL package. See Oracle Database Administrator's Guide for more information.

Syntax and Description

SHOW REPORT report_type run_name

report_type must be hm_run. run_name is the Health Monitor run name from which you created the report. You must first create the report using the CREATE REPORT command.

This command does not require an ADR home to be set before you can use it.

Example

show report hm_run hm_run_1421

SHOW TRACEFILE

Purpose

List trace files.

Syntax and Description

show tracefile [file1 file2 ...] [-rt | -t]
  [-i inc1 inc2 ...] [-path path1 path2 ...] 

This command searches for one or more files under the trace directory and all incident directories of the current ADR homes, unless the -i or -path flags are given.

This command does not require an ADR home to be set unless using the -i option.

Table 16-18 describes the arguments of SHOW TRACEFILE.

Example

This example shows all the trace files under the current ADR home:

show tracefile

This example shows all the MMON trace files, sorted by timestamp in reverse order:

show tracefile %mmon% -rt

This example shows all trace files for incidents 1 and 4, under the path /home/steve/temp:

show tracefile -i 1 4 -path /home/steve/temp

SPOOL

Purpose

Directs ADRCI output to a file.

Syntax and Description

SPOOL filename [[APPEND] | [OFF]]

filename is the file name where the output is to be directed. If a full pathname is not given, the file is created in the current ADRCI working directory. If no file extension is given, the default extension ".ado" is used. APPEND causes the output to be appended to the end of the file. Otherwise, the file is overwritten. Use OFF to turn off spooling.

This command does not require an ADR home to be set before you can use it.

Example

spool myfile

spool myfile.ado append

spool off

spool