Thanks everyone...

IBM had me follow IC88605.

The issue was table/index reorg kicked in during the weekend when our schedules 
are different.

I've been running this server for MONTHS without any problem.

I edited the serv.opt file, commented out the reorg parms and halted/started 
TSM.

I'll leave reorg disabled until I can install 6.2.4.

Thanks again to everyone.

------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information 
Technology Services
Harold.Vandeventer AT da.ks DOT gov
(785) 296-0631

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Clark, Margaret
Sent: Monday, April 16, 2012 12:32 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 6.2.3 DB2 Deadlock

We had this back in February, when a reorg deadlocked with a migration.
Get help right away, and while you're waiting, check APAR: IC81261
- Margaret

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Vandeventer, Harold [BS]
Sent: Monday, April 16, 2012 8:52 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 6.2.3 DB2 Deadlock

I find my DB2 database in a deadlock condition.  It's been deadlocked for about 
40 hours.

It's run fine for many, many months until this weekend.

Running on Windows 2008 R2.

During node backup, migration kicked in (as it does frequently).  But, 
apparently, migration is trying to move a file that a node is backing up?

Anyone have a suggestion?  I've opened a PMR but don't have a response yet.

I hesitate to halt/restart the TSM service without some guidance.


------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information 
Technology Services Harold.Vandeventer AT da.ks DOT gov
(785) 296-0631