RE: using system event triggers
- From: "Mercadante, Thomas F" <thomas.mercadante@xxxxxxxxxxxxxxxxx>
- To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 27 Feb 2004 08:24:51 -0500
Josh,
This is a very bad idea. Even if you *could* do it, how in the world would
you be able to fix it? If you cant start the database, then it's basically
hosed.
Just what are you trying to accomplish?
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
From: Josh Collier [mailto:Josh.Collier@xxxxxxxxxxxx]
Sent: Thursday, February 26, 2004 7:42 PM
To: 'oracle-l@xxxxxxxxxxxxx'
Subject: using system event triggers
Is there a way to use a system event trigger to prevent completion of
database open if a criteria isn't met
some psuedo code to elaborate:
CREATE OR REPLACE TRIGGER sys.post_dup_check
AFTER
STARTUP
ON DATABASE
DECLARE
db_name VARCHAR2 (50);
BEGIN
db_name := ora_database_name;
IF db_name ! = ' whatever .WORLD'
then don't open
END IF;
END;
/
- Follow-Ups:
- Re: using system event triggers
- From: Juan Cachito Reyes Pacheco
- Re: using system event triggers
- From: Pete Finnigan
Other related posts:
- » using system event triggers
- » RE: using system event triggers
- » RE: using system event triggers
- » Re: using system event triggers
- » Re: using system event triggers
- » RE: using system event triggers
- Re: using system event triggers
- From: Juan Cachito Reyes Pacheco
- Re: using system event triggers
- From: Pete Finnigan