I'll try again. My previous reply gave two option stop package & keep package going. Basically
o Dont stop package... You need to know how SG works and some of the methods it uses to monitor itself
o Do stop package ... this is the "safe" option if you do not know the innards of SG. Unfortunately you now need to know how to activate volume groups & alias IP to make the system look like it is up & running but without the SG monitoring options. In essence you need to know how ServiceGuard works. Which, ironically, is why you chose this option in the first place.... hmmm not nice
Given that phrases like rock & hard place come into play I'll try and give you some pointers...
Some questions that need answering & some possible investigations:
Q1- If you stop Oracle will it detect this & fail over? You MUST be certain about this, so "I think so" is not good enough.
I1 - Within ServiceGuard there is a monitor service. I've seen implementations where this is simply a script that says "while :; do; sleep; 60; done" Which basically stays alive forever. If you do "cmviewcl -v" there will be a section called "Script_parameters" beneath that a column called ITEM and a row starting with "Service". Beneath the NAME colum on the same row as "Service" is a service script, say mon_ora. This will be a script or binary that monitors your Oracle Instance. As I said above it is perfectly feasable for this to be a "dummy" or "dumb" script that always returns true. if this is the case, then stopping the Oracle instance will NOT fail over the package. If it is an intelegent script/binary then it may well have a mechanisim to "unmonitor" it... you will need to look into this.
Q2 - Assuming the answer to the above is ... "I dont know", with a pintch of "I'm not sure" or even a hint of "I'm confused & want to go home".. then Does Oracle use the floating IP adress?
I2 - The investigation for this is going to be slightly trickier, as all I know about Oracle Admin is how to spell it (but I do know about databases/Informix, so I will extrapolate). When your Oracle instance starts up it will, in general, open up ports on IP address. Sometimes the floating IP is used for this, & sometime the static host IP is used (and the application will use the floating IP & everything talks through the app). Oracle will have some listening ports/threads, and a good dba/sysadmin will put them in the /etc/services, so all you need to do is do a netstat -na | egrep
and bingo you will instantly be able to deduce if the port is on the floatring or static IP. If that option is not available, then list ALL Oracle PIDs & use glance -F to go through them all, eventually you will hit some that are the listening/poll threads & these will list the IP & ports being used.
If you do use the floating IP for Oracle, then you will be in a poor position as the only safe option is to stop the package. Activate the vgs outside of SG & ifconfig the floating IPs onto your lan cards/NICs.
vgchange -a e vgxx
mount .... (if you use mounted filesystems)
ifconfig lan0:1 x.y.z.h
:: etc ::
If you do NOT use the floating IP. Then you can stop the package & simply activate the volume groups outside of SG
vgchange -a e vgxx
mount .... (if you use mounted filesystems)
:: etc ::
I appriciate the above may be confusing, but this is the best I can do without actually logging onto your system!!!!
Regards
Tim
-
