Operating System - HP-UX
1833737 Members
3130 Online
110063 Solutions
New Discussion

steps to be followed in change of package configuration

 
SOLVED
Go to solution
Nagarathinam
Advisor

steps to be followed in change of package configuration

Dear Forum Memebers,
I have two R380 servers and 12H autoraid box in my office.
I had already configured a package in both nodes with node1 as primary and node2 as failover and successfully working for some time. But I have also installed oracle parallel server 8i (8.1.7) on these nodes.
One of our forum member had already suggested me to place startup and shutdown of oracle instances in customer defined functions section of package control script to start and shutdown oracle instances automatically.
I had written the startup and shutdown script for oracle instances.
What are the steps with commands now I need to follow and order of execution of the same for implementing the oracle server startup and shutdown while cluster is up.

Any help is welcome and thanks in advance.

Naga
5 REPLIES 5
Nagarathinam
Advisor

Re: steps to be followed in change of package configuration

Dear Animesh,
Thank you for your reply.
I have gone through the link given by you
But I have oracle8i version 8.1.7 OPS which does not use the DLM or GMS scripts for startup or shutdown.

So Startup through DLM or GMS is not possible.

Any additional help will be valuable to me.

Bye

Naga
Nagarathinam
Advisor

Re: steps to be followed in change of package configuration

Also, I have tried the startup and shutdown in the customer defined commands through a script and made the 'cmapplyconf' to rebuild the cluster.
Now I reboot the machine, what actually happens is vg_ops is getting activated and oracle is started on node1 but it does not happen in node2.
Is there anyway other than this?

I hope for an answer.

Bye

Naga
Sanjay_6
Honored Contributor
Solution

Re: steps to be followed in change of package configuration

Hi Naga,

You have to do this.

Let us assume your package is running on node1

1.) Shutdown your package on node1
# cmhaltpkg -v packge_name

2.) Edit the package control file (/etc/cmcluster/package_name/packge_contol_file) and add the oracle startup and shutdown script to the customer defined commands.
3.) Save the file and exit.
4.) Copy this file to the other node also.
# rcp /etc/cmcluster/packge_name/packge_contol_file node2:/etc/cmcluster/packge_name/packge_contol_file
5.) If you have created a script file and have just added the name of the script file in the customer defined startup and shutdown commands, for eg.: say the script file names are /usr/local/bin/db_start and /usr/local/bin/db_shut, then copy these two files to the other node, node2.

Now start the packge on node1,
# cmmodpkg -e package_name
This should start the packge on node1. Once it is started okay, check for the faiover. To do that, shutdown the package.
# cmhaltpkg -v packge_name
On node2, start the packge,
# cmrunpkg -v package_name

Check if the database has started properly. Before doing this, check and fix the file permissions for the shell scipt files you are copying across systems.

You don't have to do a "cmapplyconf' since the cluster binaries are not affected.

Hope this helps.

Regds

Nagarathinam
Advisor

Re: steps to be followed in change of package configuration

Dear Sanjay,
Thank you for your solution.
I have done the things as requested by you and still it need a 'cmapplyconf'.
But commands in the shell script is perfectly working on cluster up but it works on the node1.
I have started the oracle server and listener on node2
through the same shell script but with 'remsh'.
It is working fine.

Thank you once again .

Bye

Naga