XCOMU0464E Cannot create shared memory after a new Install of XCOM on Solaris
search cancel

XCOMU0464E Cannot create shared memory after a new Install of XCOM on Solaris

book

Article ID: 8346

calendar_today

Updated On:

Products

XCOM Data Transport

Issue/Introduction

XCOMU0464E Cannot create shared memory after a new Install of XCOM on Solaris 

 

Environment

CA XCOM Data Transport for Unix,

Solaris

Cause

Most of the shared memory segments were already created by various other applications. This is the reason why xcomd failed to create shared memory and in turn failed to start the service. 

Resolution

XCOM requires one shared memory segment and semaphore for its service. 

 

Evaluate all applications installed in your server and how many shared memory segments and semaphores each of the applications require. Based on that you can define the best suitable value for "project.max-shm-ids" in your production environment. 

  • Each user will be assigned to projects that contain limits defined for that user such as max shared memory ids, max shared memory etc. To find non-root users that are assigned to default projects use command "id -p". 
  • Issue the command below to identify the value of maximum shared memory ids for default project to which non-root users are assigned to. prctl -n project.max-shm-ids -i project default 
  • Use this command to check number of shared memory segments running:
    ipcs -m | grep ^m | wc -l 
  • Use this command to increase the number of shared memory segments value "project.max-shm-ids".

Remember that this value changes from project to project. Semaphores and shared memory segments consumed by each application depends on the project under which it is running i.e., based on the user who started the application.