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!
*********************************************************************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.*********************************************************************1
