We faced a strange situation as components were not taking any request and component were going to “UNAVAILABLE” state. This should not happen especially for the *Application Object Manager Components.
*Note: The number defined in MinMTServer ** of the component decides how many processes will be started when the component will start.Component is in unavailable state means that application server is running but no precess is running for the component.
We have file called Siebns.dat which use to keep the complete enterprise information.
· Whenever we increase the log level for Object Manager to 4 or 5 and kept long for few days, all the events information will be written into siebns.dat file and the size of the file will grow.
· Sometimes it depends upon the large number of components using in the enterprise and increase the log level for all of them.
That means even if we reset evtloglvl to 1, the corresponding entries in siebns.dat will persist and you are unable to shrink size of siebns.dat anymore. It can take significant time to copy the siebns.dat to the backup files and as long as this is being done, the gateway is unresponsive.
Means after decreasing the log level to 1 if we bounce the component or the server this problem will be occur. Even if we bounce make sure you have waited for some time (Exactly no idea) to get update the siebns.dat file. Even if you increase the log level to check the same it will not help you because the component will go to unavailable state. We received only one Siebel Error code SBL-GEN-00001
We need to perform the below activities
· Unassigned the component group from server
· Synchronize component
· Assign the component group to respective server
· Synchronize component
· Bounce the server
We have tested the same at our end where it is working fine and the component is coming to online & running state and processing the request.
Min MT Servers. The default number of multithreaded Siebel Server processes that are started for a component that has multithreading enabled. These processes are brought up when the component is started explicitly through the Siebel Server Manager, or when the Siebel Server is started (if the component state was last set to Running). Additional multithreaded Siebel Server processes are started as needed (namely, when the maximum number of threads that may run in a Siebel Server process has been reached), up to the value of the Max MT Servers parameter. Setting this parameter to 0 disables the component.