Last updated on OCTOBER 19, 2016
Applies to:Siebel Insurance Call Center - Version 220.127.116.11  and later
Siebel CRM - Version 8.0 SIA  and later
Information in this document applies to any platform.
OEM Siebel - regss files permissions inappropriate
Question / Request / Issue: The following request was raised by the customer:
When we launch the Agent on the host where Siebel Server is running, we have the following error in the file emagent.nohup :
Aug 20, 2008 11:15:54 AM oracle.sysman.siebel.management.dbaccess.OdbcExecutor newSession
SEVERE: Start session failed. Session Id: null. Stderror stream: Can't open /tmp/regss1900002:45783.pid. Cannot initialze registry server connection data.
If we stop Siebel, and the agent stays alive, the agent recreates the file regss, with his own permission, and siebel is not able to restart.
In addition, we also got confirmation from the customer that - For security, insulation purposes they cannot run the OEM agent with the same user as the Siebel software. However they do belong to the same group.
Error While Executing Siebel Env File siebenv.sh in Solaris 10.
The Siebel install was done 2 weeks back and the services were up & running till today. There have been no config changes or permission changes that happened in the last few days to our knowledge. We were able to source env, start/stop services as late as yesterday.
Today While trying to run the Siebel environment script we get an error.
Steps to reproduce:
1. Open a putty/telnet session.
2. Execute below command:
3. The below messages are displayed:
Could not open file /tmp/Mw_sbdaaln2/4E5817A4313AD5F5E5CA1D4818E4DCB1 for shared memory.
sys_setup: mkshm() failed.
Also we are not able to navigate to the folder as the sb user - it says "Permission Denied".
How can we eliminate these errors?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms