Cancel
Showing results for 
Search instead for 
Did you mean: 

The object is locked for modify in another session

Experimenter
Experimenter

I am unable to modify one particualar item .

 

Error message "You do not have change rights for this ACL
The object is locked for modify in another session.
Locked by "user X" on node "pool server" in a session started at "21-Jun-2019 16:40".

 

Curently there is no session running in the user name (user X).

Ran clearlocks - verbose .still issue is not fixed

9 REPLIES 9

Re: The object is locked for modify in another session

Gears Phenom Gears Phenom
Gears Phenom

Good afternoon, this usually happens when the user session hangs in the pool manager (goes in STATELESS mode). Open the administrator panel .NET or J2EE server manager scroll through the entire list and make sure that the user is assigned one tcserver process.

Re: The object is locked for modify in another session

Experimenter
Experimenter

Thank you for response.There is no tcserver process for this particular user.Pool servers and WAS servers are restarted already.Ran clearlocks as well.

Highlighted

Re: The object is locked for modify in another session

Legend
Legend

Hi,

 

an entry left ove rin the database table POM_M_LOCK?

try

SELECT PPOM_SESSION.puser_name, PPOM_SESSION.plogin_date,
PWORKSPACEOBJECT.pobject_name, PWORKSPACEOBJECT.pobject_type,
PWORKSPACEOBJECT.puid AS object_id, PPOM_SESSION.pprocess_id
FROM PM_PROCESS_LIST RIGHT OUTER JOIN PPOM_SESSION ON PM_PROCESS_LIST.pm_process_id = PPOM_SESSION.pprocess_id
RIGHT OUTER JOIN PWORKSPACEOBJECT
RIGHT OUTER JOIN POM_M_LOCK ON PWORKSPACEOBJECT.puid = POM_M_LOCK.ref_uid ON
PPOM_SESSION.pprocess_id = POM_M_LOCK.process
WHERE PWORKSPACEOBJECT.pobject_name IS NOT NULL;

 

Re: The object is locked for modify in another session

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
The only way that I know to free the lock, which isn't a database lock but more of a process lock, is to reboot whichever machine is listed in the log.

So the log entry was:
Locked by "user X" on node "pool server" in a session started at "21-Jun-2019 16:40".

Which means to reboot "pool server".

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: The object is locked for modify in another session

Legend
Legend

@RandyEllsworth 

If all pool servers are stopped, clearlocks -assert_all_dead infodba dba dba

should solve the issue, or am I wrong?

 

But: It should not be run, if users are connected!!

 

Re: The object is locked for modify in another session

Solution Partner Esteemed Contributor Solution Partner Esteemed Contributor
Solution Partner Esteemed Contributor
If this was a database lock then you would be correct. Any of the previous suggestions would work and @karthickm wouldn't be in this pickle. I've never been able to prove it but I think this is actually an Operating System lock (process lock) which is why rebooting finally frees the lock and life can continue. I used to get this on workstations back in the Tc Engineering days.

Always, its best to shutdown the environment cleanly before rebooting any of the servers.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: The object is locked for modify in another session

Legend
Legend

Instead of using clearlocks, we also used another solution sometimes to delete locks held by users directly from the DB, as described here

https://solutions.industrysoftware.automation.siemens.com/view.php?sort=desc&q=POM_M_LOCK&file_type=...

 

also described here by @RandyEllsworth 

https://community.plm.automation.siemens.com/t5/Teamcenter-Administrators-Forum/Delete-stale-user-se...

 

 

 

Re: The object is locked for modify in another session

Experimenter
Experimenter

Thank you Randy and and Roman .Issue is resolved after running  sql query

 

 

Re: The object is locked for modify in another session

Experimenter
Experimenter

@Roman65 wrote:

@RandyEllsworth 

If all pool servers are stopped, clearlocks -assert_all_dead infodba dba dba

should solve the issue, or am I wrong?

 

But: It should not be run, if users are connected!!

 



clearlocks -assert_all_dead infodba dba dba
didn’t help since it is database level lock.SQL query resolved the issue.