Re: How to monitor schema changes

"Rick Denoire" <100.17706_at_germanynet.de> wrote in message news:43lvfuo2shp4rhj2p25nbn2cq38th1m21c_at_4ax.com...
> Hello
>
> Users complain to the DB administrator (me) when the DB developer has
> changed the DB schema so that the SQL queries don't work anymore.
>
> Is there a way to monitor changes in the DB schema? I mean when tables
> or views are renamed, columns are deleted, etc.
>
> I thought that doing an export with the option rows=no and comparing
> this output (which contains all ddl commands) with further similar
> exports should reveal any changes.
>
> In general, what is the best practice in order to avoid this kind of
> problems caused by changes in the DB schema? (Supposing that such
> changes are absolutely necessary).
>
> Thanks
> Rick

1 check the last_ddl_time in dba|all|user_objects 2 The best practice is
a not to allow untested 'service packs'/'upgrades' or 'patches' b) implement some form of source control like Visual Source Safe.

Hth

--
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address