Professional Documents
Culture Documents
If /.profile does not already exist, use this one: PATH=/usr/bin:/usr/sbin:/usr/ucb:/usr/local/bin:/opt/VRTSvcs/bin: /sbin:$PATH export PATH . /.profile Re-verify command now runs if you changed /.profile: hastatus -summary Here is the expected result (your SYSTEMs/GROUPs may vary): One system should be OFFLINE and one system should be ONLINE ie: # hastatus -summary
-- SYSTEM STATE -- System A A e4500a e4500b State RUNNING RUNNING System e4500a e4500b Frozen 0 0 Probed Y Y AutoDisabled N N
If your systems do not show the above status, try these debugging steps:
If NO systems are up, run hastart on both systems and run hastatus -summary again. If only one system is shown, start other system with hastart. Note: one system should ALWAYS be OFFLINE for the way we configure systems here. (If we ran oracle parallel server, this could change -- but currently we run standard oracle server) If both systems are up but are OFFLINE and hastart did NOT correct the problem and oracle filesystems are not running on either system, the cluster needs to be reset. (This happens under strange network situations with GE Access.) [You ran hastart and that wasn't enough to get full cluster to work.] Verify that the systems have the following EXACT status (though your machine names will vary for other customers):
gedb002# hastatus -summary -- SYSTEM STATE -- System State Frozen
A A
gedb001 gedb002
0 0 Probed
-- GROUP STATE -- Group AutoDisabled B oragrp OFFLINE B oragrp OFFLINE gedb002# nic-qfe3 nic-qfe3
Y Y
N N
hares -display | grep ONLINE State gedb001 ONLINE State gedb002 ONLINE ID 957265489.1025.gedb002 ID 957266358.1025.gedb001
gedb002# vxdg list NAME STATE rootdg enabled gedb001# vxdg list NAME STATE rootdg enabled
Recovery Commands: hastop -all on one machine hastart wait a few minutes on other machine hastart hastatus -summary (make sure one is OFFLINE && one is ONLINE) If none of these steps resolved the situation, contact Lorraine or Luke (possibly Russ Button or Jen Redman if they made it to Veritas Cluster class) or a Veritas Consultant.
Watch failover with hastatus -summary. Once it is failed over, switch it back: hagrp -switch groupname -to system1
kill -9 process-id (the first # in list - in this case 831) Failover will take a few minutes You will note that system 2 is faulted -- and system 1 is now online You need to CLEAR the fault before trying to fail back over. hares -display | grep FAULT for the resource that is failed (in this case, LISTENER) Clear the fault hares -clear resource-name -sys faulted-system [ie: hares -clear LISTENER -sys e4500b]
oracle 987 1 0 20:49:19 ? 0:00 /apps/oracle/product/8.1.5/bin/tnslsnr LISTENER -inherit root 1330 631 0 20:58:29 pts/0 0:00 grep LISTENER
kill -9 process-id (the first # in list - in this case 987) Failover will take a few minutes You will note that system 1 is faulted -- and system 1 is now online You need to CLEAR the fault before trying to fail back over. hares -display | grep FAULT for the resource that is failed (in this case, LISTENER) Clear the fault hares -clear resource-name -sys faulted-system [ie: hares -clear LISTENER -sys e4500a] Run: hastatus -summary to make sure everything is okay.