Prddb service enduser prddb

Chapter 13 ■ tuning global CaChe

Why are only two instances in the cluster starving for shared pool sizes compared to the other instances? This could be an indication to look at the processes or application configured to run on these instances. The following query lists the current service-to-instance distribution:

SQL>!srvctl status service -d PRDDB
Service BCKUP: prddb7, prddb8
Service BIAPPS: prddb1, prddb2, prddb3, prddb4, prddb5,
Service BIETL: prddb6,prddb7, prddb8
Service DBAUSER: prddb1, prddb2, prddb3, prddb4, prddb5, prddb6 Service ENDUSER: prddb7, prddb8

397

Chapter 13 ■ tuning global CaChe

Step 8

From the output, it can be noticed that instances 7 and 8 are both running services BIETL; that is probably why these servers are consuming higher resources. BIETL is a highly insert-intensive data loading application. Because this is an INSERT mostly application, data sharing between other instances is much lower. This was noticed from the extremely low activity across the interconnect on other nodes in the cluster. If there are a sufficient number of servers and data can be further distributed, the additional resources required could be obtained by adding additional nodes during the time of peak load and balance resource utilization.