Oracle Internals Questions

From: Cary B. O'Brien <cobrien_at_access2.digex.net>
Date: 1995/10/02
Message-ID: <44qc0d$74k_at_access2.digex.net>#1/1


I have lots of questions about oracle internals.

  1. From what form are PL/SQL procedures executed? Are they interpreted, byte compiled, or native code. (In the normal RDBMS, not forms or things like that).
1.a. what is diana 
1.b  what is pidl (sp?)
1.c  how do I set breakpoints and examine variables (I know, use
     dbms_output or buy _procedure builder_.  But my boss is cheap.
     And it _is_ a cross-'compiler').
1.d  Can it be looked at beyond 'all_source'.
1.e where is the code, whatever it is.
1.f If you stick stuff in all_source, and do 'alter (whatever) compile',

     will it work? (I suppose it wouldn't kill me to try it myself).

2. Where is the documentation for tablespace, segement, and

   extent layout. I.E beyond the server concepts guide.

3. Is it possible to write database access procedures in the

   underlying language as implied by the output of explain plan?    Sometimes I think that this might be easier than fussing with    sql to get the optimizer to work right.

4. Why to tables take up code space?

5. Are there tables of the v$ ilk beyond those documented. Have I

    overlooked something obvious?

6. Anyone else interested in this kind of stuff?

7. Do third-party vendors have access to oracle internals or do

    they figure it out and hope for the best. I.e. tablespacae     de-fragmenters.

8. Does oracle give courses on this stuff?

9. Why doesn't someone just take a few days and write an RPC

    interface to oci or method 4 dynamic PRO*C so we don't     have to use SQL/NET. Is this a good idea? If so why, if     not why not. Be specific. Use examples. You have 45 minutes.

  1. Speaking of PRO*C -- is the underlying interface to the RDBMS OCI?
  2. Any oracle jokes? Like make babies or got a match? Or anything.

BTW - This is honest interest. I am not interested in making life

      more difficult for anyone. Really.

Thanks in advance.

Cary O'Brien
cobrien_at_access.digex.net Received on Mon Oct 02 1995 - 00:00:00 CET

Original text of this message