Share

Siebel Component Showing UNAVAILABLE

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.

Possible causes:

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

Possible Solution:

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.

 

Related Definitions:

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.

4 comments on “Siebel Component Showing UNAVAILABLE”

  1. Nitin Reply

    "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."

    I am not clear what file is being reffered here Siebens.dat OR ObjMgr log ?
    If Siebns.dat file than how come it's size will increase just the parameter value will be changed in that file ?

  2. Nitin Reply

    "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."

    what I understand is Gateway server maintains all current configuration information in dynamic memory which gets flushed down to siebens.dat after particular interval of time. than how can gateway server become unresponsive inwhile that backup activity ?

  3. Rajiv Rajiv Reply

    Hi Nitin,
    Regarding the first Query:
    We are referring the siebns.dat file only. Whenever we increase the log levels it will be update in siebns.dat file (check the events information after increasing the log level at siebns.dat). If we decrease the log level it should get update in siebens.dat file and if this not happening then the it will cause the problem for those components. To make the components availale we need to follow the above steps. Syncronisation will update the latest configuration of the componets in siebns.dat file.

    Regarding the second Query:
    This not related with Gateway services. When the issue was encountered All servers are up and running fine, only those components where log levels increased in past were not responding.

    Regards,
    Rajiv.
     

  4. Aniket Reply

    Hi Rajiv,
    I have never seen any change in my siebns.dat file size after increasing log levels for any componnet  even after keeping high log level for long time (sometimes for week or two).
    My question is, as you had issue with AOM then how did Synchroize helped? 
    AOM is interactive MODE component while synchronization is required only for batch MODE components. 
    As per my understanding
    When synchronized, the server component definitions are flushed from i.e siebns.dat to S_SRM_ACTION and S_SRM_ACT_PARAM tables. and one should do it only when changes are made in batch mode components.
    Is my understanding wrong? Could you please clear my doubts?
    Thanks,
    Aniket

Leave A Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!