Expert Oracle Exadata - Parent Directory

CHAPTER 7 RESOURCE MANAGEMENTLIST METRICCURRENT -WHERE name like 'CG_IO_.*' -and objectType = 'IORM_CONSUMER_GROUP' -and metricObjectName like 'SCRATCH.*' -and metricObjectName not like 'SCRATCH\._.*' -ATTRIBUTES name, objecttype, metricObjectName, metricValue, collectionTime...CG_IO_LOAD IORM_CONSUMER_GROUP SCRATCH.APPS 0 …CG_IO_LOAD IORM_CONSUMER_GROUP SCRATCH.MAINTENANCE 4 …CG_IO_LOAD IORM_CONSUMER_GROUP SCRATCH.OTHER_GROUPS 4 …CG_IO_LOAD IORM_CONSUMER_GROUP SCRATCH.REPORTS 0 …...Testing IORM PlansEarlier in the chapter, we postponed testing our IORM plans. Now that you understand how to monitorIORM, we can run a stress test and take a look at the metrics collected by cellsrv to see what effect ourIORM plans had on performance. For this test, we’ll generate a load on the storage cells by runningseveral concurrent full-table scans on our SCRATCH and SNIFF databases. We’ll let them run for a fewminutes and then collect the database, category, and consumer group metrics for our test databases. Aswith our DBRM tests earlier in this chapter, validating the precise allocations for each I/O consumer is avery complicated undertaking, because any I/O resources that are allocated but unused are passed toother consumer groups, categories, and databases. This is particularly true when implementing multilevelresource plans. The focus of this test will be to verify that cellsrv is collecting metrics for eachdatabase, category, and consumer group, and that the relative I/O utilization numbers for eachconsumer group are within a reasonable range considering their resource allocations. Refer back toFigures 7-13 through 7-15 for the I/O allocations for each of our resource plans.Test OutlineNow that we've created our I/O resource plan, we can test to see how it works. Following are the stepswe will follow to test our resource plan.1. Activate the DAYTIME resource plan in the SCRATCH and SNIFF databases. Also, activatethe Database and Category IORM plans in each storage cell.2. In both databases, start three concurrent full table scans from each account thatmaps to our consumer groups. These user accounts map to the consumer groups asfollows:KOSBORNE APPSRJOHNSON REPORTSTPODER MAINTENANCEFRED OTHER_GROUPS226