ADRCI: Create An IPS Package in 12c

Summary:

A run through of the commands and procedure to look for problems/incidents in your alert
log file and package them for support.

ADRCI starter;

You may have one or more Oracle homes available. Start by logging into your Oracle
user ID, sourcing your environment if required and entering the adrci command.

oracle:/home/oracle> adrci

ADRCI: Release 12.1.0.2.0 – Production on Mon Apr 17 14:08:28 2017

Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.

ADR base = “/u01/app/oracle”

Show the Oracle homes known by adrci:

adrci> show homes
ADR Homes:
diag/rdbms/db1/db1
diag/clients/user_oracle/host_955550271_11
diag/tnslsnr/server/listener

Now set adcri to the db Oracle home:

adrci> set home diag/rdbms/db1/db1

There are incidents and problems. Problems are issues like ORA-445 messages each occurrence of
a problem is an incident. Incidents can occur many times for each problem.

Lets look at problems in the current db alert log:

adrci> show problem

ADR Home = /u01/app/oracle/diag/rdbms/db1/db1:
*************************************************************************
PROBLEM_ID PROBLEM_KEY LAST_INCIDENT LASTINC_TIME
——————– ———————————————————– ——————– —————————————-
1 ORA 445 316004 2017-03-20 10:19:39.042000 -04:00
3 ORA 240 276107 2017-03-20 10:26:49.643000 -04:00
2 ORA 494 276227 2017-03-20 10:50:40.191000 -04:00
3 rows fetched

Let’s look to see if PROBLEM_ID 1 has more incidents:

adrci> show incident

ADR Home = /u01/app/oracle/diag/rdbms/db1/db1:
*************************************************************************
INCIDENT_ID PROBLEM_KEY CREATE_TIME
——————– ———————————————————– —————————————-
220425 ORA 445 2017-03-13 12:30:18.118000 -04:00
………………………………..
276227 ORA 494 2017-03-20 10:50:40.191000 -04:00
21 rows fetched

Now lets take a look at one of the actual incidents:

adrci> show incident -mode detail -p “incident_id=220425”

ADR Home = /u01/app/oracle/diag/rdbms/db1/db1:
*************************************************************************

**********************************************************
INCIDENT INFO RECORD 1
**********************************************************
INCIDENT_ID 220425
STATUS ready
CREATE_TIME 2017-03-13 12:30:18.118000 -04:00
PROBLEM_ID 1
CLOSE_TIME <NULL>
FLOOD_CONTROLLED none
ERROR_FACILITY ORA
ERROR_NUMBER 445
ERROR_ARG1 Q002
ERROR_ARG2 120
ERROR_ARG3 <NULL>
ERROR_ARG4 <NULL>
ERROR_ARG5 <NULL>
ERROR_ARG6 <NULL>
ERROR_ARG7 <NULL>
ERROR_ARG8 <NULL>
ERROR_ARG9 <NULL>
ERROR_ARG10 <NULL>
ERROR_ARG11 <NULL>
ERROR_ARG12 <NULL>
SIGNALLING_COMPONENT background_proc
SIGNALLING_SUBCOMPONENT <NULL>
SUSPECT_COMPONENT <NULL>
SUSPECT_SUBCOMPONENT <NULL>
ECID <NULL>
IMPACTS 0
PROBLEM_KEY ORA 445
FIRST_INCIDENT 220425
FIRSTINC_TIME 2017-03-13 12:30:18.118000 -04:00
LAST_INCIDENT 316004
LASTINC_TIME 2017-03-20 10:19:39.042000 -04:00
IMPACT1 0
IMPACT2 0
IMPACT3 0
IMPACT4 0
KEY_NAME Module
KEY_VALUE Streams
KEY_NAME ProcId
KEY_VALUE 53.1
KEY_NAME Action
KEY_VALUE QMON Coordinator
KEY_NAME Client ProcId
KEY_VALUE oracle@server.9274_140380478001792
KEY_NAME Service
KEY_VALUE SYS$BACKGROUND
KEY_NAME SID
KEY_VALUE 949.48565
OWNER_ID 1
INCIDENT_FILE /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_220425/db1_qm02_9274_i220425.trc
OWNER_ID 1
INCIDENT_FILE /u01/app/oracle/diag/rdbms/db1/db1/trace/db1_qm02_9274.trc
1 rows fetched

Now I want to see what’s in the trace file:

adrci? /u01/app/oracle/diag/rdbms/db1/db1/incident/incdir_220425/db1_qm02_9274_i220425.trc

…………………………..
[TOC00004-END]
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
——————————————————————————-
rvation=2 time=136975864
326 reservation=2 time=136975864
3< ***** Trace Bucket Dump End: default bucket for process 53 (osid: 9274, QM02) *****
[TOC00005-END]
TIME(*=approx):SEQ:COMPONENT:FILE@LINE:FUNCTION:SECT/DUMP: [EVENT#:PID:SID] DATA
[TOC00006-END]
[TOC00007]
——————————————————————————-
s, collection dur=4350 usecs —- SAMPLING DONE —-
2017-03-13 12:29:40.609973 :83502B9F:db_trace:kso.c@8620:kso_sched_delay_measure(): [10420:3:568] kso: sched delay measure before
ured=1069 usecs, lbound=0 usecs
2017-03-13 12:29:40.611044 :83502BA1:db_trace:kso.c@8620:kso_sched_delay_measure(): [10420:3:568] kso: sched delay measure before
ured=1062 usecs, lbound=0 usecs
2017-03-13 12:29:40.612108 :83502BA3:db_trace:kso.c@8620:kso_sched_delay_measure(): [10420:3:568] kso: sched delay measure before
ured=1078 usecs, lbound=0 usecs
…………………………………..

This one will have to be sent to Oracle support. Time to start the Incident Packaging Service

adrci> ips create package problem 1 correlate all
Created package 1 based on problem id 1, correlation level all

Now that the package is created we need to create the zip file to sent to OWS:

adrci> ips generate package 1 in “/home/oracle”
Generated package 1 in file /home/oracle/ORA445_20170417144525_COM_1.zip, mode complete
Additional incremental files:
/home/oracle/ORA445_20170417144525_INC_2.zip

« Older Entries