Instead of modifying the trigger all the time, why not just maintain rows in
a table?
Here's what I've written after I got tired of making typos that caused the
objects after it to fail to pin:
CREATE OR REPLACE TRIGGER sys.qt_pin_on_startup AFTER STARTUP ON DATABASE
DECLARE
v_count NUMBE
Thanks Suzy, Waleed, John, Richard, Connor, Jonathan, for your help.
Out of shape on sundays :-)
TKS
-Original Message-
Vordos
Sent: Sunday, February 23, 2003 3:44 PM
To: Multiple recipients of list ORACLE-L
Don't think you need to use execute immediate. Try this (should be run
as
... oops
and then you might want to add that you really
have to mess around with quote marks and
begin/ends to get it to work - something like (and
I really ought to test this before posting, 'cos it's
one of those tiny details that there's no point in
wasting valuable memorisation time on)
b
...oops, and I forgot to add that you might wanna wrap
the call to 'dbms_shared_pool' in pin_me within exec
immed, so that if the package ever goes invalid (or
does not exist - ie forgotten to be run) the trigger
will still run ok.
cheers
connor
--- Richard Ji <[EMAIL PROTECTED]> wrote: >
remove
Now that everyone has said "remove the exec" I'll
confuse things :-) by adding that you might to have
the trigger always "succeed", because after all, it is
a startup trigger on the database.
So maybe something like:
create or replace trigger ...
procedure pin_me(x,y,z) is
begin
dbms_shar
Title: Message
remove
exec immediate.
Richard
-Original Message-From: Ramon E. Estevez
[mailto:[EMAIL PROTECTED]Sent: Sunday, February 23,
2003 2:59 PMTo: Multiple recipients of list
ORACLE-LSubject: Error pinning PKS in shared pool
Sorry, new DB
and hadn't execut
Title: Message
You can take out the “exec immediate”,
I believe.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ramon
E. Estevez
Sent: Sunday, February 23, 2003
2:59 PM
To: Multiple recipients of list
ORACLE-L
Subject: Error pinning PKS in
sha
Title: Message
You do not need 'exec immediate'
- Original Message -
From:
Ramon E. Estevez
To: Multiple recipients of list ORACLE-L
Sent: Sunday, February 23, 2003 2:58
PM
Subject: Error pinning PKS in shared pool
Sorry, new DB
and hadn't execute the D
Don't think you need to use execute immediate. Try this (should be run
as SYS):
CREATE OR REPLACE TRIGGER PAQUETES_MEMORIA
AFTER STARTUP ON DATABASE
BEGIN
dbms_shared_pool.keep('DBMS_ALERT');
dbms_shared_pool.keep('DBMS_DDL');
dbms_shared_pool.keep('DBMS_DESCRIBE');
dbm