Oracle Database 12c New Features and New In Memory Database Option

2,110 views

Published on

Oracle Database 12c New Features and New In Memory Database Option - Prezentacja na Summer Tech Day - 26.08.2014 - Krzysztof Marciniak

Published in: Technology

Oracle Database 12c New Features and New In Memory Database Option

  1. 1. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Oracle Confidential – Internal 2
  2. 2. Oracle Database 12c New Features and New In Memory Database Option
  3. 3. Oracle Database In- Memory Option Powering the Real-Time Enterprise Available by end of Summer
  4. 4. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Database 12c In-Memory Option Goals • 100x Faster Queries: Real-Time Analytics • Instantaneous Queries on OLTP Database or Data Warehouse • Faster Mixed Workload OLTP • Transparent: no application changes • Simple to Implement 5
  5. 5. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Until Now Must Choose One Format and Suffer Tradeoffs Row Format Databases vs. Column Format Databases Row  Transactions run faster on row format – Example: Insert or query a sales order – Fast processing few rows, many columns Column  Analytics run faster on column format – Example : Report on sales totals by region – Fast accessing few columns, many rows SALES SALES 6
  6. 6. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Row Based Access to Data SELECT COL4 FROM MYTABLE X X X X X RESULT
  7. 7. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Column Based Access to Data COL1 COL2 COL3 COL4 X X X X X X X X X X X X X X X X X X X X SELECT COL4 FROM MYTABLE RESULT X X X X X
  8. 8. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Breakthrough: Dual Format Database • BOTH row and column formats for same table • Simultaneously active and transactionally consistent • Analytics & reporting use new in-memory Column format • OLTP uses proven row format 9 Memory Memory SALES SALES Row Format Column Format
  9. 9. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | System Global Area SGA Buffer Cache Shared Pool Redo Buffer Large Pool Other shared Memory Components In-Memory Area Configuring : In-Memory Column Store
  10. 10. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Configuring : In-Memory Column Store • Controlled by INMEMORY_SIZE parameter •Minimum size of 100MB • SGA_TARGET must be large enough to accommodate • Static Pool SELECT * FROM V$SGA; NAME VALUE ------------------ --------- Fixed Size 2927176 Variable Size 570426808 Database Buffers 4634022912 Redo Buffers 13848576 In-Memory Area 1024483648
  11. 11. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Data Positioning Storage Media Latencies DRAM 0.03ms FLASH 0.10ms DISK 30.00ms Dynamically Serve 70-90% of I/O from RAM Not to Scale
  12. 12. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | History Disk Cost per GB Year Average Cost Per Gigabyte 2013 $0.05 2010 $0.09 2005 $1.24 2000 $11.00 1995 $1,120 1990 $11,200 1985 $105,000 1980 $437,500
  13. 13. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Cost of RAM 0 1000000 2000000 3000000 4000000 5000000 6000000 7000000 1980 1985 1990 1995 2000 2005 2010 2013 Cost per Gigabit Cost per Gigabit
  14. 14. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Database In-Memory 5 Key Differentiators #1 OLTP Scales with Unique Dual Format #2 Maximum Availability is Built In #3 Database Size Isn’t Limited by Memory #4 All Applications are Transparently Compatible #5 No Personnel Needed
  15. 15. “Now we can run time-sensitive analytical queries directly against our OLTP database. This is something we wouldn’t have dreamt of earlier.” Arup Nanda Enterprise Architect Starwood Hotels and Resorts
  16. 16. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory Columnar Technology • Pure in-memory column format • Not persistent, and no logging • Quick to change data: fast OLTP • 2x to 20x compression • Enabled at table or partition level • Available on all hardware platforms 17 SALES Pure In-Memory Columnar
  17. 17. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Orders of Magnitude Faster Analytic Data Scans • Each CPU core scans local in-memory columns • Scans use super fast SIMD vector instructions • Billions of rows/sec scan rate per CPU core • Row format is millions/sec 18 VectorRegister Load multiple region values Vector Compare all values an 1 cycle CPU Memory REGION CA CA CA CA Example: Find all sales in region of CA > 100x Faster
  18. 18. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Joining and Combining Data Also Dramatically Faster • Converts joins of data in multiple tables into fast column scans • Joins tables 10x faster 19 Example: Find total sales in outlet stores SalesStores StoreID Amount Type=Outlet StoreID in 15, 38, 64 StoreID Type Sum
  19. 19. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Identifying : INMEMORY Joins • Bloom filters enable joins to be converted into fast column scans • Tried and true technology originally released in 10g • Same technique used to offload joins on Exadata
  20. 20. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Multiple Bloom Filter
  21. 21. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Generates Reports Instantly • Dynamically creates in-memory report outline • Then report outline filled-in during fast fact scan • Reports run much faster without predefined cubes 22 Example: Report sales of footwear in outlet stores Sales Stores Products In-Memory Report Outline Footwear Outlets $ $$ $ $$$ Footwear Sales Outlets
  22. 22. “Oracle Database In-Memory is a game changer for OLTP, DW, and mixed workloads. It dramatically improves the performance of all types of analytical queries.” Liviu Horn AVP Database Management McKesson Health Solutions
  23. 23. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | OLTP is Slowed Down by Analytic Indexes Insert rate decreases as more # of indexes increases
  24. 24. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Complex OLTP is Slowed by Analytic Indexes • Most Indexes in complex OLTP (e.g. ERP) databases are only used for analytic queries • Inserting one row into a table requires updating 10-20 analytic indexes: Slow! • Indexes only speed up predictable queries & reports Table 1 – 3 OLTP Indexes 10 – 20 Analytic Indexes 25
  25. 25. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Column Store Replaces Analytic Indexes • Fast analytics on any columns • Better for unpredictable analytics • Less tuning & administration • Column Store not persistent so update cost is much lower • OLTP & batch run faster Table 1 – 3 OLTP Indexes In-Memory Column Store 26
  26. 26. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Scale-Out In-Memory Database to Any Size • Scale-Out across servers to grow memory and CPUs • In-Memory queries parallelized across servers to access local column data • Direct-to-wire InfiniBand protocol speeds messaging 27
  27. 27. “Full support for RAC scale-out means Oracle Database In- Memory can be used on our largest Data Warehouse, enabling more near real-time analytics.” Sudhi Vijayakumar Senior Oracle DBA Yahoo Inc.
  28. 28. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | In-Memory Speed + Capacity of Low Cost Disk DISK PCI FLASH DRAM Cold Data Hottest Data Active Data • Size not limited by memory • Data transparently accessed across tiers • Each tier has specialized algorithms & compression • Speed of DRAM • I/Os of Flash • Cost of Disk 29
  29. 29. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Scale-Up for Maximum In-Memory Performance M6-32 Big Memory Machine 32 TB DRAM 32 Socket, 384 Cores 3 Terabyte/sec Bandwidth • Scale-Up on large SMPs • SMP scaling removes overhead of distributing queries across servers • Memory interconnect far faster than any network 30
  30. 30. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: Industrial Strength Availability RAC ASM RMAN Data Guard & GoldenGate • Pure In-Memory format does not change Oracle’s storage format, logging, backup, recovery, etc. • All Oracle’s proven availability technologies work transparently • Protection from all failures • Node, site, corruption, human error, etc. 31
  31. 31. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle Database In-Memory: Unique Fault Tolerance • Similar to storage mirroring • Duplicate in-memory columns on another node • Enabled per table/partition • Application transparent • Downtime eliminated by using duplicate after failure 32 RAC
  32. 32. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory Requires Zero Application Changes Full Functionality - No restrictions on SQL Easy to Implement - No migration of data Fully Compatible - All existing applications run unchanged Fully Multitenant - Oracle In-Memory is Cloud Ready Uniquely Achieves All In-Memory Benefits With No Application Changes 33
  33. 33. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Keys to Real-Time Data Processing • Process data in database not application • Process sets of rows using SQL • Row by row processing is slow and cannot be parallelized • Enable in-memory column format • Enable parallel SQL • Memory removes storage bottlenecks enabling highly parallel SQL 34
  34. 34. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | IMDB Technical Deep Dive
  35. 35. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Row Format Databases vs. Column Format Databases Same Data is concurrently cached in row and columnar format Row Column SALES SALES  Transactions run faster on row format – Example: Insert or query a sales order – Fast processing few rows, many columns – Full Table Scans: Not fit in SGA  Analytics run faster on column format – Example : Report on sales totals by region – Fast accessing few columns, many rows
  36. 36. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Breakthrough: Dual Format Database The IM column store is never out of date • BOTH row and column formats for same table • Simultaneously active and transactionally consistent • Analytics & reporting use new in-memory Column format • OLTP uses proven row format 37 Memory Memory SALES SALES Row Format Column Format Transaction Manager Journal
  37. 37. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store It can be enabled at the following levels: - Tablespace - Materialized View - Table - Partition (ILM) - Column
  38. 38. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |  A query that scans a large number of rows and applies filters that use operators such as the following: =, <, >, and IN  A query that selects a small number of columns from a table or materialized view with a large number of columns, such as a query that selects five columns from a table with 100 columns  A query that joins a small table to a large table  A query that aggregates data Oracle In-Memory: In-Memory Column Store Storing a database object in the IM column store can improve performance significantly for the following types of operations performed on the database object:
  39. 39. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store Compression Options: CREATE/ALTER Syntax Description NO MEMCOMPRESS The data is not compressed. MEMCOMPRESS FOR DML This method optimizes the data for DML operations and compresses IM column store data the least (excluding NO MEMCOMPRESS). MEMCOMPRESS FOR QUERY LOW This method results in the best query performance. This method compresses IM column store data more than MEMCOMPRESS FOR DML but less than MEMCOMPRESS FOR QUERY HIGH. This method is the default when the INMEMORY clause is specified without a compression method in a CREATE or ALTER SQL statement or when MEMCOMPRESS FOR QUERY is specified without including either LOW or HIGH. MEMCOMPRESS FOR CAPACITY LOW This method results in good query performance. This method compresses IM column store data more than MEMCOMPRESS FOR QUERY HIGH but less than MEMCOMPRESS FOR CAPACITY HIGH. This method is the default when MEMCOMPRESS FOR CAPACITY is specified without including either LOW or HIGH. MEMCOMPRESS FOR CAPACITY HIGH This method results in fair query performance. This method compresses IM column store data the most.
  40. 40. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | In-Memory Compression Unit • Unit of column store allocation • Target size is 1M rows • Maps on-disk extents • Actual size depends on size of row, compression factor, etc. • Updated by background populate • Contains list of Rowids • Separate CU for each column IMCU header Column CUs Extent #13 Blocks 20-120 Extent #14 Blocks 82-182 Extent #15 Blocks 201-301 EMPID NAME SALARYDEPTROWID
  41. 41. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | In-Memory Compression Unit IMCU header Column CUs Extent #13 Blocks 20-120 Extent #14 Blocks 82-182 Extent #15 Blocks 201-301 EMPID NAME SALARYDEPTROWID User Chosen Compression Level Optimize Mode Details BASIC Populate Speed No compression, fastest populate, slower queries FOR QUERY Throughput Lightweight compression, fastest queries FOR CAPACITY – LOW Balanced Fast decompress, balance between space and speed FOR CAPACITY - HIGH Space Heavier weight decompressor, optimizes for space
  42. 42. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory Column Store Compression Compression ratios can be highly inflated by choosing a bad uncompressed format, or reporting most compressible table. Our results are measured relative to Oracle’s efficient row format for 40 real tables. Excludes best and worst 10% outliers. Mode Compression Speed Range Avg. Populate 1x 1x Good Throughput 2x to 5x 3.3x Blazing Balanced 3x to 10x 5.2x Excellent Space 5x to 20x 10x Good
  43. 43. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |  Let Oracle Database control when the database object's data is populated in the IM column store (default) or  Specify a priority level that determines the priority of the database object in the population queue. Oracle SQL includes an INMEMORY PRIORITY subclause that provides more control over the queue for population. For example, it might be more important or less important to populate a database object's data before populating the data for other database objects. Oracle In-Memory: In-Memory Column Store When you enable a database object for the IM column store, you can either
  44. 44. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Defining IM Column Store Priority Use PRIORITY to define the population priority level IM Column Store T_LOW_PRIORITYT_HIGH_PRIORITY T_CRITICAL T_MEDIUM_PRIORITY FULL IMCO Wnnn Buffer Cache System Global Area SGA
  45. 45. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store Priority Options: PRIORITY NONE Oracle Database controls when the database object's data is populated in the IM column store. Population of the database object's data might be delayed if the memory required for the data is needed for other tasks. This is the default level when PRIORITY is not included in the INMEMORY clause. PRIORITY LOW The database object's data is populated in the IM column store before database objects with the priority level: NONE and after database objects with the following priority levels: MEDIUM, HIGH, or CRITICAL. PRIORITY MEDIUM The database object's data is populated in the IM column store before database objects with the priority levels NONE or LOW and after database objects with the following priority levels: HIGH or CRITICAL. PRIORITY HIGH The database object's data is populated in the IM column store before database objects with the priority levels NONE, LOW, or MEDIUM and after database objects with the following priority level: CRITICAL. PRIORITY CRITICAL The database object's data is populated in the IM column store before database objects with the following priority levels: NONE, LOW, MEDIUM, or HIGH.
  46. 46. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Managing In-Memory Population via Oracle Database Resource Manager • DBRM enhanced to manage CPU usage of IM population operations • 4 different types of IM population – INMEMORY_PREPOPULATE default consumer group ora$autotask – INMEMORY_POPULATE runs in consumer group of user accessing object – INMEMORY_REPOPULATE default consumer group ora$autotask – INMEMORY_TRICKLE default consumer group ora$autotask • If the ora$autotask consumer group doesn’t exist in resource plan, population will run in OTHER_GROUPS
  47. 47. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Managing In-Memory Population via Oracle Database Resource Manager • Possible to change consumer group for any IM population type • Use DBMS_RESOURCE_MANAGER.SET_CONSUMER_GROUP_MAPPING
  48. 48. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory Column Store Storage Index • Each column is the made up of multiple column units • Min / max value is recorded for each column unit in a storage index • Storage index provides partition pruning like performance for ALL queries 49 Memory SALES Column Format Min 1 Max 3 Min 4 Max 7 Min 8 Max 12 Min 13 Max 15 Example: Find sales from stores with a store_id of 8 or higher
  49. 49. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Monitoring In-Memory Very easy Oracle Confidential – Internal/Restricted/Highly Restricted 50 V$IM_SEGMENTS | V$IM_USER_SEGMENTS and DBA|ALL|USER_TABLES; SELECT sum(bytes) as diskSize, sum(inmemory_size) as inMemSize, sum(bytes_not_populated) as notInMemory FROM v$im_segments; SELECT sum(bytes), sum(inmemory_size), sum(bytes)/sum(inmemory_size) as compressRatio FROM v$im_segments; SELECT table_name, cache, inmemory_priority, inmemory_distribute, inmemory_compression FROM user_tables; Population has completed when column BYTES_NOT_POPULATED = 0
  50. 50. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store Initial parameters • INMEMORY_SIZE = integer [K | M | G] • INMEMORY_CLAUSE_DEFAULT = [INMEMORY] [NO INMEMORY] [other-clauses] • INMEMORY_FORCE = { DEFAULT | OFF } • INMEMORY_MAX_POPULATE_SERVERS = Half the effective CPU thread count • INMEMORY_QUERY = { ENABLE | DISABLE } Oracle Confidential – Internal/Restricted/Highly Restricted 51
  51. 51. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 1. Ensure that the database is at 12.1.0 or higher compatibility level 2. Set the INMEMORY_SIZE initialization parameter to a non-zero value 3. Increase SGA Target  IMDB is a part of that 4. When you set this parameter in a server parameter file (SPFILE) using the ALTER SYSTEM statement, you must specify SCOPE=SPFILE * The minimum setting is 100M e.g. ALTER SYSTEM SET INMEMORY_SIZE=5G SCOPE=SPFILE; 5. Increase PGA  To the SORT and GROUP BY operation did not reduce performance of IN-Memory Sort goes to disk if there's not enough PGA 6. Restart the database. 7. Put tables/partitions/columns/tablespaces in the In-Memory Column Store 8. Drop any analytic indexes that existed on the table to speed up OLTP Oracle In-Memory: In-Memory Column Store How to enable In Memory Column Store:
  52. 52. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store The following example creates the test_inmem table and enables it for the IM column store: CREATE TABLE test_inmem ( id NUMBER(5) PRIMARY KEY, test_col VARCHAR2(15)) INMEMORY; The following example enables the oe.product_information table for the IM column store: ALTER TABLE oe.product_information INMEMORY; Both examples use the defaults for the INMEMORY clause. Therefore, MEMCOMPRESS FOR QUERY is used, and PRIORITY NONE is used. Example 1 - How to put tables inside the In Memory Column Store
  53. 53. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | How to put tables inside the In Memory Column Store CREATE TABLE list_customers ( customer_id NUMBER(6) , cust_first_name VARCHAR2(20) , cust_last_name VARCHAR2(20) , cust_address CUST_ADDRESS_TYP , nls_territory VARCHAR2(30) , cust_email VARCHAR2(40)) PARTITION BY LIST (nls_territory) ( PARTITION asia VALUES ('CHINA', 'THAILAND') INMEMORY MEMCOMPRESS FOR CAPACITY HIGH, PARTITION europe VALUES ('GERMANY', 'ITALY', 'SWITZERLAND') INMEMORY MEMCOMPRESS FOR CAPACITY LOW, PARTITION west VALUES ('AMERICA') INMEMORY MEMCOMPRESS FOR CAPACITY LOW, PARTITION east VALUES ('INDIA') INMEMORY MEMCOMPRESS FOR CAPACITY HIGH, PARTITION rest VALUES (DEFAULT); Oracle Confidential – Internal/Restricted/Highly Restricted 54 ILM in Memory
  54. 54. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store This example enables some columns in the product_information table for the IM column store but not others. It also specifies different IM column store compression methods for the columns enabled for the IM column store. ALTER TABLE product_information INMEMORY MEMCOMPRESS FOR QUERY (product_id, product_name, category_id, supplier_id, min_price) INMEMORY MEMCOMPRESS FOR CAPACITY HIGH (product_descr, warranty_period, prod_status, list_price) NO INMEMORY ( weight_class, catalog_url); You can create also a tablespace or alter an existing to be cached in the In-Memory Column Store, e.g: CREATE TABLESPACE tbs1 DATAFILE 'tbs1.dbf' SIZE 40M ONLINE DEFAULT INMEMORY; Example 2 - How to put columns & tablespaces inside the In Memory Column Store
  55. 55. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Consider the following query that joins the products, customers, and times dimensions with the sales fact table: SELECT p.department_name, c.customer_id, t.fiscal_year, SUM(sales) FROM PRODUCTS p, CUSTOMERS c, TIMES t, SALES s WHERE p.product_id = s.product_id AND c.customer_id = s.customer_id AND t.time_id = s.time_id GROUP BY p.department_name, c.customer_id, t.fiscal_year; When the IM column store is configured, the Optimizer rewrites this query to use vector joins and VECTOR GROUP BY transformation. The predicates on the dimension tables PRODUCTS, CUSTOMERS, and TIMES are converted to filters on the fact table SALES. The GROUP BY is performed simultaneously with the scan of the SALES table by using in-memory arrays. Oracle In-Memory: In-Memory Column Store Vector Group By Transformation
  56. 56. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Oracle In-Memory: In-Memory Column Store Demo Statistics
  57. 57. Demo
  58. 58. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Become a Real-Time Enterprise Using Oracle Database In-Memory • Data-Driven • Get immediate answers to any question with real-time analytics • Agile • Eliminate latency with analytics directly on OLTP data • Efficient • Non-disruptively accelerate all applications 59 AGILE EFFICIENT DATA- DRIVEN
  59. 59. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Summary: Oracle Database In-Memory Powering the Real-Time Enterprise • Extreme Performance: Analytics & OLTP • Extreme Scale-Out & Scale-Up • Extreme Availability • Extreme Simplicity 60 AGILE EFFICIENT DATA- DRIVEN
  60. 60. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Virtualization out of the box Performance of an In-Memory DB Reduced OpEx and CapEx Best Security Easier Maintenance One Strong Vendor Lower Storage Costs
  61. 61. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Upgrade Services offered by Oracle • Oracle University: – Oracle Database 12c: Install and Upgrade Workshop – Oracle Database 12c: Admin, Install and Upgrade Accelerated • Database Upgrade Development Group – https://blogs.oracle.com/upgrade/  Advanced Customer Support Services: – Fixed Scope Services  Consulting Upgrade Services – Oracle Database Upgrade Services – DB12c Success Pack – DBaaS Rapid Start
  62. 62. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | For Additional Information on DB12c and IMDB Option • Oracle Database 12c Upgrade – http://www.oracle.com/technetwork/database/upgrade/overview/index.html • Oracle Database 12c New Features – http://www.oracle.com/technetwork/database/enterprise-edition/overview/index.html • Oracle Database 12c In-Memory Database Option – http://www.oracle.com/us/corporate/features/database-in-memory-option/index.html
  63. 63. Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | 65

×