Understanding the Status from Command Line Tools
Before testing the switchover, review the status of each node.
Understand the Status of the File System
The easiest way to check the status is using df.
The /datakeeper resource is attached to the node and is mounted as shown here.
Understand the Status of the Listener and Oracle Processes
We can use the ps command to review the status of each node. If the processes are running they will be listed as shown below.
$ ps afx | grep -v grep | grep tnslsnr 13806 ? Ssl 0:00 /u01/app/oracle/product/19.3.0/dbhome_1/bin/tnslsnr LISTENER1 -inherit $ ps afx | grep -v grep | grep ora_pmon 23091 ? Ss 0:00 ora_pmon_orcl
Understand the Status of the IP Resource
As discussed in How a Client Connects to the Active Node, if the IP resource is active, the virtual IP address can be found on the ip command as follows (see 10.10.10.10).
[oracle@node-b dbhome_1]$ ip addr show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 02:a8:0c:57:53:0b brd ff:ff:ff:ff:ff:ff inet 10.20.10.12/24 brd 10.20.10.255 scope global noprefixroute dynamic eth0 valid_lft 3585sec preferred_lft 3585sec inet 10.10.10.10/32 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::a8:cff:fe57:530b/64 scope link valid_lft forever preferred_lft forever
Switching the Resource Between Nodes
Show the context menu on the “orcl” resource on node-b (standby node) and select “In Service”.
First, the resource and all child dependencies will be transitioned to “StandBy” on node-a.
Once all resources are stopped on node-a, the dependencies and the “orcl” resource will be started on node-b.
Post your comment on this topic.