The Secondary database (in the SECONDARY ACTIVE state) on node 2 encounters connection failure to the Primary database (in the PRIMARY ACTIVE state) on node 1.
Recovery
In the recovery from the Primary node failure the Primary server is restarted. The recovery proceeds automatically as follows:
1 Upon the connection failure, the Secondary database moves automatically to the SECONDARY ALONE state.
2 The HAC instance on the Secondary database on node 2 concludes that the Primary database on node 1 has failed.
3 The HAC instance on the Secondary database on node 2 sets the Secondary database to the PRIMARY ALONE state.
4 The Primary node (node 1) is restarted.
5 The HAC instance on the Primary database (node 1) is restarted.
6 The HAC instance on the Primary database (node 1) concludes that the Primary database is not running.
7 The HAC instance on the Primary database (node 1) restarts the Primary database and sets it to the SECONDARY ALONE state.
8 The HAC instance on the Secondary database on node 2 initiates the process of connecting the Primary and Secondary database.
9 A catchup is made.
Optionally, the connection process includes a netcopyoperation from the Primary database to the Secondary database.