Hi,
i think you have to examine around 3*61 Mio =183 mio ,
as far as I can remember there are 3 objects for every file/directory -object

No one can say how long time this will take - it may also happen
that this process slows down or may get faster .

You may think  -with your IBM support-  about following:
" -though it is not recommended to interrupt an audit process, it is
 neither impossible nor forbidden
 - may be the server cannot be started after the interrupt because it
 asks for a successful audit - please just run in this case a partial
 audit with
 dsmserv auditdb admin fix=yes detail=yes > auditadmin.log
 It should take only a very short time and afterwards it should be
 possible to start the server (if the interrupt didn't cause any other
 issues preventing restart of the TSM server) "

good luck
Rainer


Zitat von "Ochs, Duane" <Duane.Ochs AT QG DOT COM>:

The results from the select 60,963,651

Expiration results for the same TSM server expiration: examined
124,304,930 objects

This TSM instance is approximately 1/2 the size of the DB being audited
and that has processed over 450 million entries.

I'm assuming the entries identified in the db updates is using more than
just number of files or objects.

Any other ideas ?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Friday, September 19, 2008 10:33 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Auditbd help

Select Sum(NUM_FILES) as "Total Files" from OCCUPANCY will quickly tell
you the count in your storage pools.
Add some factor for Unix directories and empty files, which are solely
within the TSM database.

     Richard Sims