Re: Error pinning PKS in shared pool

2003-02-24 Thread Jonathan Lewis
... 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)

RE: Error pinning PKS in shared pool

2003-02-24 Thread Ramon E. Estevez
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

RE: Error pinning PKS in shared pool

2003-02-24 Thread Jesse, Rich
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

Error pinning PKS in shared pool

2003-02-23 Thread Ramon E. Estevez
Title: Message Sorry, new DB and hadn't execute the Dbmspool.sql script. CREATE OR REPLACE TRIGGER PAQUETES_MEMORIA AFTER STARTUP ON DATABASE BEGIN exec immediate dbms_shared_pool.keep('DBMS_ALERT'); exec immediate dbms_shared_pool.keep('DBMS_DDL'); exec immediate

Re: Error pinning PKS in shared pool

2003-02-23 Thread Suzy Vordos
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');

Re: Error pinning PKS in shared pool

2003-02-23 Thread Waleed Khedr
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

RE: Error pinning PKS in shared pool

2003-02-23 Thread John Clarke
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

RE: Error pinning PKS in shared pool

2003-02-23 Thread Richard Ji
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

RE: Error pinning PKS in shared pool

2003-02-23 Thread Connor McDonald
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

RE: Error pinning PKS in shared pool

2003-02-23 Thread Connor McDonald
...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