Shared Memory

Best Practices Guide

Siemens PLM Software

Version 1.0
December 2014
 Change Summary

Version Date Comment

1.0 12/1/2014 Initial version of Shared Memory Best Practices Guide

Version 1.0 Page 2 Siemens PLM Software

 TABLE OF CONTENTS

1 Where can I download the latest version of this document? .............................................. 5

2 Shared Memory Overview ....................................................................................................... 6
2.1 Why Is Shared Memory Important? ............................................................................................. 6
3 Teamcenter Shared Memory Architecture............................................................................. 8
3.1 Populate Shared Memory Cache.................................................................................................. 8
3.2 Shared Memory for Text Server Data ........................................................................................ 11
3.3 Shared Memory for Site Preference Data .................................................................................. 12
3.4 Shared Memory for Localized LOV Data ................................................................................... 12
3.5 Shared Memory for Metadata ..................................................................................................... 12
4 Administer Shared Memory .................................................................................................. 14
4.1 Configure Shared Memory ......................................................................................................... 14
4.2 Refresh Shared Memory Cache for Text Server Data ............................................................... 15
4.3 Refresh Shared Memory Cache for Site Preference Data ........................................................ 16
4.4 Refresh Shared Memory Cache for Localized LOV Data .......................................................... 16
4.5 Refresh Shared Memory Cache for Metadata ........................................................................... 17
4.6 Clean up Semaphores ................................................................................................................ 18
5 Troubleshoot Shared Memory Problems............................................................................. 19
5.1 Shared Memory Cache Are Stale ............................................................................................... 19
5.2 Client Metadata Cache Are Stale................................................................................................ 19
5.3 Error - Shared Metadata Cache Is Out of Date .......................................................................... 19
5.4 Errors - Unable to Create Pool Lock and Acquire Mutex ......................................................... 19
5.5 Disable Shared Memory and RAC Metadata Cache .................................................................. 20

Version 1.0 Page 3 Siemens PLM Software

Document Audience
This guide provides best practices guides for the Teamcenter administrators, architects and developers who are
responsible for administrating Teamcenter. This guide will grow over time as best practices are identified. This guide
may be distributed to Teamcenter customers, third-party developers, and Siemens PLM Software Global Sales and
Services

Version 1.0 Page 4 Siemens PLM Software

1 Where can I download the latest version of this document?
This best practices guide will be continually updated whenever new information about Teamcenter Shared Memory is
available. To get the latest version, please download from GTAC.

Steps for downloading the document from GTAC:

Go to https://support.industrysoftware.automation.siemens.com/gtac.shtml
Click on the Documentation link.
Click on the Teamcenter link and login.
Click on the tab with the Teamcenter release you administer.
Download the file title: Shared Memory Best Practices Guide

Version 1.0 Page 5 Siemens PLM Software

2 Shared Memory Overview
Shared Memory is the fastest interprocess communication mechanism between collocated processes especially
when large amount of data need to be shared. Once the memory is mapped into the address space of the processes
that are sharing the memory region, the processes can access the shared memory area like regular working memory
with no overhead incurred. Since only one copy of the data in the shared memory is resident for all the processes that
are sharing the memory region, using shared memory for common data reduces the overall system memory footprint.
In the following figure, we draw one dashed box enclosing Teamcenter Server 1 and the shared memory, and another
dashed box enclosing Teamcenter Server 2 and the shared memory, to reinforce that the shared memory appears in
the address space of both the Server 1 and the Server 2. In fact, the shared memory appears in the address space of
all the Teamcenter servers, Teamcenter utility processes and Teamcenter service (daemon) processes that
are run on the same machine.
It should be noted the Teamcenter shared memory implementation is applied to all the afore-mentioned, collocated
Teamcenter processes that are run on the same machine. The remainder of this document uses Teamcenter servers
as example to present Teamcenter shared memory implementation.

Teamcenter
Teamcenter Server2
Server1 Shared Memory
Text Server Data
Site Preference Data
Localized LOV Data
Metadata
Server1 Address Space
Server2 Address Space

2.1 Why Is Shared Memory Important?

Shared Memory provides the following benefits in Teamcenter:
Reduce memory footprint for each server process and utility process

Large amount of data are loaded into shared memory. These data include text server data, site preference
data, localized LOV data and metadata. As a result, private memory footprint for a server process is
reduced. For example, in a Teamcenter 9.1.2 environment, the savings in the private memory footprint for a
server process are as follows:

TextServer ~6MB
Preferences ~2-4MB
LOV ~5MB
Metadata ~19MB

Improve Teamcenter scalability

Since private memory footprint is reduced per server, more Teamcenter servers can be configured on the
same machine than previously.

Improve Teamcenter performance

Version 1.0 Page 6 Siemens PLM Software

 All the shared data are populated once in shared memory, and saved in local backing-store files. Once
backing-store files are generated, all the subsequent servers do not need to populate data into shared
memory. Therefore, the login time for all the subsequent servers is improved.
In the case of the shared metadata, the metadata cache is pre-generated (e.g. during the install and
upgrade). This helps to further reduce the metadata population time. As a result, there is approximately 18%
improvement in the login time.
Shared metadata memory solution also helps to improve overall performance for other use cases as well.
This is because each server is able to access the already-populated shared metadata cache, which would
otherwise have to be on-demand initialized by each server if shared metadata cache were not used.

Version 1.0 Page 7 Siemens PLM Software

3 Teamcenter Shared Memory Architecture

3.1 Populate Shared Memory Cache

All the Teamcenter servers running on the same machine use the same shared memory region, which is populated
with text server data, site preference data, localized LOV data and metadata. The shared memory data are saved in
the backing-store files as shared memory cache.
Teamcenter uses named semaphores to coordinate and synchronize all the servers that attempt to populate shared
memory. The following figure illustrates the overall process flow of shared memory cache population.

Each server requests for the named

semaphore using a unique name

The named semaphore coordinates all the

servers and allows one server to proceed

Server creates shared memory directory

and subdirectories if they do not exist

Server creates the shared memory pool Backing-Store File

using the full path name of the backing- (e.g. tc_text.xml.mem)
store file
The backing-store file is mapped to shared
memory if it exists
Mapping Back-Store File to
Shared Memory
Check if shared memory is
initialized

Shared Memory
No Text Server Data
Site Preference Data
Populate shared data to shared memory Localized LOV Data
Mark initialization completed Metadata
Yes

Save shared memory data to backing-

store file

Server releases the named semaphore and

continues

As shown in the above figure,

1. Each server requests for a named semaphore using a unique name.
The semaphore name is unique for all the servers using the same shared memory region, and made in a
certain format in terms of the shared memory root directory name, TC_VERSION_STRING, site id, module
name and backing-store file name.

Version 1.0 Page 8 Siemens PLM Software

 The named semaphore coordinates and synchronizes all the servers that are attempting to populate shared
memory. The semaphore will allow only one server to proceed while putting other servers to the wait queue.

2. The server that is granted to proceed creates shared memory directory and shared memory module sub-
directories if they do not exist.
Shared memory modules are TextSrv, Preferences, LOV and Metadata. In a shared memory module sub-
directory, backing-store files are stored.
See Section 3.1.1 Backing-Store File Directory Structure

3. The server creates the shared memory pool (segment) using the full path name of the backing store file for a
shared memory module (e.g. TextSrv).

4. The server populates shared data to shared memory if it is not yet initialized.
Once the shared memory is populated, shared memory data is saved to the backing-store file. In the above
figure, the two actions highlighted in blue are executed only once by one server.

5. The server releases the named semaphore to allow a waiting server to proceed from Step 2.

3.1.1 Backing-Store File Directory Structure

The backing-store files for a shared memory module are stored in a directory accessible by all the collocated
Teamcenter servers and processes. The shared memory root directory and shared memory module subdirectories
are created by theTeamcenter process that is first granted to populate shared memory. The backing-store files are
created and saved also by the very first Teamcenter process.
The afore-mentioned directories and backing-store files are shared resources. The creation and update on these
shared resources are coordinated and synchronized through the same named semaphores, which are used to
coordinate and synchronize shared memory cache population.
The following figure illustrates the backing-store file directory structure.
Root Directory
The root directory is configured by the env variable: TC_SHARED_MEMORY_DIR.

TC_VERSION_STRING Sub-directory
In the root directory, a sub-directory is created using TC_VERSION_STRING, which is defined by
Teamcenter for each release version.

SiteId Sub-directory
TC_VERSION_STRING subdirectory consists of the sub-directories created using Site Id per Database

Sub-directory per shared memory module

Finally, a sub-directory is created per shared memory module: TextSrv, Preferences, LOV and Metadata.

Version 1.0 Page 9 Siemens PLM Software

 $TC_SHARED_MEMORY_DIR

TC_VERSION_STRING

SiteId

TextSrv

DefaultLocale (e.g. en_US)

tc_text.xml.mem
emh_text.xml.mem

Preferences

SharedSitePrefs.mem

LOV

LOVDictionarySegmentN.mem
LOVMasterSegment.mem

Metadata

MetadataCacheSegmentN
MetadataMasterSegment.mem

It should be noted the shared memory for LOV and Metadata supports multiple versions of shared memory data (i.e.
shared memory segments). One backing-store file is created per segment. N in the backing-store file name for a
segment represents the version number of the segment. Another backing-store file, a.k.a. Master Segment backing-
store file is created for LOV and Metadata module respectively. This backing-store file is used for tracking the version
number of the latest active shared memory segment. For the details, please refer to Section 3.4 Shared Memory for
Localized LOV Data and Section 3.5 Shared Memory for Metadata.

In Teamcenter release 11.2, the backing-store file for a segment is named as VersionN.mem, and the Master
Segment backing-store file is named as Master.mem. Shared memory for site preference data will also support
multiple versions of shared memory data. The following figure illustrates these changes.

Version 1.0 Page 10 Siemens PLM Software

 $TC_SHARED_MEMORY_DIR

TC_VERSION_STRING

SiteId

TextSrv

DefaultLocale (e.g. en_US)

tc_text.xml.mem
emh_text.xml.mem

Preferences

SharedSitePrefsN.mem
PREFMasterSegment.mem

LOV

VersionN.mem
Master.mem

Metadata

VersionN.mem
Master.mem

3.2 Shared Memory for Text Server Data

The very first Teamcenter server reads and parses the Text Server XML files for the default locale specified by the
preference: TC_language_default and populates Text Server key-value data to shared memory. Then, the server
saves shared memory Text Server data to the backing store files: tc_text.xml.mem and emh_text.xml.mem in the
default locale directory. These two backing store files represent the persistent cache for localized text strings and
error messages respectively. As long as the physical backing store files exist, they are mapped to shared memory
that is accessed by all the collocated servers to look up text server data.
After the start of the Teamcenter server process, once the client is connected to the server, a new locale might be
requested by that connection. In this case, the same process as explained above is repeated for the requested locale
if the Shared Memory cache does not yet exist.
Shared memory for text server data is read-only. This means the subsequent changes made in the Text Server XML
files are not automatically populated to shared memory. You need to manually remove the backing-store files in order
to refresh shared memory for text server data. For the details of how to refresh shared memory cache, please see
Section 4.2 Refresh Shared Memory Cache for Text Server Data.

Version 1.0 Page 11 Siemens PLM Software

3.3 Shared Memory for Site Preference Data
The very first Teamcenter server reads and parses the site preference XML data, and populates site preference data
to shared memory. Then, the server saves shared memory site preference data to the backing store file:
SharedSitePrefs.mem.
Shared memory for preferences supports the following preference data:
Site preference XML data, i.e. tc_preferences.xml and tc_solutions_preferences.xml in TC_DATA directory.
Site preference definition data from Database
Site preference value data from Database
Runtime preference definition data from Database

Shared memory for site preferences is updated by a subsequent server if any site preferences are modified after
shared memory population.

In Teamcenter release 11.2, shared memory for site preferences will be made read-only and will support
multiple versions of shared memory data.

3.4 Shared Memory for Localized LOV Data

The very first Teamcenter server retrieves entire localized LOV data in bulk from database and populates them to
shared memory. Then, the server saves shared memory localized LOV data to the backing store file.
The shared memory implementation for localized LOV data supports multiple shared memory segments for
representing multiple versions of LOV data. For this purpose, the backing-store file: LOVMasterSegment.mem
(Master.mem in Teamcenter release 11.2) is created and saved. This backing-store file stores the version number of
the latest active shared memory segment for LOV data. Each shared memory segment is created and used as
follows:
1. The very first Teamcenter server creates and populates shared memory for localized LOV data in the same
way as described in Section 3.1 Shared Memory Initialization

2. Each subsequent server that is granted to proceed retrieves the latest version number from database for
localized LOV data.

3. If the latest version number is greater than the version number cache in LOV Master segment, the server
creates a new shared memory segment using the full path name of the new backing store file.

4. The server populates latest localized LOV data to the new shared memory segment, and updates LOV
Master segment with the latest version number.

5. Each existing server will be switched to the latest shared memory segment upon its next access to shared
memory LOV data.

3.5 Shared Memory for Metadata

The very first Teamcenter server downloads metadata cache file pre-generated during install and upgrade, and maps
the cache file to shared memory. Then, the server saves shared memory metadata to the backing store file.

Version 1.0 Page 12 Siemens PLM Software

Shared memory for metadata supports the following metadata:
Types and property descriptors
Type constants and property constants

Similar to Shared Memory for Localized LOV Data, the shared memory metadata implementation also supports
multiple shared memory segments for representing multiple versions of metadata. For this purpose, the backing-store
file: MetadataMasterSegment.mem (Master.mem in Teamcenter release 11.2) is created and saved. This backing-
store file stores the version number of the latest active shared memory segment for metadata. Each shared memory
segment for metadata is created and used in the same way as it is done for Shared Memory for Localized LOV Data.

Version 1.0 Page 13 Siemens PLM Software

4 Administer Shared Memory
The detailed instructions on how to configure shared memory can be found in System Administration Guide ->
Configuring Teamcenter for performance -> Configuring the four-tier architecture for performance -> Shared
Memory. This section provides a brief description of the following tasks for administering shared memory:
1. Configure Shared Memory
You may want to configure the shared memory directory where the backing-store files are stored as shared
memory cache. Please refer to Section 3.1.1 Backing-Store File Directory Structure for details of the shared
memory directory.

Please refer to Section 4.1 Configure Shared Memory.

2. Refresh Shared Memory Cache

You may need to make sure the shared memory cache is refreshed after you make changes in TextSrv, Site
Preference, Localized LOV and Metadata.

Please refer to Section 4.2 - 4.5.

3. Clean up Semaphores
You may need to clean up semaphores that are not released by Teamcenter processes.

Please refer to Section 4.6 Clean up Semaphores.

4.1 Configure Shared Memory

You may want to set the env variable: TC_SHARED_MEMORY_DIR to specify the root directory where the backing
store files are stored. If you do not set this environment variable, the directory specified by the TEMP environment
variable on Windows is used, and the directory: /tmp on UNIX platforms is used. On Windows, if the TEMP
environment variable is not specified, the directory: C:\temp is used.
As described in Section 3.1 Populate Shared Memory Cache, the shared memory root directory name is also used for
making a unique semaphore name among all the collocated Teamcenter servers. When the env variable:
TC_SHARED_MEMORY_DIR is set to a different root directory, a new semaphore with a new name is created per
shared memory module. If the shared memory root directory is routinely set to a new location, the count of the used
semaphores could reach the UNIX OS limit. In such a scenario, the following message is logged in the Teamcenter
server syslog and the Teamcenter server reverts to its in-process memory mode.
ACE_Malloc_T<ACE_MEM_POOL_2, ACE_LOCK, ACE_CB>::ACE_Malloc_T: Not enough space

Teamcenter recommends the environment variable: TC_SHARED_MEMORY_DIR is set to a valid directory and it
should not be changed.
It should be noted in Teamcenter release 11.2, if the shared memory population fails, Teamcenter server will report
the error and not fall-back to the in-process memory mode. Specifically, one of the following errors (to name a few)
will be reported:
Unable to create pool lock

Version 1.0 Page 14 Siemens PLM Software

 67025 - An error has occurred while creating the shared memory pool lock for the "%1$" domain, so the
system cannot use shared memory for the "%1$" domain. Please report this error to your system
administrator.

In the above error message, "%1$" will be substituted on the fly with a specific shared memory module name,
e.g. LOV or Metadata

Unable to acquire the mutex

67028 - An error has occurred while acquiring the mutex for the segment "%1$-%2$". This is probably
caused by insufficient system resources. Please report this to your system administrator.

In the above error message, "%1$-%2$" will be substituted on the fly with a specific shared memory module
name and the backing-store file name respectively, e.g. Metadata - Master

The shared metadata cache is not pre-generated

273005 - The Shared Metadata Cache is out of date. The generated metadata cache dataset version %1$ is
older than the version %2$ of metadata, which is deployed in the database. Please ask your system
administrator to run generate_metadata_cache utility to re-generate metadata cache.

In the above error message, "%1$" will be substituted on the fly with the metadata cache dataset version
number, and "%2$" will be substituted on the fly with the metadata version number.

Please refer to Section 5 Troubleshoot Shared Memory Problems for the details on how to resolve these errors.

4.2 Refresh Shared Memory Cache for Text Server Data

The shared memory cache for Text Server data may become out of date if one of the following scenarios is
applicable:
1. You have applied to an existing Teamcenter installation a patch that has text server data changes.
2. New templates are installed for an existing Teamcenter installation.
3. You have modified your Text Server XML file.
4. The encoding of the Teamcenter server machine is changed.

Whenever one of the above scenarios occurs, Teamcenter recommends you manually remove the backing-store files
in the TextSrv directory (See 3.1.1 Backing-Store File Directory Structure) to refresh shared memory text server
cache. The detailed steps are as follows:

1. Ensure the system is idle.

No Teamcenter process (e.g. Teamcenter server, utility process and service process) can be running.

2. Remove the subdirectories underTextSrv

3. Re-start Teamcenter servers and service processes.

Version 1.0 Page 15 Siemens PLM Software

 After the backing-store files are removed, the first new Teamcenter process creates and populates shared
memory using the latest Text Server XML files.

4.3 Refresh Shared Memory Cache for Site Preference Data

The shared memory cache for Site Preference data may become out of date if one of the following scenarios is
applicable:
1. You have applied to an existing Teamcenter installation a patch that has site preference data changes.
2. New templates with site preference data are installed for an existing Teamcenter installation.

Whenever one of the above scenarios occurs, Teamcenter recommends you take one of the following options to
refresh shared memory preference cache.
1. Existing users can refresh preferences from RAC or may choose to relogin.

2. The system administrator can manually remove the backing-store files in the Preferences directory.

The detailed steps are as follows:

a) Ensure the system is idle.
No Teamcenter process (e.g. Teamcenter server, utility process and service process) can be running.

b) Remove the backing store file from the Preferences directory.

c) Re-start Teamcenter servers and service processes.

After the backing-store files are removed, the first new Teamcenter process creates and populates
shared memory using the latest site preference data.

4.4 Refresh Shared Memory Cache for Localized LOV Data

The shared memory cache for localized LOV data may become out of date if one of the following scenarios is
applicable:
1. New templates with localized LOV data are installed for an existing Teamcenter installation.
2. You have run live update or hot deploy in BMIDE to update localized LOV data in database
3. You have run the utility: business_model_updater to update localized LOV data in database

Whenever one of the above scenarios occurs, Teamcenter recommends you take one of the following options to
refresh shared memory cache for LOV. The first option is recommended.
1. The system administrator can start a Teamcenter server or run a utility (e.g. list_users).

The new Teamcenter process will create a new shared memory segment for the latest localized LOV data.
The existing servers will then be switched to the new shared memory segment when a subsequent access to
localized LOV data is made.

2. Existing users may choose to logout and re-login.

3. The system administrator can manually remove the backing-store files in the LOV directory.

The detailed steps are as follows:

Version 1.0 Page 16 Siemens PLM Software

 a) Ensure the system is idle.
No Teamcenter process (e.g. Teamcenter server, utility process and service process) can be running.

b) Remove the backing store file from the LOV directory.

c) Re-start Teamcenter servers and service processes.

After the backing-store files are removed, the first new Teamcenter process creates and populates
shared memory using the latest localized LOV data.

4.5 Refresh Shared Memory Cache for Metadata

The shared memory cache for metadata may become out of date if one of the following scenarios is applicable:
1. New templates are installed for an existing Teamcenter installation.
2. You have run live update or hot deploy in BMIDE to update types, property descriptors and constants.
3. You have run the utility: business_model_updater to update types, property descriptors and constants.

Note you must manually run the utility: generate_metadata_cache to generate the latest metadata cache if
you have not chosen the server cache generation option when performing the above actions.

4. You have modified TC_DATA\structure_alias.xml to configure properties for intermediate data capture (IDC)
objects in the Multi-Structure Manager.

Note you must manually run the utility: generate_metadata_cache force to generate the latest metadata
cache for the configured properties of IDC objects.

Whenever one of the above scenarios occurs, Teamcenter recommends you take one of the following options to
refresh shared memory cache for Metadata. The first option is recommended.
1. The system administrator can start a Teamcenter server or run a utility (e.g. list_users).

The new Teamcenter process will create a new shared memory segment for the latest metadata cache. The
existing servers will then be switched to the new shared memory segment when a subsequent SOA call is
made.

2. The system administrator can run the utility: shared_server_metadata_cache_mgr as a service.

This utility checks if any new metadata is deployed to database. This check is done periodically in terms of
the update interval setting specified by the preference:
TC_shared_server_metadata_cache_mgr_sleep_minutes. The default setting is 10 minutes. Once the
new metadata version is deployed to database, the utility retrieves the latest metadata from database to
generate a new shared metadata segment. The existing servers will then be switched to the new shared
memory segment when a subsequent SOA call is made.

3. Existing users may choose to logout and relogin.

4. The system administrator can manually remove the backing-store files in the Metadata directory.

The detailed steps are as follows:

Version 1.0 Page 17 Siemens PLM Software

 a) Ensure the system is idle.
No Teamcenter process (e.g. Teamcenter server, utility process and service process) can be running.

b) Remove the backing store file from the Metadata directory.

c) Re-start Teamcenter servers and service processes.

After the backing-store files are removed, the first new Teamcenter process creates and populates
shared memory using the latest localized Metadata data.

4.6 Clean up Semaphores

Shared memory functionality consumes named semaphores. On UNIX platforms, it is possible the count of the used
semaphores could reach the UNIX OS limit. In such a scenario, the following message is logged in the Teamcenter
server syslog and the Teamcenter server reverts to its in-process memory mode.

ACE_Malloc_T<ACE_MEM_POOL_2, ACE_LOCK, ACE_CB>::ACE_Malloc_T: Not enough space

When the above problem occurs, you need to clean up semaphores in the following steps:

1. Ensure the system is idle.

No Teamcenter process (e.g. Teamcenter server, utility process and service process) can be running.

2. Log on as root

3. Display the list of semaphores owned by Teamcenter by typing:

ipcs -sb | grep user-id-used-to-start-pool-manager

4. Free all the semaphores in the list by typing:

ipcrm -s ID_1... -s ID_n

ID_1 is the semaphore identifying number from the list.

After the semaphores are cleaned up, the newly-started Teamcenter processes will be able to get new semaphores
and populate or access the shared memory.

Version 1.0 Page 18 Siemens PLM Software

5 Troubleshoot Shared Memory Problems

5.1 Shared Memory Cache Are Stale

If Teamcenter processes do not pick up your latest changes in Text Server, Site Preferences, Localized LOV Data
and Metadata, shared memory cache could be stale. In this case, you need to refresh shared memory cache. For
details, please see Section 4 Administer Shared Memory.

5.2 Client Metadata Cache Are Stale

If you do not see in RAC the latest metadata changes in types, properties, icons, stylesheets, textserver data and
context menu suppression rules, you need to refresh shared memory metadata cache as described above, and also
re-generate client metadata cache by running the utility: generate_client_meta_cache log update all

5.3 Error - Shared Metadata Cache Is Out of Date

To resolve the following error, you need to run the utility: generate_metadata_cache to re-generate the new version of
metadata cache.

The shared metadata cache is not pre-generated

273005 - The Shared Metadata Cache is out of date. The generated metadata cache dataset version %1$ is
older than the version %2$ of metadata, which is deployed in the database. Please ask your system
administrator to run generate_metadata_cache utility to re-generate metadata cache.

In the above error message, "%1$" will be substituted on the fly with the metadata cache dataset version
number, and "%2$" will be substituted on the fly with the metadata version number.

5.4 Errors - Unable to Create Pool Lock and Acquire Mutex

To resolve the following errors, you need to clean up semaphores described in Section 4.6 Clean up Semaphores.
Unable to create pool lock
67025 - An error has occurred while creating the shared memory pool lock for the "%1$" domain, so the
system cannot use shared memory for the "%1$" domain. Please report this error to your system
administrator.

In the above error message, "%1$" will be substituted on the fly with a specific shared memory module name,
e.g. LOV or Metadata

Unable to acquire the mutex

67028 - An error has occurred while acquiring the mutex for the segment "%1$-%2$". This is probably
caused by insufficient system resources. Please report this to your system administrator.

In the above error message, "%1$-%2$" will be substituted on the fly with a specific shared memory module
name and the backing-store file name respectively, e.g. Metadata - Master

Version 1.0 Page 19 Siemens PLM Software

5.5 Disable Shared Memory and RAC Metadata Cache
If the shared memory population fails, or if a runtime error is suspected to be related to shared memory, you can
disable shared memory functionality and set Teamcenter process back to its in-process memory mode by setting the
following env variables at server machines except for TC_SKIP_CLIENT_CACHE

1. TC_NO_TEXTSRV_SHARED_MEMORY
Set it to TRUE to disable shared memory for text server data.

In Teamcenter release 11.2,

TC_USE_TEXTSRV_SHARED_MEMORY
Set it to FALSE to disable shared memory for text server data.

2. TC_USE_PREFS_SHARED_MEMORY
Set it to FALSE to disable shared memory for site preference data

3. TC_USE_LOV_SHARED_MEMORY
Set it to FALSE to disable shared memory for localized LOV data

4. TC_USE_METADATA_SHARED_MEMORY
Set it to FALSE to disable shared memory for metadata
If no metadata cache is pre-generated, the system will also disable shared memory for metadata. Therefore,
to disable shared memory for metadata, you may run the utility: generate_metadata_cache delete to delete
the metadata cache.

5. TC_SKIP_CLIENT_CACHE
At RAC machine, set TC_SKIP_CLIENT_CACHE=TRUE to turn off Client Metadata Cache for RAC so that
RAC will always retrieve metadata from server.

Version 1.0 Page 20 Siemens PLM Software