Expert Oracle Exadata - Parent Directory

CHAPTER 7 RESOURCE MANAGEMENTNow, this is not to imply that all resource management methods must be configured together. Youmay instead choose to use just one of the methods, or any combination of two, for managing I/O. Forexample if we had configured Category IORM alone then as illustrated in Figure 7-12, no furtherrestriction of I/O resources would be performed. I/O resources would be split at 70/30 between thecategories, APPS_CATEGORY and BATCH_CATEGORY. Similarly, you may choose to implement InterdatabaseIORM by itself, in which case I/O will be allocated strictly at a 60/80 split between sessions in the SCRATCHand SNIFF databases, respectively. If you have only one database and need to manage differingworkloads, then Intradatabase IORM is your only option. When Intradatabase IORM is used by itself, I/Ois managed according to your DBRM Plan directives alone. Figure 7-12 shows how I/O calls are allocatedas they filter through each layer of IORM.No IORMAll User IO100%CategoryIORMAPPS_CATEGORY70%BATCH_CATEGORY30%InterdatabaseIORM70%30%60% 80% 60%80%42%22.4%18%9.6%IntradatabaseIORM50%50%70%50%50%70%50%50%70%50%50%70%APPS29.4%RPTS.6.3%SCRATCHMAINT.3.15%APPS15.68%RPTS.3.36%SNIFFMAINT.1.68%APPS12.6%RPTS.2.7%SCRATCHMAINT.1.35%APPS6.72%RPTS.1.44%SNIFFMAINT.0.72%Figure 7-12. IORM method heirarchyIn Figure 7-12, allocations for the default consumer group OTHER_GROUPS and the default category OTHERare not shown, because of space constraints. In Figures 7-13, 14, and 15 we see the calculations used toallocate I/O resources as shown in Figure 7-12. The OTHER_GROUPS consumer group and OTHER categoryare shown here along with their allocation. Figures 7-13 through 7-15 shows a tabular representation ofthe resource plans along with their allocation percentage. Also displayed in these examples are theformulas used to calculate the allocation.217