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?]
>The section I'm unsure of is in regards to Java. I don't believe that
You have me here (and I believe a majority in this list). However, I
recently read two articles that greatly helped in shining the light on such
javahead type questions. The articles in question are 'I love the Java Jive:
J2EE Overview for Oracle Technologists' - Paper 110 at IOUG 2004 by Peter
Koletzke and 'The Fast Track to Java with Oracle' by Brad Brown in Oracle
Internals.
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).
- The moment you move away from using Java inside the Database (Java Stored
Procedures), and as long as you don't manage the 9iAS J2EE containers,
essentially, as a DBA, you are technically not responsible for the 'Java
code' and changes there of. In the practical world, I haven't seen that many
pure Database-based Java code, outside of Oracle Applications.
- There are a large number of Web servers that allow a multiplicity of
layering (and thus java code storage as either classes, JAR/WAR/EAR files,
or whatever!), so you as a DBA will not have visibility as to where this
originates.
- The rate at which Java technology (both in development and deployment)
changes is mind-boggling and one is unable to keep up, so this might be out
of date even as I write!
- In general, the Javaheads that I have met have very strong leaning towards
one or the other technologies and tools around those technologies (and there
is a lot of open source stuff out there!). So you might have to first put up
agreed upon standards in both development and deployment before you can
track changes for SarbOx.
- Most Javaheads write code that is 'Database independent', although they
_know_ that they are writing against an Oracle database. [Evidence is the
NON-USE of Sequences in most of the Java appls that I have seen: Use a
'select max(emp_no) + 1 from emp' to get the next number to allocate is a
typical one!]. The point is not to berate {as implied here) but to point out
that there is very deep, percieved and self-created divide (by the
Developers) between the Database and the Java layers.
Now, all of this is based on my very, very brief interaction with Java
technologies. But I believe I have seen enough to warrant this note!
Hth,
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)
Listen to great, commercial-free christian music 24x7x365 at
http://www.klove.com
Received on Tue Jul 20 2004 - 17:06:21 CDT
