ServiceGuard&SAP

[Cristi_2]

Hello,

I have a cluster with two HP-UX 11.11 nodes and MC/Serviceguard. This cluster is for an SAP system (R3 Oracle).
I do not have Serviceguard Extension for SAP.
My question: Can I use both nods, for example one of them to contain SAP central instance and the other Oracle instance, or the second nod have to be a dedicated, idle backup for the primary node?

Thank you.

[Stephen Doud]

Even though you do not have the SGeSAP toolkit, you may benefit from the architecture it uses.

With SGeSAP, either a 1-package or 2-package concept can be used to facilitate SAP.
1-package: DB and CI controlled by a single package on one node, with the other node acting as a standby failover node. That node may also be operating an application server until failover is needed.

2-package: one node operates the DB package while the other node operates the CI package.

SGeSAP concepts are discussed here:
http://docs.hp.com/en/B7885-90018/B7885-90018.pdf

[Rita C Workman]

As Stephen said, you can use the second node.
Put your Oracle application into a package.

What you could do is to put a simple line in the front of your primary application (your SAP) MC/SG control file, so that when this package starts up, the first thing it does is check and see if that second Oracle package is running on THIS node...if it is- shut it down.

So in your SAP control file at the very beginning it might say:

/usr/sbin/cmhaltpkg -n $(/usr/sbin/uname -n)

Just a thought,\
Rita

[Cristi_2]

Thank you for your answers.
But....you did not read carefully my message:
I do not have Serviceguard Extension for SAP (SGeSAP).

[John Bigg]

Since you are not using the SGeSAP toolkit the implementation is up to you. Either I think would work, but you will be responsible for implementing and supporting the solution yourself since you have chosen not to use the product offering.

[Geoff Wild]

Yes you can do this - but you will have to write the scripts yourself along with any monitoring you want to do.

We used to have DB on one node and CI on the other - but had issues (mainly NFS) around that - so instead we merged them into one package.

Rgds...Geoff