Search This Blog

SBL-SVR-00026: Unable to allocate shared memory

Applies to:

Siebel System Software - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
Version:Siebel 7.8 and later
OS platform : All OS ( Windows as well Unix )

***Checked for relevance on 05-NOV-2012***

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SVR-00026: Unable to allocate shared memory.

Scope

This document is informational and intended for any user.

Details

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 also 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 under the "admin" directory of its root installation ($SIEBEL_ROOT\admin on both UNIX and windows). This file follows the naming convention [<$EnterpriseName>.<$ServerName>.shm]. It is built upon server startup, and destroyed upon 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 database. In this scenario, the error was reported when the user was trying to run the srvrmgr utility and was not able to connect to the database via the ODBC Datasource. To confirm, try using the srvrmgr utility and check the appropriate ServerMgr_xxxx.log files for any additional errors like: [DataDirect][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 shutting down the Siebel Gateway Server service. Check if the above .shm file is still present in spite of a successful Siebel server shutdown. After making 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 is 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 SupportWeb. Change request 12-H7JTG6 has been logged to address the product enhancement 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 more information about the Siebel Service Owner Account, refer to Siebel Bookshelf version 7.8 > Siebel Installation Guide for (Microsoft Windows or UNIX): Servers, Mobile Web Clients, Tools > Preparing for Installation > General 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 srvrmgr utility. You can follow the instructions in FAQ 1113 for further information about testing the ODBC datasource. If you have more than one Oracle client running on the Siebel Server, ensure the PATH environment variable is configured to use the correct client software based on the database version you are running. Confirm you can connect to the database using the native database tool outside of the Siebel application.





Applies to:

Siebel System Software - Version: 7.5.2 [15051] to 8.1.1 SIA [21111] - Release: V7 to V8
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 9.2.0.4
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.2

This document was previously published as Siebel SR 38-2768753981.

Symptoms

Customer reported the following:
Hi support,

during installation on my development environment, I've had some problem to start the service. I explain what I've done:

- I've created a user named "ssoa" with all permission described in the Installation Guide (chapter "Setting Permissions and Ownership");

- I've installed the Gateway and after started it,

- I've installed a Siebel Enterprise and one Siebel Server .....

but when I try to start it, I receive in the log file the following error :

021 2005-12-23 16:43:53 2005-12-23 16:44:03 +0100 00000009 001 ffff 0001 09 SiebSrvr 426124 1 /product/siebel/siebsrvr/log/SiebSrvr.log 7.8.2 [19213] ENU
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (sissrvr.cpp (2979) err=2000026 sys=17) SBL-SVR-00026: Unable to allocate shared memory.
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (scfsis.cpp (57) err=2000026 sys=0) SBL-SVR-00026: Unable to allocate shared memory.
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (listener.cpp (147) err=2000026 sys=0) SBL-SVR-00026: Unable to allocate shared memory.
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (lstnsvc.cpp (101) err=2000026 sys=0) SBL-SVR-00026: Unable to allocate shared memory.
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (scisvc.cpp (1225) err=2001045 sys=0) SBL-SVR-01045: No components are configured.
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (scfsis.cpp (166) err=2000005 sys=0) SBL-SVR-00005: Stale or invalid Task handle
GenericLog    GenericError    1    0    2005-12-23 16:43:53    (scfsis.cpp (41) err=2000029 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.
GenericLog    GenericError    1    0    2005-12-23 16:44:03    (siebsvc.cpp (221) err=2000026 sys=0) SBL-SVR-00026: Unable to allocate shared memory.

I think to have correctly followed how much described in the document "Troubleshooting Steps 24: Siebel Server Administration Troubleshooting Guide"  (Doc ID 477442.1).

Cause

The following error message was issued when trying to start the Siebel Server process:

SBL-SVR-00026: Unable to allocate shared memory
SBL-SVR-00005: Stale or invalid Task handle

The SVR-00026 error message suggests that the startup process is unable to create the .SHM shared memory file.

By executing the aix_profile .sh script available from Doc ID 477520.1, it could be noticed that this implementation was using Veritas Volume Manager. The Siebel Server opens the .SHM file for read/write in a deferred mode, by using the O_DEFER flag. It could be concluded that the VxFS file system was not able to use the O_DEFER parameter.

SBL-SVR-00005, SBL-SVR-00026, SBL-SVR-00029

Solution

For the benefit of other readers:
Consulting Veritas support, information related to this issue could be found in the Release Notes for Veritas Storage Foundation 4.0 AIX Maintenance Pack 3.
A fix was made available that enabled VxFS to not reject the O_DEFER flag when specified with an open() system call. This flag is now quietly ignored when specified.

After applying Veritas MP3, the Siebel Server started successfully.

Things to note:

_ O_DEFER pertains only to AIX

_ Working with Storage Foundation should be transparent to Siebel Applications. Although Veritas Storage Foundation is not officially supported for use with Siebel version 7.8.x, it should work.





Applies to:

Siebel System Software - Version: 8.1 [21039] to 7.5.3 [103] - Release: V8 to V7
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Cons Sec
Database: Oracle 9.2.0.2
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-1147782151.
*** Reviewed for relevance 17 Feb 2012 ***

Symptoms

Following a series of operating system I/O errors, where hardware errors were resolved, the Siebel gateway will start but the siebel server will not.

While trying to start the siebel server environment in the usual manner, the following commands were executed and error messages were returned, where "APPSRVR" is the name of the application server and "siebprd_ent" is the name of the enterprise server:

$. /siebel/siebsrvr/firstlogic.sh
siebel1@APPSRVR: /home/siebel1
$start_server all

Cleaning up previous execution of siebprd_ent::APPSRVR ...
error 2600613 (0), file ??????error 2600613 (0), file ??????%s/%s, line 621 /, line 621
Siebel Server "APPSRVR" (Enterprise "siebprd_ent")
error 2600613 (0), file ??????error 2600613 (0), file ??????%s/%s, line 621 /, line 621

$list_server -e siebprd_ent APPSRVR

error 2600613 (0), file ??????error 2600613 (0), file ??????%s/%s, line 621 /, line 621

$reset_server -e siebprd_ent APPSRVR

error 2600613 (0), file ??????error 2600613 (0), file ??????%s/%s, line 621 /, line 621

Changes

None in the Siebel environment.

Cause

Recovery from hardware failure in the Siebel environment where old shared memory files caused siebel server start failure.

Solution

Follow these steps in order to troubleshoot and resolved the issue:

1. Recreate the svc* files under $SIEBEL_ROOT\siebsrvr\sys by entering the following command line where "APPSRVR" is the name of the application server: and "siebprd_ent" is the name of the enterprise server (substitute your environment's particular values):

$siebctl -S siebsrvr -i "siebprd_ent:APPSRVR" -a -g "-g APPSRVR -e siebprd_ent -s APPSRVR"

2. Restart siebel server with the $start_server all command to see if this helps.  If another error similar to the following occurs, continue to step 3.

error Cleaning up previous execution of siebprd_ent::APPDBOU05 ...
The file /siebel/siebsrvr/sys/osdf.siebprd_ent.APPSRVR does not exist not stopped:

3. Rename the osdf file, and restart siebel server with $start_server all command.  Check any log files generated for siebel server.  If none are found, check the contents of the SiebSrvr.log enterprise log for similar messages, and if found, continue to step 4:

SBL-SVR-00029: Shared memory has not been initialized
GenericLog    GenericError    2003-12-16 21:15:27    (siebsvc.cpp 12(218) err=2000026 sys=0) SBL-SVR-00026: Unable to allocate shared memory
in siebel.log,
SBL-SVR-00031: Attached to the wrong shared memory instance

4. Remove all *.shm (old shared memory files) under the $SIEBEL_ROOT/admin directory.

Restart siebel server again with the $start_server all command.  This should result in successfully starting the server, Object Managers and other components, as well.





 



Applies to:

Siebel System Software - Version 7.7.2.6 SIA [18372] and later
z*OBSOLETE: Microsoft Windows Server 2003
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP-UX 10.0

This document was previously published as Siebel SR 38-3262290961.


Symptoms

We've installed a new server (JANBEBESBL37) for our production server farm consisting of 6 siebel servers (enterprise ES_VINP). The server runs Windows 2003 server SP1.
However, when starting the Siebel Server service, the server won't start up displaying following error messages:

GenericLog    GenericError    1    0    2007-01-30 09:34:18    (sissrvr.cpp (2979) err=2000026 sys=12) SBL-SVR-00026: Unable to allocate shared memory.

GenericLog    GenericError    1    0    2007-01-30 09:34:18    (scisvc.cpp (1225) err=2001045 sys=0) SBL-SVR-01045: No components configured !

GenericLog    GenericError    1    0    2007-01-30 09:34:18    (scfsis.cpp (166) err=2000005 sys=0) SBL-SVR-00005: Stale or invalid Task handle

GenericLog    GenericError    1    0    2007-01-30 09:34:18    (scfsis.cpp (41) err=2000029 sys=0) SBL-SVR-00029: Internal: Shared memory has not been initialized.

Cause

While carrying out tests to monitor the behaviour of the Siebel Server service at start-up, it was determined that based on a number of different variables (# of components enable; # of maxtasks per components...etc), the optimal size of a Shared Memory file is calculated.

The test Server employed for these tests was built around the Microsoft Windows 2003 Server platform and configured with 1.8GB of physical memory.
Note, at no more point during the course of these tests did the Server actually have more than 1107MB (approx 1.1GB) free – due to allocation made to the system itself as well as other underlying (non-Siebel related) processes.

Observation:
With 5 Call Center Object Managers running with Default settings (Max Tasks = 20), .shm file built in memory was 13MB
With SCCObjMgr_enu (ONLY) re-configured to support 100 Masktasks, .shm file built went up to 22.7MB;
for 500 tasks, 70MB was required; while for 5000 and 10000 tasks, 564MB of memory and 1.1GB of memory was required respectively.

**With 20000 Maxtasks enabled, the Siebel Server simply could not be starte

Solution

Resolution:

---To begin with no .shm could be created.

---After decreasing the number of max tasks set for one of the Object Managers enabled, a 650MB shared memory file was created (note: actual size on disk was 800MB), although the following error was also recorded:
ServerLog    ProcessExit    1 0 2007-03-05 03:20:21
ServerLog    ProcessExit    1 0 2007-03-05 03:20:21    ePharmaObjMgr_egr60677     SBL-SVR-00027   Process exited with error - Internal: Unable to attach the shared memory file.
--- By decreasing the number of max tasks set on several other components, it was possible to reduce the size of the .Shm file created to 640MB and also start up the Siebel Server.



Applies to:

Siebel System Software - Version 7.8.2.3 SIA [19221] to 8.2.2.2 SIA[23016] [Release V7 to V8]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Cons Goods
Database: Oracle 9.2.0.7
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3099831881.

***Checked for relevance on 15-Feb-2013***

Symptoms

Hi,

One of our Siebel Marketing Object managers and some of the components went into "Unavailable" state in production and QA environments. The object managers which are in Unavailable state are in Clustered environment.


The components which are in Unavailable state are:

Business Integration Batch Manager
Business Integration Manager
Communications Configuration Manager
Communications Inbound Processor
Communications Inbound Receiver
Communications Outbound Manager
Communications Session Manager
EAI Object Manager (ENU)
List Import Service Manager
Marketing Object Manager (ENU)
Smart Answer Manager
Workflow Process Batch Manager
Workflow Process Manager
Workflow Recovery Manager

We have verified some of the SR's and performed following activities

1. Restarted all Siebel and Gateway Servers
2. Verified disk space and resource availability
3. Ran "fsck" in the file system
4. Verified shm files
5. Verified messages in /var/adm/messages, but no significant error found
6. Compare the file sizes from the working server to the current server and there were not much differences in file sizes
7. Verified ODBC connectivity and able to connect to database from the siebsrvr/bin directory after running siebenv.sh
8. Restarted Cluster and UNIX boxes



We are getting error messages when restarting server from the command prompt

1. SBL-SCM-00018: Could not open connection to Siebel Gateway configuration store ((null):(null)).
2. SBL-SVR-00026: Unable to allocate shared memory

Attaching the log files for

1. Server Manager
2. Gateway server
3. Siebel server and
4. siebns.dat file.

Thanks and Regards

Cause

Environment specific

Solution

For the benefits of other users:

There are list of components which are in Unavailable state and enterprise log reported those components processes exited with error (as below).

ServerLog    ProcessExit    1    0    2006-07-24 09:09:11    BusIntBatchMgr 46104     SBL-GEN-00001   Process exited with error - Error code SBL-GEN-00001..

Suggest customer to execute the siebclean, cleansync, siebctl and mwcleanup command and make sure shm, osdf and svc file are deleted and then recreate the service file with siebctl command but does not help.

Suggest customer to follow the steps on Doc ID 533958.1 to direct the output on server startup for one of the failed component to the screen and upon running the server start command, the following error reported.

gma_open_file->open1: Permission denied
sys_setup: mkshm() failed.

To rectify the above

1) Make sure that the directory $SIEBEL_ROOT/admin is owned by and writable by user id used to start/stop Siebel Server services. Customer may perform a “chown –R uid:gid $SIEBEL_ROOT/siebsrvr/admin”.

2) Make sure there are sufficient spaces on /tmp or /var/tmp partition and user id used to start/stop Siebel Server services can write to these directories.

Once the above verified and corrected all component startup without issue.

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)