New OM Processes Cannot Be Created After A Crash : Unable To Attach The Shared Memory File (Doc ID 1610084.1)

Last updated on APRIL 03, 2025

Applies to:

Symptoms

Siebel version : 8.1.1.5 SIA [21229]

Occasionally an object manager crash occurs, then when the automated creation of a new object manager process is performed - this is failing.  In fact, any new processes that then try to start on this Siebel Server, are failing to start.

See here an example from the enterprise log file:

ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:41 eCommunicationsObjMgr_enu 10551492 SBL-OSD-02006   Process 10551492 exited with error - Process exited because it received signal SIGABRT.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:50:46 Created server process (OS pid = 9437256 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:46 <NoCompName> 9437256 SBL-SVR-00027   Process 9437256 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:50:46 Created server process (OS pid = 10551494 ) for ServerMgr
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:50:46 Created server process (OS pid = 9437258 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:46 <NoCompName> 10551494 SBL-SVR-00027   Process 10551494 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:46 <NoCompName> 9437258 SBL-SVR-00027   Process 9437258 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:50:46 Created server process (OS pid = 12779534 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:46 <NoCompName> 12779534 SBL-SVR-00027   Process 12779534 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:50:46 Created server process (OS pid = 9437260 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:50:47 <NoCompName> 9437260 SBL-SVR-00027   Process 9437260 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:51:02 Created server process (OS pid = 10551502 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:51:02 <NoCompName> 10551502 SBL-SVR-00027   Process 10551502 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:51:02 Created server process (OS pid = 9437274 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:51:02 <NoCompName> 9437274 SBL-SVR-00027   Process 9437274 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:51:02 Created server process (OS pid = 12648472 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:51:02 <NoCompName> 12648472 SBL-SVR-00027   Process 12648472 exited with error - Internal: Unable to attach the shared memory file.
ServerLog ProcessCreate 1 000019c751290012:0 2013-02-25 21:51:02 Created server process (OS pid = 15335476 ) for ServerMgr
ServerLog ProcessExit 1 000019c851290012:0 2013-02-25 21:51:02 <NoCompName> 15335476 SBL-SVR-00027   Process 15335476 exited with error - Internal: Unable to attach the shared memory file.

[Continues ...]

The Siebel Server needs to be restarted, for the new Siebel processes to start successfully.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.