SG A11.18 and Oracle 10g

[Delcho Tuhchiev]

Hi,
I've 2 node SG cluster running on HP-UX 11.23.
On each node I've running 1 package ( Oracle 10g DB). The summ. of SGA of both Oracle instances is larger than the ammount of memmory on each node and this mean that I can not run both packages on one node...
So in case of failover I do not need "performance" I need availability and in this direction... Can I automaticaly manage Oracle SGA during failover (when package fails over and both packages should run on one node to start failed package with SGA reduction)

[Steven E. Protter]

Shalom,

You say:
this mean that I can not run both packages on one node

SEP: This means you should not run both packages on one node. You can try with poor results.

Answer: Yes, you will need to over-write the oracle configuration file that includes the SGA as part of your package start script.

SEP

[Delcho Tuhchiev]

Hi SEP

This is obvious.... Perhaps wright question is:
Is there any standart mechanism (or way) in SG which provides me information that both packages try to run on one node and in that case to perform a "custom" action? Or I need to write a custom start/stop scrip for packages (now I use SG-Oracle-Tookit )

BR,

Delcho

[TwoProc · Accepted solution]

I've got the toolkit as well, and I've never seen anything like what you're talking about. However, I don't believe adding a custom script to the startup command to see what packages are active is much of a problem, and then base a change in the init.ora file on this.

But, what if you're moving a package onto a server, and the server already has one package up? This means that the first package has a normal full acess to all its resources, and the second package has to handle the reduction that you would normally seek from the reducing both packages.

You've got some scenarios
a) Package A is up and Package B comes over. Package B takes the hit in performance due to limited ram allocations
b) Package B is up and Package A comes over, Package A takes the hit in performance due to limited ram allocation.
c) is you're moving both. I don't see this an an option really, as no matter "fast" you do it, its not bringing up two packages at once, but one after the other. So, if the packages "self-sense" information about the other package being "up", then somebody is always second.

[Delcho Tuhchiev]

.