You have to be at 4.2.3.2 and there is a special patch you may have to put on if cleanup backupgroups fails at the 4.2.3.2 level. Has a cleanup backupgroups been run?
Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Michael Moore [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 3:40 PM To: [EMAIL PROTECTED] Subject: Re: Errors after upgrade from TSM 4.2.1.9 to TSM 4.2.3.0 I have not seen that one. We went from 4.2.2.12 to v4.2.3 last week. The only thing we are having a problem with are backupsets are taking extremely long. But this was an issue before going to v4.2.3. Support said the problem was with 'orphaned' system objects, and v4.2.3 would correct the problem (after we ran "cleanup backupgroups"). Well, it didn't. They are now looking at other possibilites. What were you doing when the error occured? Backup, restore, reclaim? Michael Moore VF Services Inc. 105 Corporate Center Blvd. Greensboro, NC 27408 336.424.4423 (Voice) 336.424.4544 (Fax) 336.507.5199 (Pager) David Browne <[EMAIL PROTECTED] To: [EMAIL PROTECTED] OM> cc: Sent by: "ADSM: Subject: Errors after upgrade from TSM 4.2.1.9 to TSM 4.2.3.0 Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 01/15/03 08:24 AM Please respond to "ADSM: Dist Stor Manager" I was running TSM 4.2.1.9 on OS390/2.10 and upgraded yesterday to TSM 4.2.3.0 and now I am receiving the following error messages: ANR9999D SMNODE(2008): ThreadId<942> Duplicate object encountered during import or rename. Anyone else have this same problem and what did you do to correct?
