|
Re: [ADSM-L] anr1880w and other db lock conflicts suddenly appearing
2015-07-27 16:52:58
Hello Gary,
Are you running deduplication? The
IBM technote on managing deduplication and DB growth references this code
directly:
http://www-01.ibm.com/support/docview.wss?uid=swg21452146
It can be caused by a long-running online
reorg. You can check db2 reorg status by using db2pd or db2 list
utilities as the TSM instance owner ID.
I've also seen locking messages due
to an insufficiently high db2 LOCKLIST parameter. This can be adjusted
by following this note:
http://www-01.ibm.com/support/docview.wss?uid=swg21430874
Hope that helps,
__________________________
Matthew McGeary
Technical Specialist - Infrastructure
PotashCorp
T: (306) 933-8921
www.potashcorp.com
From:
"Lee, Gary"
<glee AT BSU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/27/2015 01:55 PM
Subject:
[ADSM-L] anr1880w
and other db lock conflicts suddenly appearing
Sent by:
"ADSM:
Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Tsm server 6.2.5, RHEL 6.5.
I know, out of support, trying to get to 6.3.4 next week.
Suddenly I am getting "anr1880w" messages.
Processes being cancelled because of conflicting locks on table af_bitfiles.
Never seen these before.
Happened while reclamation was running.
Also similar this morning during a delete filespace.
Is there any action I can take to mitigate this?
Message anr1880w is not in my copy of the 6.2 messages manual.
|
|
|
