but last_ddl_time is last time you compile the package.
If the app server automatically compiles on request it will update that.
Main Topics
Browse All TopicsWhat would be the best way to check if there was new code compiled into oracle database recently to troubleshoot issues that may be cause by it?
Would you select on user_objects to see and chec the created date?
would that include everything new that was introduced?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
database links only have created timestamps, last_ddl and timestamp will be null for those.
last_ddl_time will be updated whenever dll is executed (explicitly or implicitly)
timestamp will be updated if the object "specification" changes due to the ddl
informally, that means the timestamp changes only if the object "looks" different afterward.
so, truncate on a table will updated last_ddl_time but not timestamp because the table still "looks" the same
triggers may go invalid and get recompiled due to underlying packages changing and their last_ddl_time will update from implicit compilation as they are used, but unless you actually modify the trigger the timestamp won't change
indexes will usually have timestamp and last_ddl_time in synch. most ddl will touch both; but monitoring usage only modifies last_ddl_time, there might be others but I can't think of them off hand, also note, some ddl doesn't update either. alter index ..... coalesce for instance, doesn't update last_ddl_time or timestamp
Business Accounts
Answer for Membership
by: sdstuberPosted on 2009-11-04 at 13:20:26ID: 25744061
I would check dba_objects rather than user_objects
and I would look at last_ddl_time