IBM Flex System x240 w

Failure of Log Controller:This test was conducted on a 12.5% scaled database. The following steps were successfully performed:1. The current count of the total number of orders was determined by the sum of D_NEXT_O_ID of all rows in theDISTRICT table giving SUM_1.2. A 12.5% load test was started and allowed to run and steady state was reached and maintained for over 5 minutes.3. A storage controller holding one copy of the mirrored write cache for the log was removed from the storagesubsystem. The contents of the write cache mirrors became out-of-sync. The battery attached to the controllercache was removed and and let sit for 5 minutes.4. The system was subsequently powered off.5. The storage controller from step 3 was reinserted into the storage subsystem. The controller detected the cacheout-of-sync condition and synchronized with the write cache mirror in the other controller.6. The system was powered back on and DB2 was allowed to recover.7. Step 2 was performed returning SUM_2. It was verified that SUM_2 was equal to SUM_1 plus the number ofcompleted New_Order transactions recorded by the RTE 18. Consistency condition 3 was verified.Failure of Log Disk:This test was conducted on a 12.5% scaled database. The following steps were successfully performed:9. The current count of the total number of orders was determined by the sum of D_NEXT_O_ID of all rows in theDISTRICT table giving SUM_1.10. A 12.5% load test was started and allowed to run and steady state was reached and maintained for over 5 minutes.11. One of the disks containing the transaction log was removed. Since the log was implemented as a RAID-10array, DB2 continued to process the transactions successfully.12. The test continued for at least another 5 minutes.13. The test was ended and the database was deactivated in a controlled manner.14. Step 2 was performed returning SUM_2. It was verified that SUM_2 was equal to SUM_1 plus the number ofcompleted New_Order transactions recorded by the RTE 115. Consistency condition 3 was verified.Failure of Durable Medium Containing TPC-C Database Tables:1. The contents of the database were backed up in full.2. The current count of the total number of orders was determined by the sum of D_NEXT_O_ID of all rows in theDISTRICT table giving SUM_1.3. A scaled-down test was started with 12.5% of the full load and allowed to run and steady state was reached andmaintained for over 5 minutes..4. A disk containing the TPC-C tables was removed, causing DB2 to report numerous errors.5. The system was subsequently shutdown.6. The disk was reinserted.