I know I know (he says jumping up and down) Just did the 9i New Features
class.
 
The answer is "lazy dynamic remastering". Over time, resources are gradually
moved to the instance that is using them.
 
More quotes from the manual:
   Should an instance leave the group, the background processes only
remaster resources from the departing instance.
   Similarly, when a new instance joins the group, the resources are
gradually remastered, adapting to the cluster workload.


Dennis Williams 
DBA, 40%OCP 
Lifetouch, Inc. 
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>  

-----Original Message-----
Sent: Wednesday, December 04, 2002 2:30 PM
To: Multiple recipients of list ORACLE-L


So when I access the fantasy football league on the espn web site-I go to
schema2 because my team(s) are losing :-)       I guess thats what I get
when I picked a group of guys that are all on the injured reserve
 
 
Seriously though--What if 50% of the blocks of data for schema1 are "owned"
by db2? do you eventually see where ownership is transferred to the "active"
node, reduced cache fusion activity and then transfer of blocks?  Do the
users on schema1 have to use the data on schema2 at all? I'm trying to see
if not only are the users logically partitioned-but if your schemas offer
any data partitioning to align with the schema1 and schema2....
 
thanks!
Greg
 

-----Original Message-----
Sent: Wednesday, December 04, 2002 2:05 PM
To: Multiple recipients of list ORACLE-L



Hmmmm... it is probably not an good example but we too have a (couple of)
mission critical app (affects on air production) running on 9i RAC. One of
which has two major schema. We logically partitioned the application such
that, for two groups of people 9accessing one schema each) we gave them a
preference. 

Schema1 users have tns entry for db1 and fail over to db2 
Schema2 users have a preference for db2 with a fail over to db1 

This effectively allows us to do load balance, they don't share too much
data, so traffic through interconnect is manageable. If need be, we just
shutoff listener on one side, and everyone fails over to the other side
while we can perform maintenance. All their applications are written in VB,
JAVA so they handle fail over from within application.

None of the people involved in the design worried about which side of RAC
they will be on and how the DML activity affects etc etc. They designed a
plain application with a good design and it is working fine.

Like I mentioned this is not a good example ... but this is how we did it in
one of our major application. 
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! 

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: DENNIS WILLIAMS
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to