Siebel Object Manager Crashes if MaxMTServers and MaxTasks values do not result in a "whole number" of tasks per multi-threaded OM process
(Doc ID 485358.1)
Last updated on DECEMBER 20, 2018
Applies to:Siebel System Software - Version 7.5.3  and later
Product Release: V7 (Enterprise)
Version: 188.8.131.52  ESN
Database: Oracle 184.108.40.206
Application Server OS: HP-UX 11i
Database Server OS: HP-UX 11i
This document was previously published as Siebel SR 38-1116611751.
Customer reported the following:
We are having problems with the eCommWirelessObjMgr_esn OM crashing frequently in our Training environment (200 users).
The log errors we obtain many times are like this 'ServerLog ProcessExit 1 2003-10-27 21:06:20 eCommWirelessObjMgr_esn62958 GEN-00014 Process exited with error - Interno: no se pudo determinar el directorio local de Siebel'.
Also, in the OM log, we obtain sometimes the error 'GenericLog GenericError 1 2003-10-27 21:56:55 (smimtpool.cpp 50(883) err=2100114 sys=0) SMI-00114: El servidor de multiples subprocesos ha alcanzado el numero maximo de tareas simultaneas ((null)).'
Our OM has MaxMTServers set to 12 and MaxTasks set to 350, and never are more than 200 users at the same time, usually the number users is between 75 and 150.
After a number errors, the OM crashes and generates a core file.
In addition, when we stop the Siebel Server afther the crash and start again, we obtain errors after we remove the userpref directory in filesystem and generate a new empty userpref directory.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|