Activity Logging/Trending not reporting correct last accessed dates on Inactive databases

So I have configured up Activity Logging and Activity Trends in the configuration document for our Application servers, hoping to identify unused and redundant databases, of which I suspect there are many. Statlog is running and I have restarted the server since the config document change. Now to my excitement, I see under the Server, Analysis tab of the Dom Administrator under Activity Trends, a directory called Database, Inactivity. When I look at this directory I see a big bunch of documents representing inactive databases, when I open a document I see a “Last Active Date” of say 2/11/2003. The document links to the corresponding document in the catalog, and I see that the “Last Active Date” is actually the same as the “Database last modified date” in the catalog document. But when I go to the Database Properties, Information tab, User Detail and bring up the Activity Logging dialogue, I can see that users have accessed the database and read and written documents in the past 12 months.

I’m not sure where the catalogue gets this “Database last modified date” from, as it does not match the Modified date of the database on the Information tab either.

Any ideas on this? I was hoping Activity Logging would accurately assist me in the location of databases that had not been accessed by users in some time - removal/retiring of redundant databases in such a crucial part of any admins world, how do others tackle this in the larger environments? Manually going through each database or using the log is just too time consuming, I want a definitive list.

Thanks for any input,

Kellee

Subject: Activity Logging/Trending not reporting correct last accessed dates on Inactive databases.

My suggestion is to leave activity logging running a bit longer to collect more information. Activity trends first takes the “Database last modified date” from the catalog.nsf and will then update the lastmodified date with data from activity logging. Also mind that user activity can be both reads and writes, while last modified date only records edits to databases.

Do you have agent logging type enabled? (in the configuration settings) Could it be that the user activity was generated by a background agent? In this case the activity is not logged.