Ravi,
Wouldn't that be a nice feature (to track SELECTs)? Too bad that Oracle has seen fit not to implement this capability...or perhaps they worried (depending upon their implementation) that such a feature could bring db performance to its knees...(Imagine how much
writing would need to occur on simple SELECTs.) Well, such a debate is not for us to get into here.
Without pre-planning, the best that you can hope for, looking back on table activity, is querying "DBA_OBJECTS","ALL_OBJECTS", or "USER_OBJECTS" which all have columns "CREATED" and "LAST_DDL_TIME". As you can imagine, however, "LAST_DDL_TIME" is certainly not good enough to determine the "usage value" of a table.
Perhaps the best method currently available to determine "usage value" from a data-only perspective is to have implemented (at the birth of the table) a trigger to update a control table with the "LAST_INSERT", "LAST_UPDATE", and "LAST_DELETE" dates for a table. But, again, since you didn't implement such a feature "In The Beginning", you have no resource
now to analysis "usage value".
Therefore, the only available resouce you have now is "Application Analysis"...specifically, you must analyse application code to determine
code references.
Sorry for the bad news.
![[santa] [santa] [santa]](/data/assets/smilies/santa.gif)
Mufasa
(aka Dave of Sandy, Utah, USA)
[
Providing low-cost remote Database Admin services]
Click here to join
Utah Oracle Users Group on Tek-Tips if you use
Oracle in
Utah USA.