When more and more database added to RAC, we see more and more problems.
First, when we try to add more databases to rac, we see OCR get locked, we have to wait for while to try again.
Second, when we add more listeners to RACusing netca, we can not add listener on two node at same time, each time, we have to add listener on one node ....
Third, now we can not start database with srvctl, we can start databases using sqlplus.
Not sure what next problems will be. So far, each time, when we have problems, we can find a work around. So no one cares.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
If 43 databases were single instance database that would have been okay .But you still have the problem of sharing of resources.
If out of 3 you have 40 RAC instances then you are in a big soup mate.
RAC was designed to elimnate a single point of failure and dsitribute workload your design works exactly against this a single bad program/query would bring down the entire node because of RAC now .
I sympathise with you as your option is very attractive from a management perspective but technically useless.
Better option would be to use VM and virtualize the environment and have one database per guest OS and then cluster with another host sharing resources in RAC is a very bad idea without a VM.
Bookmarks