178-05:00'
org_id='oracle' comp_id='rdbms'
client_id='' type='UNKNOWN' level='16'
host_id='dw' host_addr='192.168.2.95' module='SQL*Plus'
pid='1843'>
statement in resumable session 'User HR(80),
Session 113, Instance 1' was resumed In Figure 6-3, you can see the tablespace USERS9 space alert appear on the instance??™s home
page in the Alerts section, in addition to the previous alert warning you that the USERS9 tablespace
was nearly full about 15 minutes before the HR user temporarily ran out of space!
As far as the user is concerned, the operation took longer than expected but still completed
successfully. Another way to provide more information to the user is to set up a special type of
trigger introduced in Oracle9i called a system trigger. A system trigger is like any other trigger,
Chapter 6: Monitoring Space Usage 195
except it is based on some type of system event rather than on a DML statement against a table.
Here is a template for a system trigger that fires on an AFTER SUSPEND event:
create or replace trigger resumable_notify
after suspend on database -- fired when resumable space event occurs
declare
-- variables, if required
begin
-- give DBA 2 hours to resolve
dbms_resumable.set_timeout(7200);
-- check DBA_RESUMABLE for user ID, then send e-mail
utl_mail.send ('karen_s@rjbdba.com', . . . );
end;
Managing Alert and Trace Files with ADR
New to Oracle Database 11g, the Automatic Diagnostic Repository (ADR) is a system-managed
repository for storing database alert logs, trace files, and any other diagnostic data previously
controlled by several other initialization parameters.
Pages:
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352