Message XCOM Shared Memory in use during installation

Products

• XCOM Data Transport

Issue/Introduction

Performing an installation of XCOM r11.6 SP01 64 bit on a Solaris 11.4 Sparc system and received message:

# sh xcom.bin
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

===============================================================================
CA XCOM Data Transport r11.6 SP01 (64-bit)       (created with InstallAnywhere)
-------------------------------------------------------------------------------

Preparing CONSOLE Mode Installation...

===============================================================================
XCOM Shared Memory in use
-------------------------

XCOM Shared Memory is in use.
Please close all XCOM processes before proceeding for upgrade.
Installer will now exit

PRESS <ENTER> TO ACCEPT THE FOLLOWING (Exit):

Environment

Release : 11.6 SP01

Cause

The InstallAnywhere script used to install XCOM performs several pre-installation steps. In this case when it checked for the presence of the XCOM Shared Memory Segment key, it found another application running on the system that had a memory segment key of 0x19nnnn. 

Resolution

When this message is encountered you will want to issue command "ipcs | grep 0x19". If the "ipcs" command returns shared segment keys such as "0x19nnnn", then you will want to stop that application in order to perform the installation of XCOM r11.6 for Solaris.

 

Additional Information

XCOM has always used the shared segment key of '0x19' and as part of the pre-installation steps and it will check for that specific segment key on Solaris. Please issue the following commands:

ipcs | grep 0x19

ipcs -m  -- will display the Shared Memory Segments 

ipcs -s  -- will display the Semaphores

The pre-installation steps will be reviewed and changed appropriately in a future release to prevent such error when checking for the shared segment key.