Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,390 --> 00:00:04,570
In this lesson, we'll
be looking at the ADRCI.
2
00:00:04,570 --> 00:00:07,180
So to describe
what the ADRCI is,
3
00:00:07,180 --> 00:00:10,240
we need to talk a little bit
about the old way of managing
4
00:00:10,240 --> 00:00:11,590
alert, log, and trace files.
5
00:00:11,590 --> 00:00:14,740
And so typically, there
would be a database parameter
6
00:00:14,740 --> 00:00:18,220
that would define the
location of the alert log
7
00:00:18,220 --> 00:00:19,780
and any trace files.
8
00:00:19,780 --> 00:00:22,390
And some people would
just accept the default,
9
00:00:22,390 --> 00:00:23,980
but other DBAs would
actually put them
10
00:00:23,980 --> 00:00:25,640
in certain special places.
11
00:00:25,640 --> 00:00:27,970
So this was a little
problematic for Oracle
12
00:00:27,970 --> 00:00:30,190
from a support perspective.
13
00:00:30,190 --> 00:00:31,690
Because normally,
what would happen
14
00:00:31,690 --> 00:00:35,080
is when you had a problem and
you contacted Oracle Support
15
00:00:35,080 --> 00:00:37,480
to open an incident
with them, they
16
00:00:37,480 --> 00:00:40,810
would request the alert log
and certain trace files.
17
00:00:40,810 --> 00:00:44,170
And normally, the trace files
for a certain date period.
18
00:00:44,170 --> 00:00:47,770
And so the DBA
would go find those.
19
00:00:47,770 --> 00:00:49,780
And then send those to support.
20
00:00:49,780 --> 00:00:51,940
And then oftentimes,
support would look at them
21
00:00:51,940 --> 00:00:53,980
and say, well, this isn't
all of the trace files
22
00:00:53,980 --> 00:00:56,060
that we need for this
particular incident.
23
00:00:56,060 --> 00:00:57,430
Then they would
come back and ask
24
00:00:57,430 --> 00:01:00,340
for more, which is frustrating
for the DBA, who's trying
25
00:01:00,340 --> 00:01:01,660
to get their problem fixed.
26
00:01:01,660 --> 00:01:04,240
We'd go back and forth
with that for a while.
27
00:01:04,240 --> 00:01:07,060
And then eventually, hopefully
some resolution would come.
28
00:01:07,060 --> 00:01:09,910
Starting at 11g,
Oracle consolidated
29
00:01:09,910 --> 00:01:13,840
this diagnostic information into
what it called the Automatic
30
00:01:13,840 --> 00:01:17,470
Diagnostic Repository, or ADR.
31
00:01:17,470 --> 00:01:20,650
And so the ADR is nothing more
than a directory structure
32
00:01:20,650 --> 00:01:21,610
on disk.
33
00:01:21,610 --> 00:01:24,520
So it's actually in the
Oracle based directory
34
00:01:24,520 --> 00:01:27,190
in a folder called
DIAG, and then there's
35
00:01:27,190 --> 00:01:29,800
a number of sub
directories off of that.
36
00:01:29,800 --> 00:01:32,650
So Oracle writes all of
its diagnostic information
37
00:01:32,650 --> 00:01:35,260
for the database
products in the ADR.
38
00:01:35,260 --> 00:01:37,000
And now we can
interface with them
39
00:01:37,000 --> 00:01:42,460
using a tool called the ADRCI,
Automatic Diagnostic Repository
40
00:01:42,460 --> 00:01:45,880
Command Line Interface, which
is why we call it ADRCI,
41
00:01:45,880 --> 00:01:48,190
instead of saying
the whole name.
42
00:01:48,190 --> 00:01:51,940
So the ADRCI is going to
be our primary way that we
43
00:01:51,940 --> 00:01:54,070
interface with these files now.
44
00:01:54,070 --> 00:01:56,920
And probably the best
thing about the ADRCI
45
00:01:56,920 --> 00:01:59,230
is that it can be used
to package problem
46
00:01:59,230 --> 00:02:01,150
incidents for Oracle Support.
47
00:02:01,150 --> 00:02:04,270
So we can literally
ask the ADRCI what
48
00:02:04,270 --> 00:02:06,130
are the problems
in the database,
49
00:02:06,130 --> 00:02:08,350
and then we can go through
the steps of packaging up
50
00:02:08,350 --> 00:02:12,100
exactly the diagnostic
information that is needed
51
00:02:12,100 --> 00:02:13,750
in order to solve the problem.
52
00:02:13,750 --> 00:02:18,040
So much less time is spent going
back and forth with the support
53
00:02:18,040 --> 00:02:20,660
to get the right files.
54
00:02:20,660 --> 00:02:23,240
So here is our Oracle
based directory.
55
00:02:23,240 --> 00:02:25,700
And we see our DIAG
directory here.
56
00:02:25,700 --> 00:02:28,830
So everything under here
will be considered the ADR.
57
00:02:28,830 --> 00:02:30,500
There's going to be
a number of products
58
00:02:30,500 --> 00:02:33,470
in this case that don't have
any information underneath them.
59
00:02:33,470 --> 00:02:36,690
This is just the directory
structure themselves.
60
00:02:36,690 --> 00:02:41,010
So RDBMS is going to contain
the alert log and trace files.
61
00:02:41,010 --> 00:02:43,080
Then we have TNS
Listener which will
62
00:02:43,080 --> 00:02:46,480
have networking information.
63
00:02:46,480 --> 00:02:49,210
Listener log, that's here.
64
00:02:49,210 --> 00:02:50,670
But for the most
part the way we're
65
00:02:50,670 --> 00:02:52,460
going to interface with
this information is
66
00:02:52,460 --> 00:02:54,640
through the ADRCI.
67
00:02:54,640 --> 00:02:58,860
The ADRCI is a
command line tool.
68
00:02:58,860 --> 00:03:02,900
Say ADRCI, and it
brings us here.
69
00:03:02,900 --> 00:03:04,820
So to start with,
let's just type
70
00:03:04,820 --> 00:03:07,340
help and look at a few
of the commands that
71
00:03:07,340 --> 00:03:09,960
are available to us.
72
00:03:09,960 --> 00:03:12,150
We can create reports.
73
00:03:12,150 --> 00:03:15,420
IPS is the command
that we use to package
74
00:03:15,420 --> 00:03:16,770
incidents for Oracle.
75
00:03:16,770 --> 00:03:18,310
We can do a few things.
76
00:03:18,310 --> 00:03:23,040
Let's just do some simple
ones here, like Show Base.
77
00:03:23,040 --> 00:03:25,780
That's going to tell us
what our Oracle base is.
78
00:03:25,780 --> 00:03:28,650
Say Show Homes, that's
going to give us
79
00:03:28,650 --> 00:03:32,890
the diagnostic homes for
different parts of our system.
80
00:03:32,890 --> 00:03:35,490
And one of the things
we can do with ADRCI
81
00:03:35,490 --> 00:03:38,340
is, actually, even if we
don't want to package anything
82
00:03:38,340 --> 00:03:41,190
for support, we could
actually find out
83
00:03:41,190 --> 00:03:43,150
if there's any incidents
in the database.
84
00:03:43,150 --> 00:03:47,280
So the ADRCI is recording
information anytime something
85
00:03:47,280 --> 00:03:48,390
goes seriously wrong.
86
00:03:48,390 --> 00:03:51,690
So serious bug type of errors,
system errors, those kind
87
00:03:51,690 --> 00:03:52,530
of things.
88
00:03:52,530 --> 00:03:54,330
So we can use it
to check and see,
89
00:03:54,330 --> 00:03:57,210
even if we're not opening
a ticket with Oracle.
90
00:03:57,210 --> 00:04:01,270
Or we could say Show
Incident, and then it's
91
00:04:01,270 --> 00:04:02,820
those zero of those fetched.
92
00:04:02,820 --> 00:04:06,360
So it sees no incidents, either
in the database directory,
93
00:04:06,360 --> 00:04:09,700
the RDBMS, or the
listener directory.
94
00:04:09,700 --> 00:04:15,680
Show Problem, and it
finds nothing there.
95
00:04:15,680 --> 00:04:19,020
If we want a list of the trace
files for our particular home,
96
00:04:19,020 --> 00:04:22,340
we could say show trace file.
97
00:04:22,340 --> 00:04:24,300
Then it gives a list of
the various trace files
98
00:04:24,300 --> 00:04:27,440
that are in our
diagnostic repository.
99
00:04:27,440 --> 00:04:31,680
But one we would commonly
use would be Show Alert.
100
00:04:31,680 --> 00:04:33,670
So say we want to
look at the Alert Log.
101
00:04:33,670 --> 00:04:36,580
Well, we can certainly go down
through all of the directory
102
00:04:36,580 --> 00:04:38,050
structures and find it.
103
00:04:38,050 --> 00:04:40,000
And many DBAs still
do, because that's
104
00:04:40,000 --> 00:04:41,950
kind of how things
were done in the past.
105
00:04:41,950 --> 00:04:45,130
But we could just start up
the ADRCI, type Show Alert,
106
00:04:45,130 --> 00:04:47,470
and then choose the Alert
Log that we want to see.
107
00:04:47,470 --> 00:04:51,430
We want the Database Alert
Log, so that's number one.
108
00:04:51,430 --> 00:04:54,410
And notice that the
Alert Log pops up.
109
00:04:54,410 --> 00:04:59,080
And this is actually converting
XML into text for us to read.
110
00:04:59,080 --> 00:05:01,630
So you can see the name
of it is system generated
111
00:05:01,630 --> 00:05:04,090
name, a temporary
name, in order for it
112
00:05:04,090 --> 00:05:05,820
to present it to us as text.
113
00:05:08,440 --> 00:05:12,160
And then we cue to
quit and type Exit.
114
00:05:12,160 --> 00:05:14,950
So that's a little bit about
the ADRCI and the things
115
00:05:14,950 --> 00:05:17,060
that it can do for a DBA.
9279
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.