 |
|
EnterpriseDB: View DB Logs
Oracle Tips by
Burleson
|
The View
Log page (Figure 6.10) allows you to see the actual instance log file.
From this page, you can view the log file for any cluster you have
configured in the DBA Management Server (even on remote servers).
This is a huge ease of use feature that other vendors would do well to
emulate.
Figure
6.10: View Database Log
View Audit Logs
The View
Audit Report page (Figure 6.11), is the audit version of the View Log
page. You can choose the cluster to view and set the filter
options. You can choose any of the check boxes or you can select
the Advanced Filtering link to filter by User, Database, or timestamp.
Figure
6.11: View Audit Log
SQL
You will
probably do most of your querying in Developer Studio (or at least
that is what I would recommend) but when you are working in the DBA
Management Server, it's nice to have easy access to a simple query
window. iQuery provides that for you and the Query
Profiler can give you an idea about the queries currently executing in
your database.
iQuery
iQuery
(Figure 6.12) is a basic SQL editor. You can run SQL command or
an anonymous block. From an anonymous block you can call stored
procedures. The output will appear on the Data Output tab and
any messages and errors will appear on the Messages tab.
Figure
6.12: Interactive Query Window (iQuery)
Query Profiler
The
Query Profiler (Figure 6.13) is a bit like a Top report. The
Query Profiler analyzes the log file and aggregates SQL calls. You can
sort the output by the number of times run, the total execution time
and the average execution time.
You can
also choose if you want to see all DML or you can select individual
types of DML.
Figure
6.13: Query Profiler
Scheduler
The
Scheduler allows you to create PL/pgSQL or SPL anonymous blocks and
schedule them to run at a pre-defined interval. The anonymous
blocks may call other stored procedures and may perform DML.
For the
example below, I am going to create a small table. I will
schedule an insert into the table and verify the schedule is working
by checking the values in the table and by checking the schedule log.
The
sample table is:
CREATE TABLE schedule_test (
msg_text
VARCHAR2(50),
date_and_time DATE);
This
is an excerpt from the book "EnterpriseDB:
The Definitive Reference" by Rampant TechPress.
|
