Oracle Open World

Oracle Open World Jim McKinstry Oracle Consulting Practice Director Bill Callahan Director, Product and Technology September 28 – October 2, 2014

Agenda • MAA Overview • Who is CCC? • Initial State Architecture • Phase 1: Introduction of Engineered Systems • Phase 2: Current State Architecture • Phase 3: The Future

Availability Service Levels for Unplanned and Planned Outages Oracle Maximum Availability Architecture (MAA) Tiers PLATINUM Zero Outage for Platinum Ready Applications Zero data loss GOLD Comprehensive HA and Disaster Protection Zero or near-zero data loss High Availability (HA) for Recoverable Local Outages Data protected as of last backup SILVER BRONZE Single Instance Database, Basic Service Restart Data protected as of last backup

Benefits of MAA with Engineered Systems for CCC • Oracle Engineered Systems significantly simplify the architecture with pre-built and pre-tested configurations. • Oracle Engineered Systems provide no single point of failure architectures. • Oracle Maximum Availability Architecture ensures best practices to minimize or eliminate unplanned and planned downtime (including rolling upgrades). • Oracle provides bundle patches that are pre-tested to minimize the risk of downtime. • MAA provides the performance and scalability to support CCC’s growth. • Oracle Engineered Systems: • Increase availability • Decrease TCO • Increase scalability • Increase performance

Who is CCC? RESTORE AND RESETTLE INTAKE OPTIMIZE EVALUATE AND REVIEW strategicparts sourcing next genscheduling total loss guided tour auditworkflow total loss next predictive open shop dispatch estimating AUTO PHYSICAL DAMAGE—INSURANCE salvage consulting intelligence INTAKE EVALUATE AND REVIEW REPAIR predictivecausation first partybill review third partybill review OPTIMIZE RESTORE AND RESETTLE OPTIMIZE REPAIR STATUS INTAKE EVALUATE AND REVIEW medicaladvisoryservices injuryevaluation predictive analytics injurycausation CASUALTY strategicparts sourcing parts procurement auditworkflow tabletestimating repairworkflow intelligence dispatch estimating status APD—Insurance Consumer Repair IS & AIS Capabilities New Opportunities

CCC 2011 Initial Environment Oracle/SUN M5000 and M4000 Servers • Cold Failover (4 hour RTS/? RPO) • Oracle 10g Database Single Instance Block SAN Storage • 30TB Combined storage across 20 databases • 45TB for Claim Folder/EDS Performance Issues • Regular Performance disruptions caused by SAN Contention • Reprocessing of customer transactions could take as much as 24 hours • Customer Portal Experience – Poor • Some queries related to search took 15-20 minutes – resulted in browser timeouts

CCC 2011 Initial Environment (cont’d) Data Warehouse • Redbrick (10TB On Disk Footprint) • ETL/Reports 6+ hours • MicroStrategy – 30+ minutes Web/Application Layer • Oracle/SUN SPARC servers (V490, E2900, M4000) • Oracle 10g SOA/OC4J Applications DR Using SAN Replication • Repurposed Load Test Systems at DR Site for DR

Exadata Implementation 2012 Migrated – X2-2 Full Rack in Prod and DR • Claim Folder • 7 SOA Dehydration Stores • Data Warehouse • 8 other application databases RAC for HA • Implemented Services for quick failover Storage reduction – 30TB Implemented Secure File LOBS • Reduced Application incidents by 60% where IO had been a bottleneck Storage Offload (Automatic!) • Portal Search < 30 seconds. Data Warehouse • 1.8TB On Disk – With HCC! • ETL/Reports < 1 hr • Microstrategy - < 5 min DR • Oracle Dataguard

Year 1 with Exadata DR – Exadata databases • Database recovery time for DR reduced from 4 hours to 30 minutes • Recovery resources reduced from 3 DBA team members to 1 DBA Patching • Goal was to get to Platinum Support Certification • Full Frame (Storage Cells, CRS, RDBMS, IB) required • Painful – requiring a 16 hour down time schedule • Bug in CRS prevented rolling CRS Patching – Caused random nodes to restart • Reluctance to perform Cell Patching rolling – due to single frame in production • Paid Off – It wasn’t for nothing! • Control File Caching to Flash Cache – Huge relief in log file sync waits • Significant buffer busy “global transaction manager” improvements • We need a local standby

Exalogic Implementation • Half Rack Exalogic • 980+ Application EARs Migrated off of OC4J • 60% overcapacity for Redundancy • Eliminated 30SPARC Servers in Production • Implemented SDP over Infiniband for communication to Exadata Databases • 40% Improvement in application Performance • DR • ZFS Storage Replication • Enables rapid provisioning of Prod Images over Load Test nodes

Exadata Implementation 2013 Local DataGuard Physical Standby • X3-2 Full Rack – Used for Primary • Implemented in 30 days RTS and RPO Improvements • 30 minute recovery (full frame switchover) • <15 minutes RPO Patching Impact • Standby first Patching option • Achieved Platinum Support Certification Performance • 20% improvement in CPU utilization • Eliminated remaining IO contention • Backups run from Standby (Must have Active DG) DR • Oracle Dataguard

Year 2-3 with Exadata Platinum Services - Patching • Directly coordinated patching with Platinum Support • Platinum will make you plan, this is a good thing. Patching • First half was painful again, but in a different way • We had a schedule, but did not complete platinum fast enough to schedule them! • They worked hard to support us, but the last minute details stung. • Local Standby masked all of it from our customers. • Second half (Happening right now!) • Planning since May • Plans have been set since 3 weeks after July Patch set • I am here, not there, which has to tell you something.

Years ? with Exadata – What is next? Storage! - We have grown • Claim folder is 104TB now Standbys • Improving RTS • Considered Logical Standby – but too many unsupported datatypes. • Tuning Data Guard to bring switchover down to 10 min. • Automating steps – Our Offshore will execute our next DR • Weblogic Active Grid Link • Implemented in phases since January 2014 • Should finish the across the board implementation as final apps move to Weblogic

Thank You

Oracle Open World