To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Product and version information:
Cluster networking mode:
1.The hosts and the storage array were connected through a single-path direct connection network, and the cluster environment was set up.
2.The cluster was configured with three quorum devices. A LUN was mapped from the storage array to the cluster. Two resource groups were created, and a file system was created on them. The file system was mounted to both host nodes. Data read/write operations were performed on the file system.
3.During the operations, the cluster environment was set up, and then both nodes reset (Normally, when two nodes preempt quorum devices, one node stays online while the other resets).
Do not change the default timeout value on Oracle RAC because some split-brain caused by heartbeat failures can lead to Oracle RAC VIP switchover failures. If quorum devices are unable to complete configurations within the default timeout time 25s in such an environment, replace the quorum devices.
In initial cluster deployment, perform the following steps:
1.Configure N - 1 quorum devices for the cluster where N is the number of nodes.
2.Set a higher default cluster arbitration timeout value to avoid timeouts caused by preemptions when the cluster is configured again.
This problem is a known bug and is recorded on http://wikis.sun.com/display/SunCluster/Known Bugs in Oracle Solaris Cluster 3.3
The record indicates that cluster nodes are unable to complete the arbitration within the default period (25s) after the cluster is re-configured. As a result, the nodes reset.