Problem Summary: Due to bug 4974875, whenever autorecovery is performed, the database reinitializes itself without any spares. The mentioned bug has been fixed and integrated into HA-DB release 4.3. For HA-DB 4.2 and below releases, follow one of the procedures below to change the roles of the HA-DB nodes.
Workaround: Complete one of the following procedures to change the roles of the HA-DB nodes:
Identify the HA-DB nodes that have their roles changed after autorecovery is successful.
On all the nodes that you identified in Step 1, and one node at a time, disable the fault monitor for the HA-DB resource in question.
# cladm noderole -db dbname -node nodeno -setrole role-before-auto_recovery |
Enable the fault monitor for the HA-DB resource in question.
or
Identify the HA-DB nodes that have their roles changed after autorecovery is successful.
On all nodes that host the database, disable the fault monitor for the HA-DB resource in question.
On any one of the nodes, execute the command for each HA-DB node that needs its role changed.
# cladm noderole -db dbname -node nodeno -setrole role-before-auto_recovery |