Posted: Thu Feb 13, 2003 3:22 am Post subject: Cant delete a message set from the config manager
Apprentice
Joined: 01 May 2002 Posts: 31
I want to import a new version of a message set into a config manager but I cant delete the previous version as MQSI complains that a resource is locked out.
I've had all developers check to see if they've got anything checked out and everyones done a File-Check-in-ALL(save to shared). Still get the same problem.
I've logged on as IBMMQSI2 and tried File-Check-in-ALL(save to shared) as well but get an error complaining that an element couldnt be found (not one thats actually in the Message Set im trying to delete though)
Even tried looking at the cuuidlocks table in the MQSICMDB but it doesnt
show anyone having anylocks but IBMMQSI2 - and none of these appear to be related to message sets.
Anyone now a way to get around this or where to look in the MQSIMRDB/MQSICMDB to find out what message set parts are locked
and by who ?
I had a similar problem from time to time.
Try to check out the resource. Possible you will receive an error in Control center with information:The resource already been checked out ...
Locking userID ...
If error will not appear than check in the resource. I guess the will disappear. _________________ Best regards.
Yaakov
SWG, IBM Commerce, Israel
Posted: Thu Feb 13, 2003 7:03 am Post subject: thats the problem...
Apprentice
Joined: 01 May 2002 Posts: 31
the error message wasnt saying which resource was locked (when all the developers tried the operation) and this particular message set contains 1000's of items, groups etc..
I've solved this now more by chance than anything else. I got our team leader to try the same Check-in all (save to shared) operation just to be thorough (he never does any work so it couldnt be him ) and for some reason it actually reported the element that was locked and who had it locked.
The strange things about this is :
1. The person who had it locked out had already checked in everything they had checked out (I removed the lock using the IBMMQSI2 user)
2. Why werent the other developers notified about the resource that was locked when they tried to check in their outstanding locked objects?
Just another MQSI mystery ! (looking forward to upgrading to v2.1 soon..)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum