Re: Real World Experience of Oracle RAC and its ability to Scale

When you talk about >4 node Oracle RAC clusters are you talking database server - or application and database server.

I understand a little more about the application architecture being proposed now.

They are attempting to create a grid architecture to manage both the application and database components. This is being done using Oracle CRS. I am being told that for CRS to be able to manage a node it must have a database instance on it and be part of the RAC cluster. However, unlike the database instance the application components are not load balanced. The only cluser management of application components appears to be to restart application components in the event of one of them failing. CRS must perform some monitoring to support this.

This seems odd to me. I would have thought OEM could perform this function, e.g. install the Oracle agent on the application server, configure it to report some custom events and create scripts/triggers within OEM to restart failed components. I actually thought OEM managed the grid environment - I wasn't aware of CRS until today.

Any thoughts appreciated,

Ian

"DA Morgan" <damorgan_at_x.washington.edu> wrote in message news:1114012181.639054_at_yasure...
> hpuxrac wrote:
>
> > Maybe it's just an english language thing. Seeing 8+ node clusters
> > doesn't mean they are in the majority or even close ... which would
> > meet the definition of typical.
>
> Not one of the RAC projects I have worked or bid on this year has been
> less than 4 nodes. So while there may be many of them ... "typical"
> does indeed have a meaning and "most" <> "typical" in English.
> --
> Daniel A. Morgan
> University of Washington
> damorgan_at_x.washington.edu
> (replace 'x' with 'u' to respond)
Received on Wed Apr 20 2005 - 11:36:06 CDT