Actual commands are in black.
vxlicense -p
If any licenses are not valid or expired -- get them FIXED before continuing! All licenses should say "No expiration". If ANY license has an actual expiration date, the test failed. Permenant licenses do NOT have an expiration date. Non-essential licenses may be moved -- however, a senior admin should do this.
On either machine:
Each list should contain both machines. If not, many of the next tests will fail.
First verify that veritas is up & running:
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 State Frozen A e4500a RUNNING 0 A e4500b RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B oragrp e4500a Y N ONLINE B oragrp e4500b Y N OFFLINE
If your systems do not show the above status, try these debugging steps:
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 gedb001 RUNNING 0 A gedb002 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B oragrp gedb001 Y N OFFLINE B oragrp gedb002 Y N OFFLINE gedb002# hares -display | grep ONLINE nic-qfe3 State gedb001 ONLINE nic-qfe3 State gedb002 ONLINE gedb002# vxdg list NAME STATE ID rootdg enabled 957265489.1025.gedb002 gedb001# vxdg list NAME STATE ID rootdg enabled 957266358.1025.gedb001
Recovery Commands:
Once, hastatus -summary works, note the GROUP name used. Usually, it will be "oragrp", but the installer can use any name, so please determine it's name.
First check if group can switch back and forth. On the system that is running (system1), switch veritas to other system (system2):
On system that is OFFLINE (should be system 2 at this point), reboot the computer.
To do this, we will kill off the listener process, which should force a failover. This test SHOULD be okay for the db (that is why we choose LISTENER) but there is a very small chance things will go wrong .. hence the "pray" part :).
On system that is online (should be system2), kill off ORACLE LISTENER Process
root 1415 600 0 20:43:58 pts/0 0:00 grep LISTENER oracle 831 1 0 20:27:06 ? 0:00 /apps/oracle/product/8.1.5/bin/tnslsnr LISTENER -inherit
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.
Now we do same thing for the other system first verify that the other system is NOT faulted
On system that is online (should be system2), kill off ORACLE LISTENER Process
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
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.
Run:
Free Computer-Related Freebies - Free Software, ISP access, email, webmaster goodies, and fun stuff.
Please email additional sites, redirected/broken link info, suggestions & questions to: webmaster@unixtools.com
Pages are © Copyright 1998-2002 by UnixTools.com