After installing V3.1.2.13 (or higher), an additional client backup must
occur before the expiration problem is completely cleared up.  Remember,
that your ADSM database will shrink only when the number of objects is
reduced.  So, unless you have reduced the number of backups to be retained
or the length of time they should be retained, your database won't shrink.

On Sun, 14 Mar 1999, malkit wrote:

> Hello !
>
> I have a customer with 6GB of data base. We upgrade to to V3.1.2.1 and
> run expire inventory. The output of the process was:
>
> ANR0812I Inventory file expiration process 3 completed:
>                           examined 372334 objects, deleting 101915
> backup objects,
>                           0 archive objects, 0 DB backup volumes, and 0
> recovery
>                           plan files. 0 errors were encountered.
> ANR0987I Process 3 for EXPIRE INVENTORY running in the
>                           BACKGROUND processed 101915 items with a
>                           complition state  of SUCCESS at 12:01:43.
>
> How come the data base didn't shrink ? We run audit reclaim and audit db
> as well, and the data base is still 6GB.
>
> I checked the number of files per node (LL_NAME) and got the following
> results:
>
> adsm> select node_name,count(ll_name) as "# files"  from backups group
> by node_name
>
>
> NODE_NAME         # files
> ------------------     -----------
> BART                     539421
> HOMER                 5728376
> LISA                       2918072
> MAGGIE                117951
> MARJ                     272645
> SYDNEY                626943
>
> --
> Regards
>
> Malkit Hayun , UDI
> Storage Products Manager
> IBM Certified Specialist-ADSM
> Office: 972-3-9233440
> Fax:    972-3-9233441
> Mobile: 972-52-834575
> Email: malkit AT udi.co DOT il
>