How To Influence Sequence of Package Start?

[Ralph Grothe]

Hello SG Wizards,

we have (amongst others) one SG cluster made up of two nodes which is heavily burdened with 14 packages consisting of really big Oracle DBs, whereof seven are configured to run on either node.
Because of DB layout (as far as I've heard from the DBAs) the packages (i.e. DBs) rely on each other.
Thus it seems to be important in what sequence the packages are started or stopped.
As it happens, this week both cluster nodes undergo some HW replacement and fiddling by HP techies on which occasion both nodes (i.e. the whole cluster) will be down simultanously.
When we then will be issueing the cmruncl command will there be a way to tell the forming cluster in exactly what sequence the packages are expected to be started?
(I guess this also applies to the cmhaltcl command).
From the manpage of cmruncl I can only see an -n option to specify the nodes involved in cluster forming (albeit, there are only 2), but nothing as far as packages are concerned.

TIA
Ralph

[CHRIS_ANORUO]

The sequence of starting the packages must have been set by your DBA in oracle startup script. Check in $ORACLE_HOME/bin/dbstart(for database start) or dbshut(for database shutdown)

[James R. Ferguson]

Hi Ralph:

Take a look at the 'cmmodpkg' command. This enables or disables the ability of a package to switch to another node upon failure of the package, and it enables or disables a particular node from running specific packages.

Regards!

...JRF...

[Rita C Workman]

Chris and James are correct.
If you want to let the packages start automatically when you bring the cluster back up...than have your DBA's ensure that they are loading correctly as Chris mentioned.
BUT...and this is one thing to consider. 14 databases, reliant on the other db being properly started..could spell a problem if one or more of them does not come up correctly.
SO..in that case you may want to interecede and apply what James suggested to shutdown the automatic startup features with the cmmodpkg option and start the databases up manually to ensure that nothing is amiss with the box or anything...
Then if everything comes up ok..maybe you would want to then attemp doing a full cluster down, and letting it start up automatically to make sure everything looks 'rosie....'

Just a thought,

[John Palmer]

Hi Ralph,

I think that you'll find that cmcld will execute the package start scripts at the same time but in the order that the packages were supplied to the cmapplyconf command. You can verify this by checking syslog or the individual package logs.

If you have any package dependencies (such as as application server requiring a database) then you will have to cater for that by coding checks into the start script.

Regards,
John