Siebel Service does not start on a specific cluster node and fails with SBL-SMI-00061 error (Doc ID 1909112.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.5 SIA [21229] and later
Information in this document applies to any platform.

Symptoms

Siebel Enterprise is installed on MS Cluster with two clustered Siebel Servers.

When the Siebel Server is failed over to a specific node, it fails with the following error:

        SBL-SVR-00026: Unable to allocate shared memory

In Process Monitor log file captured during the attempt to start the Siebel Server on the problematic node it was captured the following:

 

Process Name PID Operation Path Result Detail Date & Time Image Path User Command Line TID Parent PID Session

siebsvc.exe 9952 CreateFileMapping J:\SBA81\siebsrvr\ADMIN\SIEB_PRD_RUS.SS_PRD_RUS_5.shm FILE LOCKED WITH WRITERS SyncType: SyncTypeCreateSection, PageProtection: PAGE_READWRITE 6/13/2014 15:48 J:\SBA81\siebsrvr\BIN\siebsvc.exe JTICORP\Z_GVASIEBEL8PROD J:\SBA81\siebsrvr\BIN\siebsvc -s siebsrvr -i SIEB_PRD_RUS_SS_PRD_RUS_5 -a "-g TME_RUS_PRD_SGW:2320 -e SIEB_PRD_RUS -s SS_PRD_RUS_5 -l ENU -u Z_GVASIEBDB8PROD -ep 5AtSf5wjvbGIhT09yA==" -t 120 -h J:\SBA81\siebsrvr   14832 888 0

siebsvc.exe 13068 CreateFileMapping J:\SBA81\siebsrvr\ADMIN\SIEB_PRD_RUS.SS_PRD_RUS_5.shm FILE LOCKED WITH WRITERS SyncType: SyncTypeCreateSection, PageProtection: PAGE_READWRITE 6/13/2014 15:48 J:\SBA81\siebsrvr\BIN\siebsvc.exe JTICORP\Z_GVASIEBEL8PROD J:\SBA81\siebsrvr\BIN\siebsvc -s siebsrvr -i SIEB_PRD_RUS_SS_PRD_RUS_5 -a "-g TME_RUS_PRD_SGW:2320 -e SIEB_PRD_RUS -s SS_PRD_RUS_5 -l ENU -u Z_GVASIEBDB8PROD -ep 5AtSf5wjvbGIhT09yA==" -t 120 -h J:\SBA81\siebsrvr   13820 888 0


When the problematic Siebel Server was manually started from command-prompt (foreground mode) using the following syntax:

         J:\SBA81\siebsrvr\siebsrvr /g <gateway_server_hostname>:<port#> /e <enterprise_name> /s <siebel_server_name> /u SADMIN /p <password>

The following error could be encountered:

         SBL-SMI-00061 The directory Admin, does not exist under the Siebel root directory

In the cluster setup review, it was found that "use network name for computer name" checkbox was not checked for the problematic Siebel Server service.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms