SE2 goes Enterprise. Hidden Treasures in Oracle Dr. Thomas Petrik DOAG Konferenz, November 2017, Nürnberg

Transcription

1 SE2 goes Enterprise Hidden Treasures in Oracle 12.2 Dr. Thomas Petrik DOAG Konferenz, November 2017, Nürnberg

2 Oracle Container Architecture 2

3 Single-Tenant is the Default Oracle Database Upgrade Guide 12.2 SE MAX_PDBS = 4098 Oracle Database Licensing Information User Manual

4 CDB Delegation & Separation from EE to SE2 user management space management application support flashback PDB application DBA application DBA application DBA app1 app2.. container DBA (SYS) RAC Dataguard RMAN DB-software server / OS installation / setup HA / DR backup / restore workload management DB-tuning monitoring 4

5 CDB CDB CDB Delegation & Separation from EE to SE2 application DBA application DBA application DBA app1 app2.. container DBA OS-admin RAC RMAN RAC RMAN RAC RMAN DB-software server / OS 5

6 CDB CDB CDB Delegation & Separation from EE to SE2 application DBA application DBA application DBA app1 app2.. container DBA OS-admin RAC RMAN RAC RMAN RAC RMAN DB software OS container (LXC, Docker) VM DB software OS container (LXC, Docker) DB software VM physical server 6

7 Excursus: Isolation with OS-Containers 7

8 OS Container light weight virtualization containers running on the same kernel containers are separated, fully equipped machines VM admin delegates activities self-service (Dev / Test) resource control rapid provisining clone historization copy-on-write (COW) snapshots in combination with BTRFS CPU pinning memory limits / shares 8

9 LXC und Oracle Starting with Oracle Database 12c Release 1 ( ), Linux Containers are supported on Oracle Linux 7 and Oracle Linux 6 and certified on Linux x86-64 systems. Oracle 12c Release Notes MOS Note not valid any more with OEL 7.3 / Oracle

10 Building Clone Histories 10

11 Creating Hot Clones in SE2 PDB1 CDB1 PDB2 CDB2 PDB3 CDB3 PDB4 CDB4 CDB5 local undo source CDB must be in archivelog mode target PDB may be opend R/O or R/W SQL> create database link clone_link connect to pdbadmin identified by using 'PDB1'; Database link created. SQL> create pluggable database PDB2 from Pluggable database created. SQL> alter pluggable database PDB2 open; Pluggable database altered. CDB2 11

12 Creating Snapshot Clones nearly no additional (initial) storage needed (COW) Linux Container (LXC) crash consistent online clone as COW snapshot using BTRFS OS PDB snapshots Oracle VM create a crash consistent clone DB OS 12

13 LXC & COW snapshots clone your CDBs within seconds lxc-clone -s <source> <target> creates a COW-snapshot clone source container must be stopped btrfs subvolume snapshot <source> <target> creates an online snapshot clone Oracle database within the clone comes up with a crash recovery # lxc-ls ora12c01 ora12c02 # mkdir /container/ora12c03 # btrfs sub sn /container/ora12c01/rootfs /container/ora12c03/rootfs # btrfs sub list /container ID 265 gen top level 5 path ora12c01/rootfs ID 266 gen top level 265 path ora12c01/rootfs/var/lib/machines ID 304 gen top level 5 path ora12c01/snaps/snap0/rootfs ID 306 gen top level 5 path ora12c02/rootfs ID 308 gen top level 5 path ora12c03/rootfs # cp /container/ora12c01/config /container/ora12c03 # vi /container/ora12c03/config # lxc-start n ora12c03 lxc.network.ipv4 = /24 lxc.rootfs = /container/ora12c03/rootfs lxc.utsname = ora12c03 13

14 Creating PDB Snapshots master image PDB1 PDB4 SQL> alter pluggable database pdb1 close immediate; Pluggable database altered. CDB1 SQL> alter pluggable database pdb1 open read only; CDB1 Pluggable database altered. SQL> create database link clone_link connect to pdbadmin identified by using 'pdb1'; CDB2 PDB2 PDB3 PDB4 Database link created. CDB2 CDB3 CDB4 CDB5 SQL> create pluggable database pdb2 from snapshot copy; Pluggable database created. Elapsed: 00:00:00.92 SQL> alter pluggable database pdb2 open; Pluggable database altered. # ls -lhs o1_mf_sh_c4drdcjo_.dbf 32K -rw-r oracle oinstall 18G Nov 13 23:17 o1_mf_sh_c4drdcjo_.dbf allocated 14

15 PDB Snapshot Clones Prerequisites clonedb = true since set clonedb_dir (new in 12.2) destination for bitmap file default: $ORACLE_HOME/dbs is used shared destination for RAC any local filesystem may be used ext4, xfs, btrfs, etc. not on ext3 not on ASM clonedb = false only via dnfs and on ACFS License considerations EE and Multitenancy Option needed for creating snapshot PDBs within the same CDB storage snapshots on ACFS need EE Caveats source PDB must remain read only source PDB must not be dropped no error message! snapshot PDBs cannot be unplugged Oracle Database 12c Release ( ) New Features 15

16 Finally: a Dataguard for SE2 16

17 Refreshable PDB Prerequisites source CDB must be in archivelog mode local undo must be used set remote_recovery_file_dest otherwise "foreign" archivelogs go into $ORACLE_HOME/dbs create DB-link from target CDB to source PDB same privileges as for remote cloning client failover / listener config: use same methods as for DG create pluggable database pdb2 from pdb1@clone_link refresh mode manual; create pluggable database pdb2 from pdb1@clone_link refresh mode every 1 minutes; alter pluggable database pdb2 refresh mode none; Operations works between all editions EE-EE, EE-SE2, SE2-SE2 refresh modes automatic or manual refresh is stopped when target PDB is open R/O open R/W breaks the synchronization forever BEGIN SYS.DBMS_SCHEDULER.CREATE_JOB ( job_name => 'PDB2_ _REFRESH',start_date =>,repeat_interval => 'FREQ = MINUTELY; INTERVAL = 1',end_date => NULL,job_class => 'DEFAULT_JOB_CLASS',job_type => 'PLSQL_BLOCK',job_action => 'begin execute immediate ''alter session set container = PDB2''; execute immediate ''alter pluggable database refresh''; end;',comments => 'PDB2 refresh' ); 17

18 Refreshable PDB: Switchover PDB1 CDB1 refresh PDB2 CDB2 18

19 Refreshable PDB: Switchover PDB1 CDB1 refresh PDB2 CDB2 alter pluggable database pdb1 close immediate; alter pluggable database pdb1 open read only; alter session set container=pdb2; alter pluggable database pdb2 refresh; alter pluggable database pdb2 refresh mode none; 19

20 Refreshable PDB: Switchover PDB1 PDB2 CDB1 CDB2 alter pluggable database pdb1 close immediate; alter pluggable database pdb1 open read only; alter session set container=pdb2; alter pluggable database pdb2 refresh; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 open; alter pluggable database pdb1 close immediate; drop pluggable database pdb1 including datafiles; 20

21 Refreshable PDB: Switchover PDB1 CDB1 refresh PDB2 CDB2 alter pluggable database pdb1 close immediate; alter pluggable database pdb1 open read only; alter session set container=pdb2; alter pluggable database pdb2 refresh; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 open; alter pluggable database pdb1 close immediate; drop pluggable database pdb1 including datafiles; create database link clone_link using pdb2 ; create pluggable database pdb1 from pdb2@clone_link refresh mode every 1 minutes; 21

22 Refreshable PDB: Failover PDB1 CDB1 refresh PDB2 CDB2 22

23 Refreshable PDB: Failover alter session set container=pdb2; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 refresh mode none * ERROR at line 1: ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor ORA-17629: Cannot connect to the remote database server PDB2 CDB2 23

24 Refreshable PDB: Failover alter session set container=pdb2; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 refresh mode none * ERROR at line 1: ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor ORA-17629: Cannot connect to the remote database server PDB2 CDB2 alter pluggable database pdb2 open read only; exec dbms_pdb.describe('/tmp/pdb2.xml'); 24

25 Refreshable PDB: Failover alter session set container=pdb2; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 refresh mode none * ERROR at line 1: ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor ORA-17629: Cannot connect to the remote database server PDB2 CDB2 alter pluggable database pdb2 open read only; exec dbms_pdb.describe('/tmp/pdb2.xml'); alter pluggable database pdb2 close immediate; alter session set container=cdb$root; drop pluggable database pdb2 keep datafiles; 25

26 Refreshable PDB: Failover alter session set container=pdb2; alter pluggable database pdb2 refresh mode none; alter pluggable database pdb2 refresh mode none * ERROR at line 1: ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor ORA-17629: Cannot connect to the remote database server PDB2 CDB2 alter pluggable database pdb2 open read only; exec dbms_pdb.describe('/tmp/pdb2.xml'); alter pluggable database pdb2 close immediate; alter session set container=cdb$root; drop pluggable database pdb2 keep datafiles; create pluggable database pdb2 using '/tmp/pdb2.xml'; alter pluggable database pdb2 open; 26

27 DR, Golden Image & Reporting Offload PDB2 CDB2 PDB2 closed DR solution automatic refresh used for switchover & failover PDB1 CDB1 PDB2 CDB2 PDB2 open R/O used for reporting golden image for further clones manual refresh 27

28 PDB Relocation 28

29 Relocation Scenario 1 listener refresh PDB1 relocate PDB2 create pluggable database pdb1 from pdb1@clone_link relocate; CDB1 CDB2 29

30 Relocation Scenario 1 listener use a shared listener or... use listener_networks or... change tns-connect CDB1 PDB1 CDB2 create pluggable database pdb1 from pdb1@clone_link relocate; alter pluggable database pdb1 open; 30

31 Relocation Scenario 2 listener refresh PDB1 relocate PDB2 create pluggable database pdb1 from pdb1@clone_link relocate availability max; CDB1 CDB2 31

32 Relocation Scenario 2 listener leaves a proxy PDB system & sysaux on both CDBs DD always in sync no change of client connects no firewall changes PDB name must be the same nearly no performance impact PDB1 CDB1 PDB1 CDB2 create pluggable database pdb1 from pdb1@clone_link relocate availability max; alter pluggable database pdb1 open; 32

33 PDB Relocation Use cases live migration scenarios VM-based live migration is often restricted due to licensing issues Hybrid Cloud scenarios move PDBs between cloud and on-premise online patching by relocating a PDB to a new CDB it is upgraded implicitly options (EE) and software patches must match! Good to know db-link goes from CDB to CDB works basically between all editions (EE / SE2) source PDB must be in archivelog mode local undo must be used relocation is only nearly live all active sessions are killed on the source uses the refreshable PDB feature in the background during relocation 33

34 The Application DBA: Separation of Duties I 34

35 The PDB-DBA should be restricted in changing PDB parameters bound to the defined directory structure on the filesystem restricted in his network communication... restricted to specific OS activities restricted in changing FGAC policies 35

36 PDB Security & Resource Isolation create pluggable database create_file_dest target destination for datafiles cannot be overruled by PDB DBA new behaviour since 12.2 path_prefix mandatory prefix for directory objects no absolute paths any more new behaviour since 12.2 storage (maxsize ) maximum disk space for the PDB Parameter Settings PDB_OS_CREDENTIAL CPU_COUNT MAX_IOPS (12.2) MAX_MBPS (12.2) DB_CACHE_SIZE minimum size SHARED_POOL_SIZE minimum size PGA_AGGREGATE_LIMIT PGA_AGGREGATE_TARGET SGA_MIN_SIZE (12.2) SGA_TARGET resource management also in single-tenant environments 36

37 Lockdown Profiles Options PARTTIONING DATABASE QUEUING STATEMENTS ALTER DATABASE ALTER PLUGGABLE DATABASE ALTER SYSTEM ALTER SESSION Feature Bundles OS_ACCESS NETWORK_ACCESS COMMON_SCHEMA_ACCESS CONNECTIONS utl_file drop_tablespace_keep_data_files file_transfer security_policies (VPD,RAS,FGA) utl_tcp utl_smtp utl_http 37

38 Lockdown Profiles create lockdown profile def_profile; alter system set pdb_lockdown = def_profile; alter lockdown profile def_profile enable option = ('PARTITIONING'); alter lockdown profile def_profile enable option all; alter lockdown profile def_profile enable option all except (' '); alter lockdown profile def_profile disable option = ('PARTITIONING'); alter lockdown profile def_profile disable option all; alter lockdown profile def_profile disable option all except (' '); alter lockdown profile def_profile enable feature = ('OS_ACCESS'); alter lockdown profile def_profile enable feature all; alter lockdown profile def_profile enable feature all except (' '); alter lockdown profile def_profile disable feature = ('OS_ACCESS'); alter lockdown profile def_profile disable feature all; alter lockdown profile def_profile disable feature all except (' '); no alter system except for 1 <= CPU_COUNT <= 4 alter lockdown profile def_profile enable statement = ('ALTER SYSTEM'); alter lockdown profile def_profile enable statement all; alter lockdown profile def_profile disable statement = ('ALTER SYSTEM'); alter lockdown profile def_profile disable statement = ('ALTER SYSTEM') clause = ('SET') OPTION = ('CPU_COUNT') minvalue = '1' maxvalue = '4'; 38

39 The Application DBA: Separation of Duties II 39

40 The PDB-DBA should manage users and tablespaces do some PDB tuning... NOT change the application structure do application monitoring NOT change the application config (common data) 40

41 CDB Application Container in EE tenant 1 tenant 2 tenant 3 APP_ROOT APP_DB1 APP_DB2 APP_DB3 Deployment deployed structures (and common data) cannot be changed by any PDB user (not even by SYS) 41

42 CDB Application Container in SE2 can do Head DBA APP_ROOT APP_DB App-DBA create additional users and TS change local data PDB performance tuning PDB monitoring PDB flashback database cannot do deployment change application structure change application common user change common data 42

43 APP1 APP1 Application Container / Install create pluggable database app_root as application container CDB$ROOT APP_ROOT 1.0 alter pluggable database application APP1 begin install '1.0'; DDL, DML, alter pluggable database application APP1 end install; APP_ROOT APP_DB 1.0 create pluggable database app_db APP_ROOT alter pluggable database application all sync; APP_DB local data local data 43

44 APP2 APP2 APP1 APP1 Application Container / Upgrade APP_ROOT APP_DB local data 1.0 local data

45 APP2 APP2 APP1 APP1 Application Container / Upgrade APP_ROOT 1.1 alter pluggable database application APP1 begin upgrade '1.0' to '1.1'; DDL, DML, APP_DB alter pluggable database application APP1 end upgrade; APP_ROOT 1.0 local data local data 45

46 APP2 APP2 APP1 APP1 Application Container / Upgrade APP_ROOT 1.1 alter pluggable database application APP1 begin upgrade '1.0' to '1.1'; DDL, DML, APP_DB 1.1 alter pluggable database application APP1 sync; APP_DB 1.0 alter pluggable database application APP1 end upgrade; APP_ROOT 1.0 local data local data 46

47 Conclusio many new features in 12.2 made for the enterprise can be used with an SE2 as well use the PDB based Dataguard for DR scenarios use snapshot technologies for rapid provisioning in test and development environments introduce separation of duties between head DBA and application DBA by applying PDB infrastructure even in SE2 47

48 ? Dr. Thomas Petrik E thomas.petrik@sphinx.at M T Sphinx IT Consulting GmbH Aspernbrückengasse Wien