Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 E-mail Us
 Oracle Articles
New Oracle Articles

 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog

 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Oracle Support

 SQL Tuning

 Oracle UNIX
 Oracle Linux
 Remote s
 Remote plans
 Application Server

 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S


 Consulting Staff
 Consulting Prices
 Help Wanted!


 Oracle Posters
 Oracle Books

 Oracle Scripts

Don Burleson Blog 









Create an Incident Package with ADRCI and IPS Commands

Oracle 11g New Features Tips by Donald BurlesonJune 29, 2015

Oracle 11g Incident Packaging steps

Also see my ADRCI command tips!

From the command prompt, the Automatic Diagnostic Repository (ADR) command interface utility is entered by typing "adrci" from the OS prompt:


ADRCI: Release - Beta on Thu Nov 15 22:21:42 2015 

Copyright (c) 1982, 2015, Oracle.  All rights reserved. 

ADR base = "c:\oracle\11g"

ADRCI commands are based on one or more base directories known as ADR homes.  Before using the ADRCI commands, it is helpful to set an active ADR home to work with a single instance.  The available homes can be seen by typing:

adrci> show homes
ADR Homes:
diag\clients\user_varun jain\host_1475088825_11

The output above shows that there are several available home directories on which ADR can operate.  If a DBA wants to only access diagnostic data from one of the available homes, the active ADR home should be set appropriately.  The active home can be set using the set homepath command:

adrci> set homepath diag\rdbms\ora11gr1\ora11gr1
adrci> show homes
ADR Homes:

The output demonstrates that after setting the active ADR home, only the active home displays. 

Creating Incident Packages

Once the incident or problem that should be included in the incident package is identified, two options remain.  The DBA can then either create a physical package immediately or create a logical package to verify the package contents and customize the package to include the files that are needed. 

Incidents in the ADR home can be viewed by using the 'show incident? command:

adrci> set homepath diag\rdbms\ora11gr1\ora11gr1
adrci> show incident 

ADR Home = c:\oracle\11g\diag\rdbms\ora11gr1\ora11gr1:


INCIDENT_ID          PROBLEM_KEY                              CREATE_TIME
-------------------- -----------------------------------------------------------------
5138                 ORA 7445 [qmxarFindPartition()+15]       2015-11-15 22:53:58.343000 -08:00
5137                 ORA 600 [qmxarElemAt2]                   2015-11-15 22:53:40.859000 -08:00

2 rows fetched


NOTE: If an active ADR home has not been set, this will include incidents from all homes listed in the 'show homes? command.

If the problem reported has not been captured as an incident in ADR, then it is best to create a logical package and add the necessary files before generating the zip file.

If the physical package needs to be generated immediately based on an incident, problem, problem key, or time interval without the opportunity to customize the logical package, the ?ips pack? command can be used as follows:

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

For example:

adrci> ips pack incident 5137 in c:\tmp
Generated package 5 in file C:\tmp\, mode complete

To create the logical incident package, use a variation of the ?ips create package? command:

ips create package {incident incident_id|problem problem_id|problemkey problem_key|seconds secs|time
to end_time} [correlate basic|typical|all]

It is possible to create a logical package based on incident number such as:

adrci> ips create package incident 5138
Created package 1 based on incident id 5138, correlation level typical

To create an incident package based on a problem, it is necessary to find the problem_id by using the 'show incident? command:

show incident [-p predicate_string] [-mode {BASIC|BRIEF|DETAIL}] 

For example:

adrci> show incident -mode brief -p "incident_id=5137" 

ADR Home = c:\oracle\11g\diag\rdbms\ora11gr1\ora11gr1:
   INCIDENT_ID                   5137
   STATUS                        ready
   CREATE_TIME                   2015-11-15 22:53:40.859000 -08:00
   PROBLEM_ID                    1
   CLOSE_TIME                    <NULL>
   FLOOD_CONTROLLED              none
   ERROR_FACILITY                ORA
   ERROR_NUMBER                  600
   ERROR_ARG1                    qmxarElemAt2
   ERROR_ARG2                    144
   ERROR_ARG3                    <NULL>
   ERROR_ARG4                    <NULL>
   ERROR_ARG5                    <NULL>
   ERROR_ARG6                    <NULL>
   ERROR_ARG7                    <NULL>
   ERROR_ARG8                    <NULL>
   ECID                          <NULL>
   IMPACTS                       0

1 rows fetched


This shows that incident 5137 has been assigned the problem id of 1.  Using this problem id, creates the package for this problem:

adrci> ips create package problem 1
Created package 2 based on problem id 1, correlation level typical

To create the package based on the problem key, use the problem_key value displayed in the show incident output.  For example:

adrci> ips create package problemkey "ORA 7445 [qmxarFindPartition()+15]"
Created package 3 based on problem key ORA 7445 [qmxarFindPartition()+15], correlation level


As previously discussed, creating an incident package based on a problem includes diagnostic information for incidents associated to that problem.  Since the same problem could potentially include many incidents, only the first and last three incidents associated with the problem will be included. This prevents the inclusion of superfluous information in the package.  Additionally, incidents older than 90 days are excluded to prevent the inclusion of incidents that are no longer impacting the database.  These settings apply to all generated incident packages except manually created packages.  Both of these options are configurable by either using IPS set configuration or the Enterprise Manager Support Workbench. 

When creating an incident package based on a time interval, the DBA can either include incidents that occurred relative to the current time, or inside of a specific time interval.  To create a package based on incidents that occurred a certain time from the present, use ?ips create package seconds [seconds]?.  This will include incidents that occurred within secondsfrom the time the command was run.  For example, ?ips create package seconds 600? will create a package including incidents that occurred within the last 10 minutes. 

To use a time interval instead, use the command ?ips create package time 'start_time? to ?end_time??.  The start and end times in the command must be in the time format 'YYYY-MM-DD HH24:MI:SS.FF TZR' or 'YYYY-MM-DD HH24:MI:SS TZR'.  The colons in the ?HH24:MI:SS? can optionally be substituted with periods.  To create the package based on the incidents that occurred between November 11, 2015 10PM and November 12, 2015 12AM (2 hour window), the command would be:

adrci> IPS CREATE PACKAGE TIME '2007-11-11 22:00:00 -08:00' to '2007-11-12 00:00:00 -08:00'
Created package 4 based on time range 2015-11-11 22:00:00 -08:00 to 2015-11-12 00:00:00 -08:00,
correlation level typical


If the issue that is being reported to Oracle Support has not been captured as an incident, create an empty package using ?ips create package? without any options.

Rampant author Laurent Schneider has some additional insight into creating an Oracle Automatic Diagnostic Repository (ADR)


This is an excerpt from the new book Oracle 11g New Features: Expert Guide to the Important New Features by John Garmany, Steve Karam, Lutz Hartmann, V. J. Jain, Brian Carr.

You can buy it direct from the publisher for 30% off.


Oracle Training at Sea
oracle dba poster

Follow us on Twitter 
Oracle performance tuning software 
Oracle Linux poster


Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.