The Siebel Server Fault Monitor does the following every thorough_probe_interval seconds.
If the Siebel database fails, the status of the Siebel server is marked as DEGRADED. When the Siebel database restarts again, the Siebel server resource probe tries to verify that the Siebel server is functioning. When this test fails, the Siebel server is restarted or failed over to another node.
The Fault Monitor also starts the Siebel server when the Siebel database that was not available when the START method ran then becomes available.
If the Siebel gateway fails, the status of the Siebel server is marked as DEGRADED. When the Siebel gateway restarts again, the Siebel server resource probe tries to verify that the Siebel server is functioning. When this test fails, the Siebel server is restarted or failed over to another node.
The Fault Monitor also starts the Siebel server when the Siebel gateway that was not available when the START method ran then becomes available.
If the Siebel server fails, it is restarted or failed over. If any of the Siebel components fail, a partial (10%) failure is reported to the framework. Currently, component failures may be detected only in English language installations of Siebel.