SBL-SVR-00026: Unable to allocate shared memory
The above error message is reported in the log files when the Siebel server
fails to start up. In most cases, one or more additional error messages al
so accompany this one, for example SBL-SVR-00005.
These errors might be reported for the following known reasons:
There is a shared memory file that is maintained by each Siebel server unde
r the “admin” directory of its root installation ($SIEBEL_ROOTadmin on bot
h UNIX and windows). This file follows the naming convention [<$EnterpriseN
ame>.<$ServerName>.shm]. It is built upon server startup, and destroyed upo
n shutdown. If this file cannot be created successfully upon server startup
, the above error message can be reported. Possible reasons for this file
to not be created successfully are:
1. The clean up routine upon shutdown did not clean this file possibly
because of an abnormal termination of the Siebel server service.
2. Possible disk space issues are preventing the creation of this file.
3. Lack of permissions on this directory or folder or file by the service
4. The wrong Oracle client for example a version 8 client which is running
on the Siebel Server is being used to connect to an Oracle version 9 databa
se. In this scenario, the error was reported when the user was trying to ru
n the srvrmgr utility and was not able to connect to the database via the O
DBC Datasource. To confirm, try using the srvrmgr utility and check the app
ropriate ServerMgr_xxxx.log files for any additional errors like: [DataDire
ct][ODBC Oracle driver][Oracle]ORA-24316: illegal handle type.
For the above known behaviors, try the following corrective steps:
1. Make sure the Siebel Server service(s) are shutdown completely before sh
utting down the Siebel Gateway Server service. Check if the above .shm file
is still present in spite of a successful Siebel server shutdown. After ma
king a copy of the old *.shm (if it was left behind after a server shutdown
), delete it and restart the service, and verify whether a new *.shm file i
s created and if that allowed the server to start up properly.
2. Provide for ample disk space and comply with the memory requirements of
a typical Siebel installation. For more information refer to the appropriate
System Requirements and Supported Platforms Guide (SRSP) located on Suppo
rtWeb. Change request 12-H7JTG6 has been logged to address the product enha
ncement request of checking for available disk space before starting the server.
3. Grant necessary privileges and permissions to the Siebel Server service
owner account. NOTE: The following bookshelf version is also applicable to
the version listed in the header of this error message documentation. For m
ore information about the Siebel Service Owner Account, refer to Siebel Boo
kshelf version 7.8 > Siebel Installation Guide for (Microsoft Windows or UN
IX): Servers, Mobile Web Clients, Tools > Preparing for Installation > Gene
ral Considerations in Planning Your Siebel Deployment > Creating the Siebel
Service Owner Account.
4. Make sure you are using the correct ODBC datasource when running the srv
rmgr utility. You can follow the instructions in FAQ 1113 for further infor
mation about testing the ODBC datasource. If you have more than one Oracle
client running on the Siebel Server, ensure the PATH environment variable i
s configured to use the correct client software based on the database versi
on you are running. Confirm you can connect to the database using the nativ
e database tool outside of the Siebel application.