They show up on their own during reclamation (and reclamation fails on that 
volume).
Sounds like the patch cleans them up.
Thanks!

W

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Tuesday, October 19, 2010 12:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 6.1 - IC68245 - Unexpected error 2 fetching row in 
table during RECLAIMS

FWIW, we have been at 6.1.4.1 for a while and are no longer seeing the
errors.  How would I check for the orphans?
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:
"Prather, Wanda" <wPrather AT ICFI DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
10/19/2010 11:13 AM
Subject:
[ADSM-L] TSM 6.1 - IC68245 -  Unexpected error 2 fetching row in table
during RECLAIMS
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Anybody on 6.1 who has survived and recovered from IC68245,

Can you tell me whether upgrading to 6.1.4.1 (or a 6.2 x) to get the
fixing code actually takes care of the orphans for you, or does it just
stop new orphans from being created?

Trying to figure out whether it's best to go ahead and upgrade first, or
have Tivoli support clean up the orphans one at a time....

Thanks!

Wanda Prather  |  Senior Technical Specialist  | wprather AT icfi DOT com<
mailto:wprather AT icfi DOT com>  |  www.jasi.com<www.jasi.com%20>
ICF Jacob & Sundstrom  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202
| 410.539.1135