The Speaker. Alain Fuhrer, born in Bachelor in computer science. Working with Oracle databases for about 12 years now

Transcription

1 The Speaker Alain Fuhrer, born in 1986 Bachelor in computer science Working with Oracle databases for about 12 years now Head IT Databases at Swiss Mobiliar Insurance REPORTS ANALYTICS AUF ON OLTP DATEN DATA 1

2 Agenda 1. Swiss Mobiliar in a nut shell 2. Oracle MT 12.2 Our Next Level of consolidation 3. Agile@Swiss Mobiliar Insurance Impact on DB Management 4. Q & A 2

3 Swiss Mobiliar Insurance in a nut shell 3

4 Open Source

5 Our Oracle Multitenant Footprint Hardware 8 physical database servers with 16 CPU each Features Data Guard PDB Lockdown Profile Databases 1350 PDB s distributed across 130 CDB Refreshable PDB Oracle Audit 5

6 Oracle MT 12.2 Our next level of consolidation 6

7 Schemas Step 1 Schema consolidation with Oracle 10g Application 1 Application 2 Application 3 Application 4 Application 5 Many applications = one database Savings More than 200 databases 2 physical servers or 16 cores License costs 1 Mio $ 7

8 Schema consolidation makes db management complicated Problems after schema consolidation Solution with Multitenant 12.2 RMAN cloning is not possible Flashback on database level AWR on database level Backup / Restore only with datapump Only limited resource manager PDB cloning is now possible also online Flashback now possible on PDB level AWR now available on PDB level Backup / Restore on PDB level with RMAN Memory management on PDB level Multitenant is «production ready» with Oracle 12.2 and becomes the future for us. But: It s not as easy as it seems at first glance! 8

9 Data Guard configuration in Multitenant Environments Every online PDB clone in a Data Guard environment leads by default to a corrupt standby database MRP0: Background Media Recovery terminated with error T10:14: :00 Errors in file /oradata/u00/app/oracle/diag/rdbms/do10mm98_01/do10mm98/trace/do10mm98_pr00_2938.trc: ORA-01274: cannot add data file that was originally created as '+DATAFS/DO10MM99_01/4AC25F1C7F721BA3E0534EC10B0A18D3/DATAFILE/system ' Managed Standby Recovery not using Real Time Apply Recovery interrupted! T10:14: :00 Errors in file /oradata/u00/app/oracle/diag/rdbms/do10mm98_01/do10mm98/trace/do10mm98_m000_8847.trc: file 1: '+DATAFS/DO10MM98_01/DATAFILE/system ' Recovery ORA-01110: data stopped due to failure in applying recovery marker (opcode 17.34). Datafiles are recovered to a consistent state at change but controlfile could be ahead of datafiles. During an online clone Oracle has to manage the REDO stream of the PDB clone as well as the REDO stream to the standby DB. This does not (yet) work Oracle can only transfer a PDB to the standby on its own, if the clone was made in read-only mode. 9

10 Different ways lead to the goal There are different ways of dealing with the problem, but all of them have a high level of automation effort Master Note «Data Guard Impact on Oracle Multitenant Environments (Doc ID )» 1. Making Use of the STANDBYS=NONE Feature with Oracle Multitenant (Document ) 2. Reusing the Source Standby Database Files When Plugging a PDB into the Primary Database of a Data Guard Configuration (Document ) 3. Using standby_pdb_source_file_dblink and standby_pdb_source_file_directory to Maintain Standby Databases when Performing PDB Remote Clones or Plugins (Document ) As automation of processes is a high priority at Mobiliar, we implemented Workaround 3. 10

11 DB-Link von Standby nach Primary für File Copy First of all Interim Patch ( ) must be installed, which adds a new DB parameter. standby_pdb_source_file_dblink Then the following configuration has to be implemented on the primary CDB PRIM_CDB SQL> PRIM_CDB SQL> STBY_CDB SQL> create database link copy_from_prim connect to system identified by xxx using prim_db ; alter system archive log current; alter system set standby_pdb_source_file_dblink= copy_from_prim ; When we wanted to test the workaround, we were unfortunately confronted with a new problem. 11

12 Because a DB link can only be used if the Database is in OPEN mode, an Active DG license would be required for this solution! The container root (CDB$Root) of the standby database may be opened read-only without requiring an Oracle Active Data Guard license. An Oracle Active Data Guard license is only required if any of the pluggable databases in the standby is opened for read. 12

13 PDB online clone in a Data Guard Environment Step 1 Primary CDB Standby CDB APP 1 APP 2 TMP1 APP 1 APP 2 Container Database no file copy Container Database (RO) CDB1 SQL> create pluggable database tmp1 from app1 standby=none; CDB1 SQL> alter pluggable database tmp open; CDB1 SQL> alter pluggable database tmp close; CDB1 SQL> alter pluggable database tmp open read only; 13

14 PDB online clone in a Data Guard Environment Step 2 Primary CDB Standby CDB APP 1 APP 2 TMP1(RO) APP1_COPY APP 1 APP 2 APP1_COPY Container Database DB-LINK REDO Container Database (RO) CDB1 SQL> create pluggable database app1_copy from temp1; CDB1 SQL> alter pluggable database app1_copy open; 14

15 PDB online clone in a Data Guard Environment Step 3 Primary CDB Standby CDB APP 1 APP 2 TMP1(RO) APP1_COPY APP 1 APP 2 APP1_COPY Container Database REDO Container Database (RO) CDB1 SQL> alter pluggable database tmp1 close immediate; CDB1 SQL> drop pluggable database tmp1 including datafiles; 15

16 Mobiliar Insurance & Impact on DB Management 16

17 I want that the company is able to deploy productive services every day in 2020 Rolf Trueb CIO Swiss Mobiliar Insurance 17

18 Opportunities for the Company Time to Market can be improved (faster implementation of new business requirements) Business & customers don t wait 6 months for new functionality Effort reduction by much more automatization Manual testing effort decreases: automation and smaller software packages increase the efficiency Minimizing risks by applying smaller software releases Development can react quickly and flexibly Quick Business response and quick bug fixing Cooperation between Business & IT is improved Business regards IT as a service provider who delivers continuously Confidence rises -major step towards DevOps 18

19 Transformation from Application to s Typical evolution t 19

20 Impact on Database Management We have to deliver managed services for the development In the future we get a large number of s that use databases Multitenant architecture will help us to solve this challenge Automatization: we had to implement automatic database deployment (DBaaS) Databases have to be available in minutes Databases can exists from days to hours or even minutes 1:1 mapping between s and databases 20

21 Starting point: The deployment pipeline Version control detect Continuous integration push image trigger deployment register Docker registry Push Get image How and where to build the database in this deployment pipeline Development Start Image Kubernetes 21

22 DBaaS architecture at Swiss Mobiliar t = min detect build register Version control Continuous integration trigger deployment Docker registry Push t = 1 min Fully automated application deployment including Oracle database t = 2 min in less than 10 minutes order get state Get image t = min OUD connect Start Image Development PDB Kubernetes 22

23 Technical implementation Continuous integration REST Call Execute Function sql over oracle client pdb_orders Repository Database REST Server Create external Job to execute shell script Submit os credentials and execute job Shell script creates, delete, start or stop new pdb and post actions Update pdb_orders table when pdb is created Submit success to Continuous Integration Create corresponding Docker image Template PDB APPL 1 APPL 2 Container Database Execute Procedure DB Link 23

24 Deployment decision process Restrictions $pdb_name=topdb1 P = 15 PDB / CDB T & D = 50 PDB / CDB CDB Inventory do10mm01 to10ms01 po10ss01 do10mm02 to10ms02 po10ss02 do10mm03 to10ms03 po10ss03 Available Restrictions to10ms01 Submit job PDB Inventory pdb count on to10ms01 = 22 pdb count on to10ms03 = 37 24

25 Conclusion - The DBAAS Interface is a great success DBAAS STATISTICS DB created DB deleted created PDB s Dez Jan Feb Mär 17 Apr 17 Mai 17 Jun Jul 17 Aug Sep Okt 17 Nov Dez Jan 18 Feb Mär Apr Mai Jun Jul 18 Aug Sep 18 1 Okt 18 deleted PDB s We satisfy the requirements of all stakeholders We delivered more than 1200 PDB s over the Interface in less than two years With this service we can cover today and in the near future the requirements, which an agile software development places on the DB management - and Oracle Multitenant is the right architecture for it 25

26

27