Re: why does 11g plsql_code_type default to interpreted?

From: hpuxrac <johnbhurley_at_sbcglobal.net>
Date: Mon, 3 Mar 2008 13:24:18 -0800 (PST)
Message-ID: <7980bfd4-3783-4ce4-a604-5878505c891d@z17g2000hsg.googlegroups.com>


On Mar 3, 12:01 pm, DA Morgan <damor..._at_psoug.org> wrote:
> hpuxrac wrote:
> > I have a test system running 11g 64 bit on OEL 4.  Created a new
> > database ( custom ... not from template with pre-suppplied
> > datafiles ).
>
> > It seems kind of curious that oracle is defaulting plsql_code_type to
> > interpreted.
>
> > If the native is so much faster ... and you don't need a compiler/etc
> > anymore ... why is this happening for a new database?
>
> > Are there a bunch of bugs and caveats that are still being experienced
> > in this area?  Maybe this default will eventually change by 11.2?
>
> Consider the implication of exporting a procedure if you have
> compiled code versus pcode. You might well choose to import it
> into a different environment.
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington
> damor..._at_x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Groupwww.psoug.org

So are you claiming that export or expdp doesn't export the source code for a procedure along with pcode and/or binary? Received on Mon Mar 03 2008 - 15:24:18 CST

Original text of this message