Automatic Diagnostic Repository Command Interpreter (ADRCI)

To start ADRCI in the interactive mode, type adrci at the command line, as shown here:

Invoke ADRCI.

[oracle@srv1 ~]$ adrci
ADRCI: Release 12.1.0.2.0 - Production on Wed Feb 12 22:37:21 2020
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
ADR base = "/u01/app/oracle"
adrci>

You can view all the ADRCI commands available to you by typing HELP

adrci> help
HELP [topic]
Available Topics:
CREATE REPORT
ECHO
EXIT
HELP
HOST
IPS
PURGE
...
SHOW LOG
SHOW PROBLEM
SHOW REPORT
SHOW TRACEFILE
SPOOL
SELECT

You can get detailed information for an individual ADRCI command.

adrci> help IPS
HELP IPS [topic] 
Available Topics: 
ADD 
ADD FILE 
ADD NEW INCIDENTS 
...
UNPACK FILE 
UNPACK PACKAGE 
USE REMOTE KEYS 
adrci>

To execute an ADRCI command directly at the command line instead of invoking ADRCI first and working
interactively with the ADR interface, specify the parameter EXECwith the ADRCI command, as shown here:

[oracle@srv1 ~]$ adrci EXEC="SHOW HOMEPATH;"
ADR Homes: 
diag/rdbms/oradb/ORADB
[oracle@srv1 ~]$
To view an alert log with ADRCI

Enter the following command to view the alert log

adrci> show alert
ADR Home = /u01/app/oracle/diag/rdbms/oradb/ORADB:
*************************************************************************
Output the results to file: /tmp/alert_12549_1401_ORADB_1.ado

The alert log will pop up in your default editor.

If you want to examine just the latest events in the alert log, issue the following command:

adrci> show alert -tail 50

To shows a “live” alert log

adrci> show alert -tail -f

ou can issue the following command to trap the ORA- errors.

adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'"
2019-08-31 00:08:46.912000 +03:00
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
2019-08-31 00:09:19.360000 +03:00
Errors in file /u01/app/oracle/diag/rdbms/oradb/ORADB/trace/ORADB_ora_27076.trc:

The SHOW TRACEFILE command with filters. The following example looks for trace files that reference ORA

adrci> show tracefile %ora%
diag/rdbms/oradb/ORADB/trace/ORADB_ora_6607.trc
diag/rdbms/oradb/ORADB/trace/ORADB_ora_6583.trc
diag/rdbms/oradb/ORADB/trace/ORADB_ora_6524.trc
adrci>

You can view all incidents in the ADR with the show incident command

adrci> show incident
ADR Home = /u01/app/oracle/diag/rdbms/oradb/ORADB:
*************************************************************************
INCIDENT_ID PROBLEM_KEY CREATE_TIME 
-------------------- ----------------------------------------------------------- ---------------------------------------- 
16873 ORA 700 [kskvmstatact: excessive swapping observed] 2020-02-04 19:19:37.450000 +03:00 
17121 ORA 445 2020-02-04 19:20:13.078000 +03:00 
16874 ORA 700 [kskvmstatact: excessive swapping observed] 2020-02-04 20:26:40.534000 +03:00 
17122 ORA 445 2020-02-04 21:01:48.661000 +03:00 
16875 ORA 700 [kskvmstatact: excessive swapping observed] 2020-02-04 21:27:42.627000 +03:00 
17123 ORA 445 2020-02-04 21:30:25.444000 +03:00 
16876 ORA 700 [kskvmstatact: excessive swapping observed] 2020-02-04 22:30:51.505000 +03:00 
7 rows fetched

You can specify the detail mode

adrci> show incident -mode detail -p "incident_id=16873"

ADR Home = /u01/app/oracle/diag/rdbms/oradb/ORADB:
*************************************************************************
**********************************************************
INCIDENT INFO RECORD 1
**********************************************************
INCIDENT_ID 16873
STATUS ready
CREATE_TIME 2020-02-04 19:19:37.450000 +03:00
PROBLEM_ID 2
CLOSE_TIME <NULL>
FLOOD_CONTROLLED none
ERROR_FACILITY ORA
...
ERROR_NUMBER 700
ERROR_ARG1 kskvmstatact: excessive swapping observed
PROBLEM_KEY ORA 700 [kskvmstatact: excessive swapping observed]
INCIDENT_FILE /u01/app/oracle/diag/rdbms/oradb/ORADB/trace/ORADB_dbrm_3248.trc
OWNER_ID 1
INCIDENT_FILE /u01/app/oracle/diag/rdbms/oradb/ORADB/incident/incdir_16873/ORADB_dbrm_3248_i16873.trc
1 rows fetched
adrci>
Packaging Incidents for Oracle Support

Here are the steps to create an incident package.
Create an empty logical package as shown here:

adrci> ips create package 
Created package 1 without any contents, correlation level typical

Add diagnostic information to the logical package with the ips add incident command

adrci> ips add incident 16873 package 1
Added incident 16873 to package 1

The incident 16873 is associated with package 1, but there are no diagnostic data in it yet.

Generate the physical package.

adrci> ips generate package 1 in /u01/app/oracle/diag\ 
2>
Generated package 1 in file /u01/app/oracle/diag/IPSPKG_20200212221955_COM_1.zip, mode complete

Send the resulting IPSPKG_20200212221955_COM_1.zip file to Oracle Support

Mughees Ahmed

Over 2-year experience of Administration in Oracle, SQL Server, and MySQL databases using various tools and technologies. Keen on learning new database technologies having very good analytical skills. Working knowledge of Red Hat Linux, UNIX, Solaris and Windows Server 2012 is a valuable addition to my knowledge desk. KNOWLEDGE & SKILLS • Oracle Database Server 10g/11g/12c. • Oracle RAC, Data guard. • Oracle Golden Gate (Oracle to Oracle, Oracle to MySQL and MySQL to Oracle) • Oracle Enterprise Manager Grid Control, Toad, SQL developer. • SQL Server 2005/2008/2012/2016. • SQL Server Failover clustering, mirroring & log shipping, Always On availability groups. • MySQL 5 Administration, MySQL Workbench, MySQL Enterprise Monitor, SQLyog • MySQL NDB Cluster Installation,Administration. • MySQL Asynchronous/Semi-synchronous replication. • Oracle OEM Contact me on mughees52@gmail.com

Leave a Reply