- What's the deal on performance? I haven't heard a lot of good things.
- What is the implication of using RAC for D/R?
- Are there any issues with using RAC with Oracle integrated with SAP R/3?
- I know there are different opinions out there, but for my money most properly designed, properly configured RAC databases will not experience any significant performance issues related to RAC in and of itself. Is there overhead? Yes. But I believe that it is more than manageable given adequate hardware resources and a well-planned architecture configuration. I have supported dozens of RAC environments, and performance issues resulting from the product itself have never been a major problem.
- RAC is more of an availability solution as opposed to a disaster recovery solution in the traditional sense of the term. Yes, it allows continued operation in the event of node failure but you still have the same control file(s), the same system tablespace, etc. So a lot of your common disaster scenarios remain the same. You still need to be in archivelog mode for point in time recovery and these logs should be available to all instances. You still need disk redundancy, backups, etc. Since most RAC servers sit next to each other in the same data center, many sites opt for a combination of RAC and Data Guard (off site) for a complete availability and disaster recovery solution.
- I personally don't have experience with this but I know it is a supported solution. Here is a presentation from someone who introduced RAC into their SAP R/3 environment.