Operating System - HP-UX
1830498 Members
2419 Online
110006 Solutions
New Discussion

To keep oracle datbase high avilable to on m/c service guard

 
naveen_6
Occasional Contributor

To keep oracle datbase high avilable to on m/c service guard

Hi,

I have M/c service guard a.11.13 on hp-ux11i on n-class server with Fc-60 disk array.I have installed oracle database on fc-60 disk array.If oracle sitting on current(system1) server fails i want oracle to start on another node configured(system2) for failover.Already i tested when oracle was not installed the failover was working perfectly.Now my question is what to be added in(ex:pkg_oltp.sh) script file so that oracle will failover to configured node.I have added oracle startup scirpt in
#vi pkg_oltp.sh

ServiceName:service1
Servicecmd:"/etc/cmcluster/pkg_oltp/orastart
But i 'm unable to get oracle started and also failover is not working and it is unable to mount filesystems.Help me.
naveen
4 REPLIES 4
Jeff Schussele
Honored Contributor

Re: To keep oracle datbase high avilable to on m/c service guard

Naveen,

First things to do are:

1) verfiy that the VG(s) can be mounted manually.
2) If they mount OK then try to execute your Oracle startup script.

If these work OK then you need the ensure that you have an Oracle shutdown script to run when you want the pkg to failover. Again. I would test that outside MC/SG.
(One of the keys to Oracle scripts is to ensure they are run by the Oracle user (EX #su - oracle -c "script") so that proper env vars exist.). By default root runs MC/SG scripts.

When everything works OK outside of MC/SG - then you can tailor the control & ascii files to mount the VGs (you'll need to make them cluster aware), run the start & stop scripts for the pkg & make sure pkq switching is enabled. Then cmhaltpkg the Oracle pkg & see if it starts properly on the other node.

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Tilok
Occasional Contributor

Re: To keep oracle datbase high avilable to on m/c service guard

Hi naveen,
i would like to suggest u to put ur oracle startup and shutdown script in package control script file, under customer defined function. ie.

function customer_defined_run_cmds
{
# ADD customer defined run commands.
su - oracle /xyz/oracle_start.sh
test_return 51
}


function customer_defined_halt_cmds
{
# ADD customer defined halt commands.
su - oracle /xyz/oracle_stop.sh
test_return 52
}

This scripts will be executed once all the VG and filesystem defined in control files are activated/deactivated.

In service command, invoke ur oracle monitoring script (to make oracle db high available) which will be demon script continusely checking health of ur databases.

Hope this will help u to make ur database 99.9999 % available.

cheers



Animesh Chakraborty
Honored Contributor

Re: To keep oracle datbase high avilable to on m/c service guard

Hi,
In my server:
SERVICE_CMD[0]="/etc/cmcluster/its_prod/its_prod.sh monitor"

I am attaching its_prod.sh scripts for your reference


Did you take a backup?
Tilok
Occasional Contributor

Re: To keep oracle datbase high avilable to on m/c service guard

hi animesh,
ur monitor script will work fine if database is open in normal state, but suppose take the following scenario

"Datafile missing/currepted while starting database"

in this case ur database will have all the background process running (ie. pmon,smon,dbwr,lgwr etc) but it will be not in open state, that means database is not available to user.

To over come this u need to modify the script to also check the status of database.

cheers.