Secondary Node Rebooted instead of falling to Ok prompt

Question

Hi all,
We need to get system backup for our clustered DB, before and after our maintenance work.
We have the following configuration:
Node #1 and Node #2
Solaris 8
SunCluster 3.0
Oracle 9.3.4
VxVM 3.2
Before issuing cluster shutdown command, I verified which node is primary.
#scstat
I issued scshutdown -y -i0 on the primary node, the secondary node rebooted instead of halting to {ok} prompt. (The primary server successfully fall to ok prompt)
When I checked on the logs on the secondary node.
May 16 08:18:41 SC[SUNW.HAStoragePlus,ttmapd-rg,tmsstor-res,hastorageplus_prenet_start_private]: Global device path /dev/vx/rdsk/tms_usr_dg01/bak_redo11_vol is not recognized as a device group or a device special file.
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost3-res,hafoip_start]: pnm_init: RPC: Rpcbind failure - RPC: Unable to receive
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost0-res,hafoip_start]: pnm_init: RPC: Rpcbind failure - RPC: Unable to receive
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost3-res,hafoip_start]: Failed to validate NAFO group name <nafo0> nafo errorcode <5>.
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost0-res,hafoip_start]: Failed to validate NAFO group name <nafo1> nafo errorcode <5>.
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost0-res,hafoip_stop]: pnm_init: RPC: Rpcbind failure - RPC: Unable to receive
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost0-res,hafoip_stop]: Failed to validate NAFO group name <nafo1> nafo errorcode <5>.
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost3-res,hafoip_stop]: pnm_init: RPC: Rpcbind failure - RPC: Unable to receive
May 16 08:18:42 SC[SUNW.LogicalHostname,ttmapd-rg,tmslhost3-res,hafoip_stop]: Failed to validate NAFO group name <nafo0> nafo errorcode <5>.
Has anyone encountered this error before.
Thank you in advance.
Regards,
Rachele

Answer 1

scshutdown gives a shutdown command on both nodes. here is the procedure.
-failover your resourcegroup to node_2
root@node_2#scswitch -z -g oracle -h node_2
you can check the status of the with scstat
-on the node which you want to backup:
root@node_1#init 0
ok boot -sx
s = single usermode
x = outside of the cluster
Once you're in single usermode, start your backup
If you wish to avoid a bunch of logging on node_2, you can always disable, or set it in maintenance, node_1 on node_2 with scconf:
root@node_2#scconf -q node=node_1,maintstate
(make sure you know what you're doing here)
to reboot node_1 and join it into the cluster:
root@node_1#umount -a
root@node_1#sync
root@node_1#reboot
ok boot (if auto-boot? is set to false)
root@node_2#scconf -q node=node_1,reset
that's it
cheers,
Kim