SBL-SVR-00026: Unable to allocate shared memory

Explanation 

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
owner account. 


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. 

Corrective Action 

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.

How to start Server Manager through Command Promt:

  • Go to command prompt.
  • Go to Siebel folder where it is installed in your machine. 
  • C:Siebel8.1.1.11.0sessiebsrvrBIN>
  • Then type srvrmgr and give appropriate parameter.

          parameter is:
   

         srvrmgr /g gatewayservername /e enterpriseservername /s siebelservername /u SADMIN            /p SADMIN

          

Steps for Clean bounce

1. Stop All Siebel Servers
· Navigate to /siebel/siebsrvr
· Run the environment file using the below command
. ./siebenv.sh
· Stop the Siebel Server using the below command
stop_server all
· Cross verify all the Servicesare gone down
Ps –ef |grep srv_sit1
2. Stop Gateway Server
· Navigate to /siebel/gtwysrvr
· Run the environment file using the below command
. ./siebenv.sh
· Stop gateway server using the below command
stop_ns
· Cross verify all the Services are gone down
Ps –ef |grep siebenv
3. Stop and start Web Server
· Navigate to /Siebel/IBMIHS/bin
· ./stopapa –> to stop the web servers
· Cross verify all the Services are gone down
ps -ef | grep httpd
· ./startapa –> to start the web servers
· Cross verify all the Services are gone down all below services should be running.
ps -ef | grep httpd
siebel 143610 250354 0 Sep 06- 0:21 /siebel/IBMIHS/bin/httpd -d /siebel/IBMIHS -k start
siebel 200718 250354 0 Sep 16- 0:18 /siebel/IBMIHS/bin/httpd -d /siebel/IBMIHS -k start
siebel 266250 250354 0 Sep 06- 0:00 /siebel/IBMIHS/bin/httpd -d /siebel/IBMIHS -k start
siebel 250354 1 0 Sep 06 – 0:13 /siebel/IBMIHS/bin/httpd -d /siebel/IBMIHS -k start
siebel 274740 250354 0 Sep 06- 0:22 /siebel/IBMIHS/bin/httpd -d /siebel/IBMIHS -k start
4. Start Gateway Server
· Navigate to /siebel/gtwysrvr
· Run the environment file using the below command
. ./siebenv.sh
· Stop gateway server using the below command
stop_ns
· Cross verify all the Services are gone down
Ps –ef |grep siebenv
5. Start Siebel Server
· Navigate to /siebel/siebsrvr
· Run the environment file using the below command
. ./siebenv.sh
· Cross verify the status of the server
list_server all
· Stop the Siebel Server using the below command
start_server all
· Cross verify all the Services are gone down
Ps –ef |grep srv_sit1
6. To start the MQ
Navigate to /home/Siebel/CRMTOOLS
Runt the bleow command
./RunAllMQTasks.sh
./mq.sh
7. To Delete webserver logs
Delete the log files
/siebel/IBMIHS/logs
access_log and error_log

Verifying the Installation Version Number for the Siebel Web Client

After installing the Siebel Web Client software, verify the version number of the installed Siebel software.
NOTE:  This topic applies to the Siebel Web Client installation, but not to the Siebel Sample Database installation.
To verify the installation version number for the Siebel Web Client
  1. Open a DOS window.
  2. Set the value of the ORACLE_HOME environment variable to correspond to your installation location, such as C:siebel8.1Client_1 or C:siebel8.2.2.0.0Client_1. For example, enter a command like this for Siebel CRM version 8.1.1:
    set ORACLE_HOME=C:siebel8.1Client_1
  3. Navigate to the opatch directory within your installation. For example, enter a command like this for Siebel CRM version 8.1.1:
    cd C:siebel8.1Client_1opatch
  4. Enter the following command:
    opatch lsinventory

Table Space Creation in Siebel
create tablespace SIEBEL_DATA
  datafile ‘/app/Administrator/oradata/siebeldb/siebel_data.dbf’ 
  size 5000m 
  autoextend on maxsize 1000m 
  extent management local 
  uniform size 128k 
  segment space management auto; 
create tablespace SIEBEL_INDEX
  datafile ‘/app/Administrator/oradata/siebeldb/siebel_index.dbf’ 
  size 5000m 
  autoextend on maxsize 1000m 
  extent management local 
  uniform size 128k 
  segment space management auto; 

                -Install the Seibel server patch file ..



Bring up command set for these path to run the patch file ..

 C:>set java_home=C:Program FilesJavajre7
 C:>set ORACLE_HOME=C:Siebel8.1.1.11.0eappweb
 C:>SET ORACLE_HOME=C:Siebel8.1.1.11.0ses

C:Siebel8.1.1.11.0sesOPatch>opatch applyE:Siebel_InstallImage14patch8.1.1.11.patchset14WindowsServerSiebel_Enterprise_Server

After successfully installation it will show ….

verifying the update…
Inventory check OK: Patch ID 8111114 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8111114 are present in Oracle Home.
OPatch succeeded.

If you want to check patch file installed or not then execute this command same cmd prompt where u did set path.

->opatch lsinventory-detail