I wasn't aware of any back when I had the question/problem... so, many years ago, I rolled my own. I'm still not aware of any other scripts so I've been continuing to use the home-rolled solution. FWIW, I recently revisited and re-wrote portions of it to use git for tracking the changes-- this allowed me to throw out much of the original custom code.

While it isn't the most elegant code I've ever written, it works well enough and it isn't so ugly as to make my eyes bleed looking at it. The current incarnation is built around the dbms_metadata package, sqlplus, git, perl, shell, and cron.

The work flow is more-or-less as follows (for each database of interest, with each database having it's own git repository):

• delete the results (if any) of the previous DDL extract (but NOT the .git directory)
• use sqlplus and the dbms_metadata package to extract the DDL from the database (this is the oldest surviving piece, written back in the day)
• parse the resulting file (using perl) and writing the object DDL out in a file structure of the form "db_name/ddl/schema_name/object_type/object_name.sql" (Note that, since the parser was written against the dbms_metadata output, it may not work well, or at all, when run against DDL generated by other means-- YMMV)
• `git commit` the results
• `git clone` some of the exported databases to the gitweb data directory so the developers can peruse the DDL history

This runs once a week from cron on a linux box (could run it more often but weekly is sufficient for our purposes).

I'm pretty pleased so far with using git to track the changes-- so pleased I've even gone so far as to twist git to document the DDL differences between our production, test, and development databases. The work flow for documenting the differences operates along the lines of (for each pair of databases to compare):

• delete the previous DDL comparison project (including the .git directory)
• `git init` a new comparison project
• copy the already extracted DDL directory from the "from database" to the new project dir
• `git add` and `git commit` the project dir
• delete the extracted DDL from the project dir
• copy the extracted DDL directory from the "to database" to the new project dir
• `git add` and `git commit` the project dir
• `git clone` the results to the gitweb data directory

...at this point the comparison git repository has but two commits, the "from database" and the "to database" and git kindly indicates the new, deleted, moved and changed db object DDL files.

I don't have this anywhere out on the net but you can drop me a line if you're interested in looking at it.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.