The One-To-One database fails and the back-end hosts fail over – If the database fails and the back-end hosts fail over before the database comes back online, the BroadVision One-To-One Enterprise resources cannot come online on any cluster node. When you successfully restart the database, start the BroadVision One-To-One Enterprise resources again.
The hosts in the startup order are offline – BroadVision One-To-One Enterprise resources must be started in a particular order. The BroadVision command bvconf bootstrap lists this order. If both of the following conditions occur, the BroadVision One-To-One Enterprise processes that are configured on the hostname in the resource group will not start.
Any of the resources in the startup order are offline.
You start a BroadVision One-To-One Enterprise resource that is listed after the offline resources in the startup order.
If both of these conditions occur, the resource group will come online, but the processes will not start. The probe will wait for the resource group in the startup order to come online before the probe starts the BroadVision One-To-One Enterprise processes for this resource.
The BroadVision and Oracle resource groups fail over at the same time – If you use Oracle, and the BroadVision One-To-One Enterprise backend resource groups and the Oracle resource group fail over at the same time, some BroadVision daemons might fail to restart. These daemons will fail to restart while the Oracle database is restarting. The BroadVision One-To-One Enterprise resource will attempt to restart the failed daemons until it succeeds.