• Like
  • Save
Exadata and Oracle Database 12c
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Exadata and Oracle Database 12c

  • 250 views
Published

Oracle Database 12c Upgrade, 15.07.2014

Oracle Database 12c Upgrade, 15.07.2014

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
250
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • We identify five stages in the journey to the cloud.
    Most customers today are still mostly siloed, or in the process of standardizing their environment.
    Standardization is actually very important, and many of the benefits of moving to the cloud come from this phase.
    We want to encourage customers to standardize as much as possible, and particularly standardize on Oracle.
    We provide a single architecture that can help a customer move through the cloud stages with simple configuration changes and minimal disruption.
    Each phase delivers value of the customer, and needs to be messaged according to the customer value it delivers.
    Each phase also provides an opportunity to upsell new products.
    In the consolidation phase the key focus is on cost savings, and reducing floorspace.
    It is possible to consolidate using EE, but in this phase we want to encourage standardizing on RAC or even better our engineered systems,
    We also have an opportunity to uspell security and management options.
    In the service delivery phase we shift the focus to agility, rapid provisioning and the ability to rapidly respond to changes in business requirements.
    Things like self-service provisioning, metering and chargeback also become important.
    In the final cloud delivery phase, the focus shifts to enabling location independence and integrating the private cloud with other clouds.
    Here we have an opportunity to upsell products and services for integration.
  • Let me explain more what I mean by “engineered to work together”.
    Again each of these layers—and all the products within the layers—have been designed and engineered using open standards.
    Oracle tests everything within a stack layer and across stack layers, from applications all the way down to the servers and storage.
    Oracle then certifies all these different combinations so that customers know which particular versions of software are designed to work together and we manage and support them all together.
    But it’s more than just certification. Because this is one development organization – they are actually developing these components in concert with one another.
    (examples:
    Every night when a software team drops their code, there is integration and regression testing with the hardware systems.
    If the database team is working on a new patch, it’s also going through regression testing with the OS, the virtualization and the servers and storage.
    And then with the core infrastructure (the HW, OS and Virtualization) and with our Engineered Systems, we’re actually taking this even further. This when we don’t just certify across layers of the stack, but it’s actually pre-integrated and productized as a single system which is deployed, upgraded and supported as a single system. (We’ll cover more on ES later)
    Oracle makes it easier to deploy them together, and they are designed to be easily upgraded together.
    And, the entire stack can be managed together, and supported together.
    --------
    When we say that Oracle hardware and software is engineered to work together, this refers to our unique ability to offer customers a complete hardware and software stack, from applications through middleware and databases, and all the way down into servers and storage.
    Each of these layers—and all the products within the layers—have been designed and engineered to work together according to open standards.
    Oracle tests everything within a stack layer together– for example, between different applications, between different middleware suites, between various database products, and so on. Oracle also tests everything across stack layers, from applications all the way down to the servers and storage. So, applications are tested with middleware, middleware is tested with the database, the database is tested with the hardware … every layer is tested with every other layer.
    Oracle certifies the complete stack so that customers know which particular versions of software are designed to work together. For example, every major application that Oracle delivers, including Oracle E-Business Suite, PeopleSoft Enterprise, JD Edwards and Siebel CRM is certified with Oracle Fusion Middleware 11g . Database 11g Release 2 has been tested and certified with all of Oracle’s major applications, including Oracle Fusion Applications.
    Oracle packages our different technologies into standardized solutions, which customers can then deploy together.
    These complete solutions are designed to be upgraded effectively and efficiently together. And, the entire stack can be managed together, supported together and so on.
  • In 11.2.0.3 -> only Exadata target -> 1389592.1 - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backups
    Minimize read-only impact with multiple incremental backups
    Successive incrementals converted & applied to restored data files
    Final incremental while tablespace in read-only mode, with separate Data Pump metadata export and import
    To create the backup set containing data that must be transported to the destination database, use the BACKUP command on the source database. To indicate that you are creating a cross-platform backup, the BACKUP command must contain either the FOR
    TRANSPORT or TO PLATFORM clause.
    When you use FOR TRANSPORT, the backup set that is created can be transported to any destination database. If the destination database uses an endian format that is different from that of the source database, the endian format conversion is performed on the destination database. When you use TO PLATFORM, the endian format conversion is performed on the source database. If you specify a target platform by using TO PLATFORM, the platform must be a supported platform.
    In the source database, use the DATAPUMP clause of the BACKUP command to create the metadata required to plug tablespaces into the target database. The metadata is stored in a Data Pump export dump file as a separate backup set. This backup set can be used in conjunction with the tablespace backup set to plug the transported tablespaces into the target database.

Transcript

  • 1. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata and Oracle Database 12c
  • 2. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Silo’ed Standardize SE or EE RAC for HA, Scale EM Diag and Tuning Packs EM DB Lifecycle Mgmt. Pack Dedicated Size, deploy to need Low utilization Simplification Standard H/W Fix deployment pools Pre-deployed Consolidate Cost savings Floor space RAC or RAC One Database Vault Audit Vault Advanced Security Opt. RAT for Consolidation EM Cloud Mgmt Pack for DB (Planning) Engineered System Good Utilization Service Delivery Agility Rapid provisioning Online management EM Cloud Mgmt. Pack for DB (Prov, Chargeback) Engineered System High Utilization Cloud Pay-as-you-go Location independence Golden Gate Active Data Guard Oracle Cloud Services Oracle Virtual Assembly Builder Engineered System High Utilization Journey to Cloud
  • 3. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Pre-built and Optimized Out-of-the-Box PerformanceAchievement PerformanceAchievement Time (Days) Time (Months) 100% Measure, diagnose, tune and reconfigure Test & debug failure modes Assemble dozens of components Multi- vendor finger pointing Custom Configuration
  • 4. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Tuned Together Tested Together Certified Together Deployed Together Upgraded Together Managed Together Supported Together
  • 5. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata - One Machine | Many Workloads • Data Warehousing • Transactional Databases • Mixed Workloads • Database Consolidation • Database Cloud Mixed WorkloadsMixed Workloads Data WarehousingData Warehousing Transactional DatabasesTransactional Databases Database ConsolidationDatabase Consolidation Database CloudDatabase Cloud Public 5
  • 6. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Complete Family of Exadata Machines For OLTP, Data Warehousing and Consolidated Workloads Exadata X4-8 (8 Socket) Exadata X4-2 (2 socket) Storage Expansion Rack (Quarter, Half, Full) Public 6
  • 7. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Start With Exactly What You Need, and Grow 2Nodes 2Nodes 4Nodes 8Nodes 144Nodes 1 TB RAM* 4.8 TB Flash 24 Database Cores 18 Storage Cores 72 TB Disk 1 TB RAM* 9.6 TB Flash 48 Database Cores 36 Storage Cores 144 TB Disk 2 TB RAM* 22.4 TB Flash 96 Database Cores 84 Storage Cores 336 TB Disk 4 TB RAM* 44.8 TB Flash 192 Database Cores 168 Storage Cores 672 TB Disk 72 TB RAM* 806.4 TB Flash 3,456 Database Cores 3,024 Storage Cores 12 PB Disk Multi-RackFull RackHalf RackQuarter RackEighth Rack *With optional Memory Expansion Kits installed Public 7
  • 8. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Scale to Virtually Any Database Workload Scale up to 18 Racks with Cables and Internal Switches Scale beyond 18 Racks with External Switches Full Bandwidth and Redundancy As You Scale Public 8
  • 9. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata is the Best Platform For Consolidation • Most Exadata deployments consolidate many databases • Exadata has the unique ability to run many databases supporting multiple workloads in a single platform with extreme performance – High-end OLTP, Analytics, Batch, Reporting, Backups, etc. – All at the same time – Scalable capacity handles unpredictable workloads All Workloads, All Applications All Workloads, All Applications Sales PDB Asset s PDB Billing PDB Parts PDB
  • 10. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Enterprise Manager 12c Complete, Integrated Management Hardware View • Schematic of Storage Servers, Database Servers and IB Switches • Hardware Components Alerts Software/System View • Performance, Availability, Usage by Databases, Services, Clusters • Software Alerts DB, Cluster, ASM • Topology View of DB Systems/Clusters Configuration View • Version Summary of all Components along with Patch Recommendations Public 10
  • 11. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Database 12.1 Optimizes Exadata OLTP • Database 12.1 enhancements for Exadata are particularly focused on OLTP and Consolidation • Exadata is the best and safest platform for 12.1 Multitenant databases • Online Compression Tiering and Storage Tiering • Hybrid Columnar Compression OLTP Enhancements • Smart scans on LOBs • Enhanced Availability and Migration • SQL Performance Enhancements
  • 12. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Consolidation Methodologies • Schema Consolidation – Multiple applications share a database • Server Consolidation – Multiple databases share a server • Multi-Tenancy Newin12cNewin12c – Multiple Pluggable Databases share a Container • Virtualization – Multiple virtual machines share a single physical machine No “right” approach! Each approach has its pros and cons! Public 14
  • 13. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata Storage Server 12.1.1.1.0 • Supports Database 12c Smart Scan offload • Supports IORM for Database 12c pluggable database • Cell-to-cell Data Transfer – With Database 12c, offload data movement for ASM operations like resynchronization, resilver, and rebalance – Cells transfer data directly to destination cell without going through the database server
  • 14. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Support for Multiple DB versions on Exadata • Exadata Systems can run a mix of 11.2 and 12.1 databases • Different offload server process for each DB version – Matches DB libraries • Offload server startup/shutdown/ restarts automatic • Offload server communicates only to cellsrv DB1 (11.2) DB2 (12.1) DB3 (12.1) CELLSRV CELLOFLSRV 12.1 12.1 Offload CELLOFLSRV 11.2 11.2 Offload EXADATA STORAGE SERVER 12.1.1.1.0DB NODE 1 DB NODE 2 I/Os Smart Scans Smart Scans
  • 15. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Database 12.1 Multitenant Architecture  Transformational architecture for Database Consolidation and Cloud  Operational Cost of one database and OS, benefits of many independent databases  One database patch, upgrade, backup, standby, monitoring  Dynamically provision or upgrade a database in a few minutes  Completely Transparent - No Application Changes  Less Hardware Resources per Database – 5x for small databases Ideal for Database as a Service Many Databases each in a OS & VM Sales DB Assets DB Billing DB VM O/S Parts DB VM O/S VM O/S VM O/S Single O/S, No VMs Needed Single Multitenant Database Billing PDB Parts PDB Sales PDB Assets PDB Single Physical Container Database
  • 16. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata I/O Resource Management Mixed Workloads and Multi-Database Environment • Ensure different databases are allocated the correct relative amount of I/O bandwidth • Database A: 33% I/O resources • Database B: 67% I/O resources • Ensure different users and tasks within a database are allocated the correct relative amount of I/O bandwidth • Database A: • Reporting: 60% of I/O resources • ETL: 40% of I/O resources • Database B: • Interactive: 30% of I/O resources • Batch: 70% of I/O resources Exadata Cell InfiniBand Switch/Network Database A Database B Exadata Cell Exadata Cell
  • 17. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata Network Resource Management • OLTP workloads can degrade when network intensive reports or jobs are run – This is an especially serious issue on an unpredictable consolidated system • Exadata Network Resource Management uniquely prioritizes critical database messages through the entire fabric – Latency sensitive messages prioritized over batch, reporting, and backup messages – Log file writes have highest priority to ensure low latency transactions Network Resource Management maintains steady performance
  • 18. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | • Automatic Compression Tiering converts cooler partitions to columnar compressed format online • Global indexes maintained • HCC now has row level locking for better OLTP • Get OLTP performance of row format, with compression and reporting benefits of columnar format Automatic Compression Tiering for OLTP This Year’s Data Last Year Prior Years OLTP Frequent Reporting Compliance & Reporting 10x compressed 15x compressed Row Format is best for OLTP Column Format is best for reporting & archiving
  • 19. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Storage Tiering and Migration • New command moves database files and tablespaces to a new location online • Enables moving to a different ASM disk group • Use cases: • Move tables or partitions to different storage tier • E.g. Historical tablespaces can move from high performance to high capacity disks • Move to different mirroring • E.g move from normal redundancy to high • Move to newer hardware
  • 20. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Exadata Compression Enhancements for OLTP • 12.1 allows Hybrid Columnar Compression for tables with Spatial, and Text indexes – Enabled by Direct Load support for tables with Domain and Functional Indexes – One Oil & Gas company saw over 40X compression for a spatial table • OLTP Compression for tables with over 254 columns – Frequent request of Exadata customers
  • 21. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Availability Enhancements in ASM for Exadata • Prioritize recovery of critical files – Critical files like log files and control files are rebalanced first to reduce the chance of data loss due to double failures (e.g double disk failure) – Prioritizing important files is a big advantage over generic storage mirroring • Rebalance I/Os offloaded to Exadata – Data sent directly from cell to cell rather than through database node • Disc Resync accepts power limit to control speed – Also periodically checkpoints so that failed resyncs restart at last checkpoint End-to-End Integration to improve Availability
  • 22. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 11101 10110111101 0010100001 1001 11101 10110111101 0010100001 1001 Reduced Complexity and Downtime for DB Migration • Cross Platform Backup and Restore optimizes migration to Exadata – Endian conversion performed without staging migration files • Minimize offline or read-only impact with multiple incremental backups Source DB (Big Endian) Backup Restore Backup Destination DB – Little Endian
  • 23. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |