Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: PL*SQL Procedures becoming corrupt / becoming uncompiled

Re: PL*SQL Procedures becoming corrupt / becoming uncompiled

From: <catatony_at_my-deja.com>
Date: 2000/03/17
Message-ID: <8atmgq$mk4$1@nnrp1.deja.com>#1/1

One more note: in my situation, when the packages become "invalid", they are not being automatically recompiled.

In article <953228903.12904.0.pluto.d4ee154e_at_news.demon.nl>, "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote:
> This occurs because they are validated each time they are called.
> The problem usually occurs most frequently when procedures call each
 other,
> this can result in deadlock on the datadictionary.
> If they are really heavily used you should pin them in the shared
 pool.
> At least this prevents revalidation.
> Use dbms_shared_pool.keep('<USERNAME>.<PROCEDURENAME>')
>
> Invalid procedures are recompiled automatically.
> Alternatively you could try
> dbms_utility.compile_schema('<SCHEMANAME>');
>
> Hth,
>
> Sybrand Bakker, Oracle DBA

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Fri Mar 17 2000 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US