package switching enablement

[Aaron Sheard]

I have a question, when a fail-over occurs, it disables package switching on the primary node. I would like to know how, when you fail a package from one node to another, you can re-enable package switching from the command line, instead of going into sam, under package admin, modify failover options. I was hoping i can script it with cmmodpkg or something like that,,,


Thanks in advnace.

[Uday_S_Ankolekar]

Hi,
Default settings is always disabled.
To make a package autostart on its primary server when it joins a cluster,
the following must set.

1. /etc/rc.config.d/cmcluster AUTOSTART_CMCLD=1


-USA..

[A. Clay Stephenson]

Hi Aaron,

You already have your answer; cmmodpkg -e my_package.

Clay

[Uday_S_Ankolekar]

Hi again,
Aslo note that
The FAILBACK_POLICY parameter of the package configuration file should be set to AUTOMATIC
-USA..

[Aaron Sheard]

i tried cmmodpkg -e PKGNAME and it says it compelted successfuly, but if i go back into sam, the switching is off.

I get this from cmviewcl -v -p oracleNNMP

PACKAGE STATUS STATE AUTO_RUN NODE
oracleNNMP up running enabled xora000

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 3 0 oracle_NNMP
Subnet up 10.85.239.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up disabled xora001
Alternate up enabled xora000 (current)


what i want to change from the command line is switching from disabled to enabled. cmmodpkg -e didn't do it.

[Sanjay_6]

Hi Aaron,

to enable the package switching once it has failed from the primary to the secondary, you can execute this at command line,

# cmmodpkg -e package_name


this will enable the package switching for the package.

Hope this helps.

Regds

[Sudalaimani · Accepted solution]

Hi,

One time I had the same issue and resolved...try the following
1. The major thing is Check ORACLE is mounted and up and running.. (if the database is down the package will not UP).

2. Check the control log file in /etc/cmcluster/oracleNNMP/oracleNNMP_cntl_log (in your system replae oracleNNMP with package name)

3. Try with node name to force the package to switch like this..
#cmmodpakg -n -e

hope this will help U out.. In my case the oracle was down and once it is mounted the application package(autosys) was up and running so. check the database...

regards,

Sudalaimani.S

[A. Clay Stephenson]

Because the package is disabled on one of the nodes. You need to add the -n argument.

e.g.

cmmodpkg -n nodea -n nodeb -e my_package



Man cmmodpkg. It gives a pretty good description of this command.

[Jeff Schussele]

Aaron,

After the problem has been corrected on the failed server you have to run the cmmodpkg -e PKGNAME on it - as well as the current server.

Also it never hurts to use the -n NODENAME on the command line - it can save you time in not having to login to the other server.

HTH,
Jeff

[Aaron Sheard]

ahh.. the -n switch was the fix!! here are my results:


# cmmodpkg -e -n xora001 oracleNNMP
cmmodpkg : Completed successfully on all packages specified.

# cmviewcl -v -p oracleNNMP

PACKAGE STATUS STATE AUTO_RUN NODE
oracleNNMP up running enabled xora000

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Service up 3 0 oracle_NNMP
Subnet up 10.85.239.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled xora001
Alternate up enabled xora000 (current)


That's what I needed! Thanks guys!

[Sudalaimani]

The way of showing THANKS is to give points to to friends...

Thanks,
regards,

Sudalaimani.S