Details
1. Data is saved at time 'x'
2. Again, Data modified and saved from NX at time 'x+6'
3. At time 'x+7', error appears while saving file.
4. After closing the data, we reopen the same data, but the data is showing of modified time as 'x'
Solution
From TC syslog
++++++++++++
INFO - 2019/11/27-12:42:23.007 UTC - CWSHPMU1265.09688.01.288233.04689 - Service Request: Core-2006-03-FileManagement:commitDatasetFiles - Teamcenter.Soa.Communication
NOTE - 2019/11/27-12:42:23.537 UTC - CWSHPMU1265.09688.01.288233.04689 - (RIL) really_delete_locks: Failed to delete all the locks - Teamcenter.POM at D:\workdir\tc11301_a01_win64\src\foundation\pom\ril\ril_locks_db.cxx(3370)
**** THIS PROCESS HAS GONE FROM THE PROCESS LIST TABLE IN THE DATABASE ****
This is probably because someone ran clearlocks on our process Please do not report any locking bugs or POM_i_am_a_zombie_process errors from this process until you are confident clearlocks abuse does not account for them.
You have lost the lock you had on 0000826e/iyVlrUWZV5OjgD because someone asserted your session was dead
This description of the process that took away your lock may help you place the blame:-
infodba/infodba CPU:msiltclicrhel SESSION:00006d43 msiltclicrhel clearlocks27971.syslog 2019/11/26 23:57:55
++++++++++++
This message is coming from your database server and indicates that the Teamcenter session is no longer connected.
Running clearlocks -assert_all_dead should resolve the condition.
Hardware/Software Configuration
Platform: INTL64
OS: windows
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V11.0.2
Function: FILE_SAVE
Ref: 002-8016683