Documenting Oracle Databases

The latest version of dbscript 0.96 now supports importing schema information from Oracle databases.

Version 0.96 introduces the separation of various database engines (previous versions assumed MSSQL Server only), and a dbscript Project must now explicitly define which database engine it is based on (MSSQL or Oracle).

In the database properties form for “live” databases, you can define the Oracle connection in two ways:

  • set “Server” to the instance name listed inside tnsnames.ora and leave “Catalog” empty
  • set “Server” to server:port, and “Catalog” to the service name (as in tnsnames.ora)

A new field called “Import Options” allows you to define the scope of the schema import:

  • “USER” (the default value)
  • “ALL:” + list of user names
  • “DBA:” + list of user names

The user specified in “Username” needs to have access to the ALL_ and DBA_ catalog views, respectively.

Sample Output based on the HR Demo Database

Wiki documentation of Oracle Demo Schema

Single HTML documentation of Oracle Demo Schema

Data Diagram of Oracle Demo Schema:

To access Oracle databases, dbscript requires ODP.Net from the Oracle Data Access Components 11g to be installed on the web server.

dbscript is available for download here.

2 thoughts on “Documenting Oracle Databases

  1. Pingback: Documenting Oracle Databases « devioblog

  2. Pingback: Creating Dia Data Diagrams from Database Schema « devioblog

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.