Knowledgebase

Workaround - Failed to Bind SHMEM

Sometimes, when starting up the database, the following error(s) may be triggered:

• FSHAREMM: Failed to bind/listen on Unix domain socket for shared memory: 2
• NewUser: Unable to create an instance of a named pipe

A workaround for this issue is to switch the environmental variable that is assigned at startup to use full paths in the following areas:

• temp
• shared memory
• data

Note: ctsrvr.cfg by default uses relative paths.

Switching the environmental variable to use full paths in the above areas should fix the issue.