Concurrent Processing in one of the most resources consuming Oracle e-Business Suite component. It is important to ensure a proper performance management of that components. Oracle Real Application Clusters provides Scalability and High Availability. Applications running on RAC should support certain configuration options to leverage RAC benefits. This blog posts describes possible concurrent processing configuration options and highlights EBS today’s limitations. It provides a possible solution and explains what benefits it could introduce to organizations running both EBS and RAC today.
Posted the slides of Under The Hood of Oracle Clusterware 2.0: Grid Infrastructure (UTHOC2). Updated for Oracle Database 11g Release 2.
If you are interested in the topic of ODA performance, but missed the webinar or if you want to hear it again, you can view our recording here. I also uploaded the slides to slideshare, so you can take a better look at our benchmark results and study our consolidation methods at your own pace.
RDA 4.11 is out, with a couple of new features. “Oracle Database Diagnostics Collector” (ORADDC) is one of those. It allows you to easily activate all kinds of traces, dumps, or stack collections. This may become one of the most used RDA modules for Oracle Support Services and Oracle database administrators stuck in different situations. For now, let’s start with a more basic question: “How to leverage RDA in a RAC environment ?”
Have you ever heard the one about throwing hardware at a software problem? I have this nifty RAC system that supports some very public and very mission-critical apps, and one day (it was Sunday night) it starts choking. We’re getting enqueues. Slowly they start climbing. Ten nodes came to a crashing halt. I have now seen a ten-node RAC cluster come to crashing halt and completely lock up. Why, you ask? A simple SQL statement: DELETE FROM a WHERE b=c AND d=e;.