Thank you for the info.

Just for the ha-ha's, I ran another expire and it didn't generate any 
errors.  However, I found it interesting that it still found something to 
delete considering there weren't any backups run and there was only about 
10-minutes between runs.  I guess if the expiration process is very 
granular down to the minute/second, theoretically it would always find 
something to expire......................


Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will 
never use email to request that you reply with your password, social 
security number or confidential personal information. For more details 
visit http://infosecurity.vcu.edu/phishing.html



From:
Mark Haye <mark.haye AT US.IBM DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/28/2011 01:46 PM
Subject:
Re: [ADSM-L] Expire Inventory errors after upgrade to 6.1.5.10
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



> 7/28/2011 10:20:14 AM ANR9999D_3916334743 ComputeHashValue
(tbcache.c:4313) Thread<91>: Table Group.Leaders, Column 4 of type 0 not
valid for hashKey.

This is a known problem, fixed in internal defect 73872.  It is not 
related
to the Win2K8 system state cleanup problem.  All indications are that the
message is "harmless" and does not adversely affect server operation.  If
you haven't opened a PMR for it yet, that would be the next step ...

Mark Haye (马克海), IBM TSM Server Development, mark.haye AT us.ibm DOT com,
8/321-4403, (520)799-4403, 0N6/9062-2, Tucson
Professional programmer.  Closed source.  Do not attempt.