RE: using system event triggers

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Thu, 26 Feb 2004 18:18:44 -0800
Message-ID: <B5C5F99D765BB744B54FFDF35F60262119FBDA@irvmbxw02>

Are you getting ready for April Fool's Day? As far as I know it's not possible. If you raise an error then all you will get is the error logged in a trace file. I suppose you could try to find a command that, because of an Oracle bug, causes the database to go down. One was mentioned on the list today. (NUMTOYMINTERVAL with an extra long parameter) How about doing an "alter system enable restricted session" in the trigger? Would that be sufficient? Are you trying to verify the database name or the global name?

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Josh Collier Sent: jeudi, 26. février 2004 16:42
To: 'oracle-l_at_freelists.org'
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; /

---

Please see the official ORACLE-L FAQ: http://www.orafaq.com

---

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html


-----------------------------------------------------------------

Received on Thu Feb 26 2004 - 20:22:39 CST