anr2033e define stgpool: command failed - lock conflict

Zaka

Newcomer
Joined
Feb 4, 2019
Messages
2
Reaction score
0
Points
0
Hi All,

when define storage pool, there found error :

anr2033e define stgpool: command failed - lock conflict.

using Spectrum Protect 8.1.8. anyone can help to solve this error..?


Thanks,
Zaka
 
Suspected the following APAR but it is address at 8.1.6 .

IT25199: ANR2033E DEFINE ASSOCIATION: COMMAND FAILED - LOCK CONFLICT.

Since we are issuing define stgpool rather than define association.
There is a possibility that we me be encountering a variation of IT25199.

Are there any other error message(s) around the time frame ANR2033e?

Was the Spectrum Protect Server recently upgraded to 8.1.8 ?

Would have to open a ticket with IBM to see if there is a work around or a APAR that may not be publish at this time.

Good Luck,
Sias
 
Hi Sias,

when running command define stgpool, admin console become stuck/hang. it need around 2-3 hrs then error ANR2033e appear. even to run command query stg it's becoma stuck too.
Spectrum was upgraded from 8.1.4 to 8.1.8 on August.

Yes, the ticket was opened for this case. below from support :

Thread 339, Parent 262: SmAdminCommandThread, Storage 76752, AllocCnt 39 HighWaterAmt 77168
tid=70364686840160, ptid=70364706959712, det=0, zomb=0, join=0, result=0, sess=0, procToken=0, sessToken=8
lwp=63313
Stack traces are disabled by option.
Awaiting cond SDV->traversingPoolListCond (0x0x3fffb3255c20), using mutex SDV->poolMutex (0x0x12090d60), at sdpool.c(4522)
Thread context:
COMMAND: DEFINE STGPOOL
COMMMETHOD: SSL
THREAD_TYPE: SESSION
SESSION_TYPE: ADMIN
ADMIN_NAME: ADMIN

This is a define stgpool cmd... This holds the resources waiting by other threads

LockDesc: Type=34000(ss universe), NameSpace=0, SummMode=sixLock, Key=''
Holder: (sspool.c:1554 Thread 339) Tsn=0:12370, Mode=sixLock
Waiter: (sspool.c:7107 Thread 322) Tsn=0:175039, Mode=sLock
Waiter: (sspool.c:1554 Thread 7131) Tsn=0:197889, Mode=sixLock
Waiter: (ssclass.c:1731 Thread 3226) Tsn=0:285660, Mode=isLock

Can you please :
1: don't run concurrent define stgpool the same time, this cmd acqire the same locks.
2: for now, please stop thread 339 and other define stgpool cmd

su - instance_id
db2 "force application (1230,8318,10407)"

After that finishes: cancel all the admin sessions... see if this can break the hang...

If that doesn't, schedule a time to halt restart.

After applying request from support, there is still error to run command define storagepool.
schedule a time to halt restart can not be applied since last halt process was stuck too.

when checking process db2 list utilities, there two process are executing :
1. TSMDB1.SD_REFCOUNT_UPDATES
2. TSMDB1.SD_CHUNK_LOCATIONS

thanks,
Zaka
 
Back
Top