Expert Oracle Exadata - Parent Directory

CHAPTER 7 RESOURCE MANAGEMENT3. Allow the queries to run for a few minutes, and then, while they are still running, we’lldump the IORM metrics for database, category, and consumer groups to a file. Thisdata will be cleaned up and loaded into an Oracle database for reporting.Step 1: Activate Resource ManagerBefore we start the load test, we need to verify that our DAYTIME resource plan is activated in thedatabases.SYS:SCRATCH> show parameter resource_manager_planNAME TYPE VALUE------------------------------------ ----------- ------------------------------resource_manager_plan string DAYTIMESYS:SNIFF> show parameter resource_manager_planNAME TYPE VALUE------------------------------------ ----------- ------------------------------resource_manager_plan string DAYTIMEWe also need to to check our IORM Plan on each storage cell to ensure they are active.CellCLI> list iormplan detailname:catPlan:dbPlan:objective:status:enkcel03_IORMPLANname=APPS_CATEGORY,level=1,allocation=70name=BATCH_CATEGORY,level=1,allocation=30name=OTHER,level=2,allocation=100name=SCRATCH,level=1,allocation=60name=SNIFF,level=2,allocation=80name=other,level=3,allocation=100autoactiveStep 2: Start Load TestNext, we’ll start our load test by running the burn_io.sh script in eight separate terminal sessions, onefor each user account in the SCRATCH and SNIFF databases. This script is similar to the burn_cpu.sh scriptwe used to test our DBRM resource plan earlier. The script takes three parameters: USERNAME, PASSWORD,and PARALLEL. The PARALLEL parameter determines how many queries will be run concurrently. For ourtest, we’ll run three sessions from each user account. The query isselect distinct segment_name from kosborne.bigtabThe SQL script turns off output from the query, (set TERMOUT off) to reduce the overhead on thedatabase server. The bigtab table contains 194 million (repeating) rows from the dba_segments view.[enkdb02:SCRATCH] /home/rjohnson/myscripts> burn_io.sh {kosborne, tpoder, rjohnson, fred} x 3227