Title: RE: Recipe for application design to run on RAC

Boris,

the example I gave you is 9012 RAC and I have 5 other production systems that are 9202 RAC.  BTW remember if you have cluster_database is true, then no matter how many instances, you will see GC traffic and boy those numbers are crooked .. it is a generic problem hopefully there will be patch for it to fix the GC timing..

I think that advise should have been prefixed with something like ...
"Following statement is issued so that in case your application fails to scale contrary to our well publicized claim that RAC is extensible and scalable, we can always blame on your not-so-well-thought-rac-incompatible design. This way we will be safe and no one in media can blame us."

I am pretty sure it is hidden somewhere ...

BTW 9202 ... make sure you get all the patches ... this upgrade is a painful story (at-least for us).
Raj
______________________________________________________
Rajendra Jamadagni              MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!


-----Original Message-----
From: Boris Dali [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 04, 2002 9:19 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Recipe for application design to run on RAC


On a more serious note the following guidelines look
interesting:
http://download-west.oracle.com/docs/cd/A97630_01/rac.920/a96600/migrate.htm#1013313

"Migrate to RAC ... unless your application was
specifically designed to not use cluster database
processing".
I wonder why would somebody do that?

********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************2


Reply via email to