Cancel
Showing results for 
Search instead for 
Did you mean: 

POM_timestamp maintenance

Experimenter
Experimenter

What is the use of POM_timestamp  maintenance in Teamcenter?

4 REPLIES

Re: POM_timestamp maintenance

Valued Contributor
Valued Contributor

The POM_timestamp table records the time of an object’s most recent modification. The POM_timestamp table holds timestamps for a configured amount of time. (The default is 96 hours.) By default, Teamcenter performs maintenance on the POM_timestamp table at session logout. If this becomes a bottleneck due to the volume of concurrent session logouts, moving to manual maintenance offers better control.

 

 

To perform manual maintenance on the POM_timestamp table (nightly or as appropriate):

 

https://docs.plm.automation.siemens.com/tdoc/tc/11.4/help/#uid:id1617770

 

install -tidy_timestamps -u=user  -p=password  -g=group 

 

Regards
Rafa

Re: POM_timestamp maintenance

Experimenter
Experimenter

@Rafa2wrote:

The POM_timestamp table records the time of an object’s most recent modification. The POM_timestamp table holds timestamps for a configured amount of time. (The default is 96 hours.) By default, Teamcenter performs maintenance on the POM_timestamp table at session logout. If this becomes a bottleneck due to the volume of concurrent session logouts, moving to manual maintenance offers better control.

 

 

To perform manual maintenance on the POM_timestamp table (nightly or as appropriate):

 

https://docs.plm.automation.siemens.com/tdoc/tc/11.4/help/#uid:id1617770

 

install -tidy_timestamps -u=user  -p=password  -g=group 

 



 

Its mainly used for the Teamcenter Session? 

 

Do you have any detailed document that you prepared for this.

 

Do we need to set any preference value below for this

TC_TIMESTAMP_TIDY_MODE

 

Re: POM_timestamp maintenance

Valued Contributor
Valued Contributor

This is mainly used to enable manual maintenance of POM_timestamp table to alleviate POM_timestamp update bottlenecks during the logout process.

 

Note: Please make sure to plan for manual maintenance of the POM_timestamp table as appropriate if using this method. A very large POM_timestamp table can cause performance issues in other areas.

 

TC_TIMESTAMP_TIDY_MOD is just a install utility for manual cleaning of POM_TIMESTAMP table

 

Capture.PNG

 

I am sorry I don't have any specific documents for it.

Regards
Rafa

Re: POM_timestamp maintenance

Siemens Experimenter Siemens Experimenter
Siemens Experimenter

Good morning, just found the way to the forum.. and it looks like a good place to share some expierence. 

 

POM_timestamp is introduced in Tc9, and it replaced the check against PPOM_OBJECT (ptimestamp), so Teamcenter is will do a refresh against POM_timemstamp instead of PPOM_OBJECT to see if objects need to be refreshed. 

 

To keep the table small, they are delleted after 96 hrs. Now if have created a lot of objects, for example in a migration or in a bigger release workflow, this delete can take a few seconds. The default setting is that the delete is done by every tc_server during the logout. And there you can sometime see a lock issue if the logout happens from multiple tc_server.

 

The 

TC_TIMESTAMP_TIDY_MODE = manual

Is deactivating the delete from each tc_server and the responsibility to keep the table small is handed over the adminstrator. They can use the install tool and run it in a regular cycle to clean the timestamps.

 

Another side effects of putting 96 hrs is that if you have a process that runs longer then 96 hrs, it is possible that he will not be able to identify changes anymore. So it is also recommended to make sure that all processes are restarted after some time (task_monitor, subscription_manager, etc..) 

 

If you see a issue with POM_timestamp let me know. Maybe I can help.