My favorite Oracle manuals, in no particular order:

SQL Reference
PL/SQL Packages and Types Reference
Application Developer’s Guide – Fundamentals
PL/SQL User’s Guide and Reference

I guess the shorter the title, the more I like it :-)

Seriously, I’ve always thought the quality and breadth of documentation from Oracle to be pretty good — especially when compared with docco from other vendors.  Microsoft and Siebel documentation is pretty poor in my opinion — non-existent or only documents blatantly obvious stuff.  I’m continually amazed at so-called Oracle developers who don’t have the Oracle Documentation link bookmarked…

4 Responses to “Docco”

  1. Eddie Awad Says:

    Moreover, if you use Firefox, you may want to install this extension:

    and/or this plugin:

    Or if you’re an IE user, you may want to check:


  2. Doug Burns Says:

    I agree. I think Oracle’s documentation is generally excellent. It’s always easy to have a dig at a big vendor, but I wish everything I used was documented as well.

    I suppose if I had a criticism it would be that it can be difficult for novices to find the right book to look in. Yes, I know they can use tahiti etc, but they always seem to struggle with this.

    Once you know how to use the documentation, it does the job

  3. ddelmoli Says:

    You know, the 10g R2 Database section of the Oracle Documentation web site called “Most Popular” is a pretty good starting point. Well, except for “2 Day DBA”. That title alone gives me nightmares about novices. Sounds like “DBA in a Box” :-)

  4. peter bell Says:


    this message is not related to this thread but I read your Hotsos paper and wondered if you could elaborate on your source control procedures ?

    I would like to implement the delivery package structure you detailed therein. As I understand, each release would get a new root directory with the ddl,dml,plsql and install subdirectories.

    But we use CVS for our source control and therefore, there is one diectory structure that holds all releases but each release is tagged within CVS. Therefore, I’m not sure if your directory structure would be appropriate (but I guess it could be implemented with some modifications).

    Is the delivery package directory structure you describe (ddl,dml,plsql,install etc) directly under CVS (or someother source control tool) ?

    Hope you get a chance to answer. If not, thanks anyway for an interesting whitepaper and informative blog.

    peter bell

Leave a Reply

Posting code can be a pain. To make sure your code doesn't get eaten, you may want to pre-format it first by using HTML Encoder