Enterprise Manager DBaaS : Database, Schema, or Terabytes of Data in Minutes

2. Enterprise Manager DBaaS: Database, Schema, or Terabytes of Data in Minutes ShaileshDwivedi Director Product Management

3. Description Session: CON1719 Title: Oracle Enterprise Manager DBaaS: Database, Schema, or Terabytes of Data in Minutes Description: Database as a service (DBaaS) is the latest trend in providing automated database services to a wide set of end users. In this session, you will learn about the latest features in DBaaS, including schema-based consolidation, thin provisioning of data, and other exciting features.

4. Safe Harbor 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.

5. Table of Contents • What is DBaaS? • Key Challenges • Oracle’s Cloud Solution • Database and Schema Consolidation • Rapid Template based Provisioning • Data Cloning (Storage Copy on Write and RMAN Backups) • Customer Story – HDFC Bank

6. Total Cloud Control Integrated Cloud Stack Management Business-Driven Application Management Complete Cloud Lifecycle Management | | Self-Service IT Simple and Automated Business Driven

7. Customers Have a Choice of Clouds Exclusive Shared by multiple organizations Hybrid Cloud Private Cloud Public Cloud • Cloudbursting – overdraft for peak loads • Dev/Test & production • B2B integration • CapEx & OpEx • Lower total costs • Control & visibility • Multiple apps sharing resources • OpEx • Fast & inexpensive to start • Outsourced services • Multiple tenants sharing resources

8. Private Cloud: PaaSvsIaaS • Increasing Enterprise value with Private PaaS • Private PaaS • Enforces standardization and consolidation • Provides Security and Compliance • Maximizes component re-use • Minimizes hand coding • Maximizes flexibility and control

9. The problem of many and varied • Manual, time consuming provisioning • Data, lots of data! Three Key Challenges

10. Key Challenge 1: The problem of many and varied Solution: Standardization and Consolidation

11. Need for Standardization and Consolidation Complex and ever growing database estate Highcost of operation High cost of deployment PoorUtilizationH/W, CPU, Storage ServiceDelivery Workloadmultiple skills,lots of disparate systems, poor automation “a mixture of versions, operating systems, hardware; rapidly falling into legacy” Poor service, long lead times

12. Consolidation at PaaS and IaaS Layers • Consolidate onto standard, shared and elastically scalable PaaS App App App • Standardized PaaS for all applications reduces heterogeneity, cost and complexity • Accelerated new application development • Cost savings from less hardware, power and data center space PaaS App App App vs. App App App • Software stack heterogeneity, cost and complexity persists • No administration (O&M) cost savings • Consolidate onto shared IaaS without standardization • Cost savings from less hardware, power and data center space IaaS

13. DBaaS Cloud Models Infrastructure Cloud Database Cloud Database Cloud DW CRM ERP ERP DW CRM DW ERP CRM DB DB DB DB OS OS OS DB DB DB Shared Database Shared database instances Hypervisor OS OS OS OS Increasing Consolidation Shared Cluster Shared pool of servers SharedServer Shared pool of hypervisors

14. Considerations for Choosing the Right Model • Brownfield or Greenfield? • Commodity Servers Vs Engineered Systems? • Applications to be deployed, and their database footprint? • Expected SLAs from business users? • Isolation or Security requirements? • Ease of management? Available skill set? • Is self service needed? If yes, who is the user, and what do they expect from this service? Most Customers Settle On a Combination these Models

15. Comparison of DBaaS Cloud Models

16. Examples of DBaaS Cloud Model Usage Shared Cluster Shared Database Shared Server • Application DBA • Provision database for a complex packaged application e.g. eBiz • Application Tester • Clone a production database for performance testing • Application Developer • Provision one or more schemas for a homegrown custom application • Sales Engineer • Provision schema with data for a training app • Junior DBA • Build test environment to verify a database patch • Application Developer • Provision application middleware and database on the same VM

17. Key Challenge 2: Manual and admin based provisioning Solution: Rapid provisioning of Standardized Templates

18. DEPLOYMENT PORTAL Need for Rapid Template based Provisioning Database-as-a-Service Deployment(End-user driven) Traditional App Deployment(Admin driven) Specify and procure hardware Request database deployment Configure hardware Deploy hardware Database Adjust capacity as demand changes Databases OS and Storage Deploy operating system and configure storage Server Hardware Retire database when not needed Deploy database User unaware of underlying infra Self-Service Provisioning

19. EM 12c: Most Comprehensive DBaaS Solution • Self service paradigm for database deployment and management • Pre-packaged, pre-configured database configurations • One-click provisioning and deployment of databases • On-demand scalability of underlying platform • Support for allthreeDBaaS deployment models • Metering and chargeback/showback for IT accountability • Data cloning using Storage copy on write and RMAN Backups • Intelligent Auto-placement, Quota Management, Role based access, and so on ..

20. Ultimate consolidation of databases (shared database deployment model) Each application user gets one or more database schema(s) Service level guarantee through Database Resource Manager Security isolation through Data Vault Integrated with Database 12c Pluggable Databases Multiple pluggable databases within a single container database Schema as a Service

21. Schema as a Service User: Portal • Out-of-box console ; no additional set up required • Supports custom background • Rich service catalog: • Database instances • Schemas • Database portal functions • List all databases and schemas • List requests, quota usage, and notifications • Resource Monitoring • Backup/restore • RESTful Web Service based APIs and CLIs

22. Schema as a Service User: Features • A ‘Schema’ request provides • 1 Database (Application) Service • N schemas/users • 1 master account that has grants over other schemas • 1 tablespace • Request for a ‘Schema’ instance • Choose service templates with/without seed data • Rename and set passwords for schemas • Upload custom sql scripts for execution • Pick duration • Home page for management of provisioned instances

23. DBaaS Setup: Schema as a Service Roles and Responsibilities Self Service Administrator Cloud Administrator

24. DBaaS Cloud Resource Model PaaS Zone Collection of various pools – MW & DB Based on geography, cost center, … Database Pool Defines a homogeneous collection of Databases or Oracle Homes Mandatory criteria - platform, db version, availability (SI/RAC) Optional criteria - SLAs, security, product lifecycle, … Databases and Oracle Homes – Single instance and clustered SI 10.2.0.5 SI 10.2.0.5 SI 10.2.0.5 RAC 11.2.0.2 RAC 11.2.0.2 4N RAC DB 11.2.0.3 N = Node SI = Single Instance RAC = Real Application Clusters

25. Setup Service CatalogCapture -> Publish to Catalog • Publish Service Template to Service Catalog • Schemas with or without data and objects • Assign roles and privileges for master account • Register pre and post creation sql • Tablespace encryption for secure environments • Capture Database Provisioning Profiles • Capture schema and data from existing databases • Uses datapump for export/import

26. Setup Service Catalogcontd. Workload Sizing and Placement • Workload Sizes • Based on projected usage of CPU, Memory, and Storage • Define Small/ Medium/ Large workloads • Attach to Service Templates • Placement Algorithm • Simple: By number of services • Advanced: Based on projected workload characteristics • Resource Manager for CPU allocation • Fixed Datafile Size for storage allocation

27. Chargeback Reporting Chargeback Administrator Self-Service Portal User Line of Business User • Rollup based on LDAP hierarchy • Summary and Trending reports for Usage and Charge • Drilldowns • Integrate with BI Publisher • Generate Reports in variety of formats • Excel, Word, HTML, PowerPoint, PDF • Email or FTP reports • Charge Trend reports broken down by resource • Selectable detail levels • Charge Plan configuration

28. Chargeback Database Metrics

29. Key Challenge 3: Data, lots of data! Solution: Data Cloning using Storage copy-on-write technology and RMAN backups

30. Data Cloning Overview • Functional Testing of Applications • Most functional tests require minimal data changes • Testers frequently need to rollback data • Most storage based solutions lack lifecycle management capabilities • DBA Friendly. Clone ‘Databases’ instead of ‘Storage Volumes’ • Monitoring and configuration management of the cloned database • Upstream Test Master creation workflows (integrated with Masking, Subsetting, etc) • Monitor, implement quota and chargeback based on QOS

31. Data Cloning Options Technology Comparison Copy on Write RMAN Backup • Storage basedtechnology • Saves space and time • Ideal for "use and throw“ i.e. short lived databases • Storage Admin involved • Oracle Database based technology; Storage neutral • Restore time proportional to backup size • Leverages existing technology and infrastructure • Completely managed by DBAs Data Cloning

32. Database Instant Cloning Using Copy on Write ProductionDatabase Test MasterDatabase Masking &Sub setting 010110011101001010 000111010 Functional Copies– User can create multiple copies for functional testing without consuming space • Initial Support for Sun ZFS Storage and NetApp Storage • More than just storage volume cloning • Users can create snapshots and ‘timetravel’ to an earlier snapshot

34. DBaaS Setup: Database Instant Cloning Roles and Responsibilities Cloud Administrator Self Service Administrator

35. Database Cloning Using RMAN Backups 1 RMAN Duplicate • Backup-Based Duplication With a Target Connection • Backup-Based Duplication Without a Target Connection • Backup-Based Duplication Without a Target Connection or a Recovery Catalog Connection Connect Target Connect Auxillary 3 2 Connect Catalog

36. DBaaS Setup: RMAN Backups Roles and Responsibilities Cloud Administrator Self Service Administrator

37. HDFC BANK DBaaS Journey into Oracle Database Cloud with EM12c

38. About HDFC Bank • Incorporated in August 1994 • India’s second largest Private Bank with a nationwide network of • Branches: 2,564 • ATMs: 10,000 (In 1,416 Indian towns and cities) & 20 million customers • Debit Cards: 14.9 Million • Credit Cards: 5.8 Million • Industry: Retail & Corporate Banking • Employees: 56,000 • Revenue: USD 5 Billion

39. Business Drivers • Retail Assets Segment [Lending Business] • 50% of HDFC Bank’s Top Line • Always under pressure to launch “New Schemes” to compete and stay ahead in this segment • IT must respond to this Business need because each new Scheme means – changes to application and testing against Production data [UAT database] • Agility in launching new business initiatives

40. Life Before Database Cloud • Average 3.5 days to provision UAT Database for Loan Management Application • Silo’ed environment with Average 30% utilization • Compliance requirement consume UAT testing resources. • DBA activities mean $$ paid to SI for provisioning databases manually • Overhead in managing configuration drift between production and test environments. • Rollout impact/delay on new business initiatives

41. Database Consolidation – Application Classification • Classify application based on system availability requirement/criticality

42. Database Consolidation Planning • Identify candidate application for Cloud • Further Group them based on availability requirement and sub classification based on OS/DB

43. Database Cloud Solution Architecture

44. Cloud Administration Setup • Zones • Exadata Zone • AIX zone • Role for each application on Exadata and AIX zone • Quota is set based on existing infra available • 7 Databases on LOS Application • 5 Databases on LMS Application • 5 Databases on Web collection Application • Universal charge plan • Service Templates • Exadata -Three templates with data • Exadata -Three templates with only structure • AIX template for Small, Medium, Large database only structure

45. Provision Databases using RMAN Backups • Beta Customer for RMAN restoration integration feature with DBaaS • Level 0 RMAN Backups of Production Databases from Standby[Bunker Copies] • Service Templates created for each of Level 0 Backups • Process to Provision Databases through RMAN is same as Empty Databases

46. Life after Database Cloud Go-live – Time to Provision

47. Summary • DBaaS supports three different DBaaS models • Database in a dedicated VM • Databases in a shared cluster or installation, and • Schemas in a shared database • Special focus on data cloning • Storage copy-on-write technology, and • RMAN backups • Out of box portal to deliver all types of services

48. DBaaS is the Sweet Spot for Enterprise Clouds • Benefits All Stakeholders

49. Graphic Section Divider