All Teamcenter clients and users should know of SFB-Teamcenter-8568. Due to a problem involving concurrent use of generating and accessing shared memory, the use of shared memory can cause memory corruption in certain cases. This is more evident in the UNIX/Linux platform. These shared memory issues will be completely resolved in Teamcenter 11.2, slated to be released in late July 2015, where shared memory will be fully robust with enhancements.

Affected Software: Teamcenter 8.3 and MPs or patches up to TC11.2
Associated PR Number(s): 1792150, 2241061
Associated document: SFB-Teamcenter-8568
Associated document: Steps for disabling preferences in shared memory (download or view)

SYNOPSIS:

For user convenience we are outlining here the steps for disabling preferences in shared memory. Download these instructions.

High-Level Process

1)     Shutdown the environment (services\processes)
a)      On remote servers.
b)     On Web/App servers.

2)     Run in a Tc command window
a)      clearlocks -assert_all_dead
b)     install -lock_db

3)     Delete the shared memory directory
a)      TC_SHARED_MEMORY_DIR

4)     In custom env file (or directly in tc_profilevars.bat)
a)      set TC_USE_PREFS_SHARED_MEMORY=FALSE

5)     Run in a Tc command window
a)      generate_metadata_cache -u=infodba -p=infodba -g=dba -force

6)     Optionally clean up
a)      Clear logs in TC_TMP_DIR
b)     Clear logs in TC_LOG (%TC_DATA%\log_%TC_DB_SERVER%_%ORACLE_SID%)

7)     Run in a Tc command window
a)      install -unlock_db

8)     Restart the environment (services\processes)
a)      On App/Web servers.
b)     On remote servers.

Default Values

TC_NO_TEXTSRV_SHARED_MEMORY = FALSE

TC_USE_LOV_SHARED_MEMORY = TRUE

TC_USE_METADATA_SHARED_MEMORY = TRUE

TC_USE_PREFS_SHARED_MEMORY=TRUE

Notes

The side effect of turning off shared memory is that each tcserver takes additional memory as below.