IPs simple Use Method:
The IPS (Incident packaging service) is a new feature of 11G that is designed to look at all the dump and trace files associated with an error and can easily be made into a package, which I think is a great convenience for DBAs to diagnose remotely.
Pre: Set the Oracle_home and PATH environment variables first before use.
Enter the ADRCI console:
$adrci
Adrci tool is started.
List ADR HOME:
Adrci> Show Home
Diag/rdbms/v11/v11
Set Adrhome path:
Adrci> Set HomePath diag/rdbms/v11/v11
List problem:
Adrci> Show Problem
--will list ORA-600, ORA-7445, ORA-1578, and accompany problem_id, Problem_key and error dates.
Package the error trace file
adrci> IPs pack problem <problem id> in/tmp
--The Operation packages error-related TRC files to/tmp according to PROBLEM_ID.
Annex I: ADR how to package Diagnostic information in 11g
Invoke Adrci and set Adr_home.
You can create a logical package based on an incident number, a problem number, a problem key, or a time interval. Create A logical package such that it'll be is most useful to diagnose the error of your concern.
I) Creating package based on incident.
Select correct incident If there is many incidents.
Adrci>show INCIDENT
Adrci>ips CREATE Package INCIDENT Incident_number
II) Creating Empty package.
Adrci>ips CREATE Package
This creates a empty package. You must use the IPs add INCIDENT or IPs add FILE commands to ADD diagnostic data to the package before generating it.
III) Creating package based on problem ID
Adrci>ips CREATE Package Problem problem_id
This creates a, includes diagnostic information for incidents that reference the specified
Problem ID. (Problem IDs is integers.) You can obtain the problem ID for a incident from the
Report displayed by the SHOW incident-mode BRIEF command. Because There can be many incidents and the same problem ID, Adrci adds to the package the diagnostic information for the First three incidents ("early incidents") that occurred and the last three incidents ("late incidents") that
occurred with the problem ID, excluding any incidents that is older than.
IV) Creating package based on problem key
Adrci>ips CREATE Package Problemkey "Problem_key"
The problem key must is enclosed in a single quotes (') or double quotes (") if it contains spaces or quotes.
V) Creating package based on time interval.
This creates a package and includes diagnostic information for all incidents that occurred from sec
Seconds ago until now. SEC must is an integer.
Adrci>ips CREATE Package SECONDS sec
Adrci>ips CREATE Package time ' start_time ' to ' end_time '
This creates a package and includes diagnostic information for all incidents that occurred within the
Specified time range. Start_time and End_time must is in the format ' Yyyy-mm-dd HH24:MI:SS. FF TZR '.
This was a valid string for the Nls_timestamp_tz_format initialization parameter. The fraction (FF) portion of the time is optional, and the HH24:MI:SS delimiters can be colons or periods.
Adding Incidents and files to the logical package:
You can add more files or more incidents to the package.
Adrci>ips ADD INCIDENT Incident_number Package Package_number
Adrci>ips ADD FILE filespec Package Package_number
Filespec is the complete path and name of the trace file to add.
Package_number is the package ID.
Generate a physical incident package:
Once you has created a logical package using one of the above methods, next step was to generate a physical package.
Adrci>ips GENERATE Package Package_number in Path
This generates a complete physical package (zip file) in the designated path. For example, the
Following command creates a complete physical package in the Directory/home/steve/diagnostics
From logical Package number 2:
Adrci>ips GENERATE Package 2 in/home/steve/diagnostics
Upload This package to the SR for diagnosing the problem.
You can also create and generate package with one command:ips Pack.
Adrci>ips PACK INCIDENT incident_id in Path
All the methods discussed above apply to ' IPS pack ' as well.
Attached two: Database 11g:quick Steps to package and Send Critical Error Diagnostic information to support:
ORACLE11G provides tools and methods to automatically identify and gather trace files related to a problem (a critical err or in the database environment) or an incident (an occurrence of a problem). This facility is known as the Incident packaging Services (IPS). The support Workbench (GUI) and Adrci (command line) utilities is the interfaces to the Incident packaging Services. Every occurrence of a critical error (problem) in the database creates an incident.
Steps in identifying and sending files to support.
1. You is notified of a critical error reported in the database environment:
Sql> select * from Atab;
SELECT * FROM Atab
*
ERROR at line 1:
Ora-01578:oracle data Block corrupted (file # 6, Block # 11)
Ora-01110:data file 6: '/OPT/ORACLE/ORADATA/DB11G/TT.DBF '
2. Check for the error reported in the instance alert file and in the ADR.
To check for the error reported in the ADR:
With the 11g environment being set, from the OS command prompt invoke the Adrci utility:
$ adrci
Let Adrci know which Oracle environment to investigate:
Adrci> Show Home
--show Home would list all the ADR homes. Set the proper database ADR home for use with Adrci.
Adrci> Set HomePath Database_home
Check for the problems reported:
Adrci> Show Problem
ADR Home =/opt/oracle/diag/rdbms/db11g/db11g:
*************************************************************************
problem_id Problem_key last_incident Lastinc_time
------------ -------------- --------------- ---------------------------------
1 ORA 1578 18104 2009-06-01 22:06:19.501207 +10:00
1 Rows fetched
You can have multiple problems reported. Create A which needs to be investigated.
3. Check for the incidents reported for the problem which needs to be packaged
Each occurrence of the problem was called an ' incident '. The instance alert file would show all the incidents reported. Each incident is associated with a unique incident ID in the ADR.
From the Adrci prompt, execute the SHOW INCIDENT command for the problem to being investigated, by specifying the associated Problem key. You can get the problem key from the SHOW problem command:
Adrci> show incident-p "problem_key= ' ORA 1578 '"
ADR Home =/opt/oracle/diag/rdbms/db11g/db11g:
*************************************************************************
incident_id Problem_key Create_time
--------------- ------------------------ ----------------------------------
18147 ORA 1578 2009-06-01 22:02:08.805002 +10:00
1 Rows fetched
You can see multiple incidents reported for the same problem.
Note the incident number for which your need to create a package.
4. Package The trace files invoking IPS.
Generate the package using the IPS PACK command and store the generated package in a directory of your choice. The example below shows the package for the incident would be a created in the/tmp directory.
adrci> IPs pack incident 18147 In/tmp
Generated Package 9 in File/tmp/ora1578_20090602113045_com_1.zip, mode complete
If at this step the Adrci utility complains that the incident is flood-controlled and that no package can generated fo R it, then instead of choosing the most recent incident to being packaged, choose the first incident that occurred after an I Nstance startup.
Examples of IPS PACK include:
IPs pack Problem in/tmp
--generates the package for the problem ID of in/tmp
IPs pack incident 6439 in/tmp
--generates the package for the incident ID 6439 in/tmp
IPs pack Problemkey "ORA 1578"
--generates the problem with the Problem_key ' ORA 1578 '
IPs pack seconds 8
--generates the package with the incidents occurred on last 8 seconds.
IPs pack time ' 2007-05-01 10:00:00.00 ' to ' 2007-05-01 23:00:00.00 '
--generates the package with the incidents occurred between the Times ' 2007-05-01 10:00:00.00 ' and ' 2007-05-01 23:00:00.00 '
Upload the ZIP file generated to the Service Request for your created on the My Oracle support website. This file would include all of the trace files, instance alert file and other diagnostic information for the critical error. Make sure, the ZIP file is uploaded without any post processing (such as TAR).
Attached three: 11g Understanding Automatic Diagnostic Repository
What's New in 11g?
In 11g, RDBMS diagnostic data have been reorganized and is stored inside a common directory structure, the Automatic Diagno Stic Repository (ADR). An ADR is a centralized directory structure where one can find trace files, alert messages, incident dumps, core files, et C.
Automatic Diagnostic Repository (ADR):
All trace files, core files, and the alert files is now organized to a directory structure comprising the Automatic Dia Gnostic Repository (ADR).
The ADR is a file-based repository for database diagnostic data. It has a unified directory structure across multiple instances and multiple products.
