> Jared, > > >Track DDL_TIME, CREATION_DATE and TIMESTAMP for all objects. > > In our Apps database, I have a System trigger that records *all* DDL, with > the exception of 'pre-approved' DDL. [Remember your earlier post about the > pre-approved changes?] That would be useful, but I need a baseline at a certain date, for comparison to the database at a later date. > In short, you will need to keep in mind that: > > * Java code (and applications) could be stored in many locations, including > the Database (Java Stored Procedure), Business Tier (OC4J, EJB), Web Tier > (JSPs and Servlets) as well as at the Client tier (separately as a Java > Application or run as an Applet). > ... Thanks for the great input John. We don't write any any Java apps here, so all I'm interested tracking are changes to std installed stuff (if installed) and new Java that has been added. There may be database utility code, but that will all be stored in the database. I'll check the articles. Jared ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------