All language subtitles for [SubtitleTools.com] ADRCI - Learning Oracle 12c [Video]

In this lesson, we'll
be looking at the ADRCI.

So to describe
what the ADRCI is,

we need to talk a little bit
about the old way of managing

alert, log, and trace files.

And so typically, there
would be a database parameter

that would define the
location of the alert log

and any trace files.

And some people would
just accept the default,

but other DBAs would
actually put them

in certain special places.

So this was a little
problematic for Oracle

from a support perspective.

Because normally,
what would happen

is when you had a problem and
you contacted Oracle Support

to open an incident
with them, they

would request the alert log
and certain trace files.

And normally, the trace files
for a certain date period.

And so the DBA
would go find those.

And then send those to support.

And then oftentimes,
support would look at them

and say, well, this isn't
all of the trace files

that we need for this
particular incident.

Then they would
come back and ask

for more, which is frustrating
for the DBA, who's trying

to get their problem fixed.

We'd go back and forth
with that for a while.

And then eventually, hopefully
some resolution would come.

Starting at 11g,
Oracle consolidated

this diagnostic information into
what it called the Automatic

Diagnostic Repository, or ADR.

And so the ADR is nothing more
than a directory structure

on disk.

So it's actually in the
Oracle based directory

in a folder called
DIAG, and then there's

a number of sub
directories off of that.

So Oracle writes all of
its diagnostic information

for the database
products in the ADR.

And now we can
interface with them

using a tool called the ADRCI,
Automatic Diagnostic Repository

Command Line Interface, which
is why we call it ADRCI,

instead of saying
the whole name.

So the ADRCI is going to
be our primary way that we

interface with these files now.

And probably the best
thing about the ADRCI

is that it can be used
to package problem

incidents for Oracle Support.

So we can literally
ask the ADRCI what

are the problems
in the database,

and then we can go through
the steps of packaging up

exactly the diagnostic
information that is needed

in order to solve the problem.

So much less time is spent going
back and forth with the support

to get the right files.

So here is our Oracle
based directory.

And we see our DIAG
directory here.

So everything under here
will be considered the ADR.

There's going to be
a number of products

in this case that don't have
any information underneath them.

This is just the directory
structure themselves.

So RDBMS is going to contain
the alert log and trace files.

Then we have TNS
Listener which will

have networking information.

Listener log, that's here.

But for the most
part the way we're

going to interface with
this information is

through the ADRCI.

The ADRCI is a
command line tool.

Say ADRCI, and it
brings us here.

So to start with,
let's just type

help and look at a few
of the commands that

are available to us.

We can create reports.

IPS is the command
that we use to package

incidents for Oracle.

We can do a few things.

Let's just do some simple
ones here, like Show Base.

That's going to tell us
what our Oracle base is.

Say Show Homes, that's
going to give us

the diagnostic homes for
different parts of our system.

And one of the things
we can do with ADRCI

is, actually, even if we
don't want to package anything

for support, we could
actually find out

if there's any incidents
in the database.

So the ADRCI is recording
information anytime something

goes seriously wrong.

So serious bug type of errors,
system errors, those kind

of things.

So we can use it
to check and see,

even if we're not opening
a ticket with Oracle.

Or we could say Show
Incident, and then it's

those zero of those fetched.

So it sees no incidents, either
in the database directory,

the RDBMS, or the
listener directory.

Show Problem, and it
finds nothing there.

If we want a list of the trace
files for our particular home,

we could say show trace file.

Then it gives a list of
the various trace files

that are in our
diagnostic repository.

But one we would commonly
use would be Show Alert.

So say we want to
look at the Alert Log.

Well, we can certainly go down
through all of the directory

structures and find it.

And many DBAs still
do, because that's

kind of how things
were done in the past.

But we could just start up
the ADRCI, type Show Alert,

and then choose the Alert
Log that we want to see.

We want the Database Alert
Log, so that's number one.

And notice that the
Alert Log pops up.

And this is actually converting
XML into text for us to read.

So you can see the name
of it is system generated

name, a temporary
name, in order for it

to present it to us as text.

And then we cue to
quit and type Exit.

So that's a little bit about
the ADRCI and the things

that it can do for a DBA.