Infrastructure at your Service. DOAG Webinar. ODA 12c new features. ODA 12c new features

Transcription

1 Infrastructure at your Service. DOAG Webinar

2 Infrastructure at your Service. About us David Hueber COO Principal Consultant Mobile Page 2

3 Who we are dbi services Experts At Your Service > Over 40 specialists in IT infrastructure > Certified, experienced, passionate Based In Switzerland > 100% self-financed Swiss company > Over CHF 6 mio. turnover Leading In Infrastructure Services > More than 100 customers in CH, D, & F > Over 40 SLAs dbi FlexService contracted > ISO20000 certified Page 3

4 Agenda 1. ODA X5-2 new hardware > Global specifications > Storage capacities > Networking capacities 2. > Software versions > ACFS storage > Container databases > Cache Fusion > In Memory support > Interfaces changes Page 4

5 ODA X5-2 new hardware Bigger, faster... > ODA versions > Global specifications > Storage capacity > Networking capacities Page 5

6 Hardware architecture ODA versions ODA v1 ODA X4-2 Sep Mar Dec Feb ODA X3-2 ODA X5-2 Page 6

7 ODA X5-2 new hardware Global specifications 2 x 1 RU x86 Server > 2 x 18-cores Intel Xeon E v3 > 256 GB RAM (8 x 32GB) Extensible up to 768GB > 2 x 600GB Boot Disks > Hardware mirroring > 1 x Internal SAS HBA > 2 x External SAS HBA > 10GbE customer network > 40Gb/s Infiniband interconnect 1 x 4 RU Storage > 4 x GB SSD (Redo) > 4 x GB SSD (Flash Cache) > 16 x 2.5 4TB HDD (Data) Page 7

8 ODA X5-2 new hardware Storage capacity Depends on ASM redundancy > Raw data: 64 TB > Double mirrored: 32TB > Triple mirrored: 21,3 TB Depends on backups location > Local or External > Impacts Disk Groups sizing > +DATA > +RECO > REDO 248GB > FLASH 746GB ODA X4-2 X5-2 Backup Mode + DATA (TB) +RECO (TB) Normal Redundancy Local 12, ,4 4.5 External 24, High Redundancy Local 8, ,9 3 External 16, ,6 Page 8

9 ODA X5-2 new hardware Storage capacity Flash Cache feature > Based on +FLASH ASM Disk Group > 4 x 400GB SSDs > Used as swap for the SGA > Expired block in SGA are moved to Flash Cache > Data request process > Check SGA > Check Flash Cache > Access disks > db_flash_cache_file > Default = 3 x SGA > Max = 196GB 1 - Data retrieval Data disks SGA (Memory) 2 - Data ejection 3 - Data restore Flash disks Page 9

10 ODA X5-2 new hardware Storage capacity Data files on Flash storage > Data files can be stored on SSDs > Using OAKCLI at database creation > Manually > Restrictions > Database version >= > Database type must be OLTP > CDB databases cannot be completely stored on SSDs > At least 160GB space available in +FLASH diskgroup Page 10

11 ODA X5-2 new hardware Networking capacities New interconnect > Infiniband based 40Gb/s > Allows Cache Fusion ability Data network & interconnect can be switched over > Use 10GbE base-t ports for Interconnect > Use fiber connections for data network > Requires > Remove of Infiniband cards > Buy 2 additional Dual 10GbE SFP+ PCIe 2.0 & SFP+ transceivers > Budget around $6 000 Page 11

12 More possibilities... > Software version > ACFS storage > Container databases > Cache fusion > In-Memory support > Licensing Page 12

13 Software versions Latest Patch Bundle ODA (20 May 2015) > Whole 12c support > Still under Oracle Linux 5 Oracle Database Oracle Database Grid Infrastructure Oracle Clusterware Appliance Manager Oracle Linux 5.11 Kernel Appliance Manager OVM Oracle Linux Page 13

14 ACFS storage Introduced in version > Move database files from ASM disk groups to ACFS volumes ACFS Databases Volumes DATA datastore-286 datastore-360 datastore-386 REDO DATA DATA ARC ARC ARC REDO REDO ASM Disk Groups +DATA +RECO +REDO Page 14

15 ACFS storage Introduced in version > Move database files from ASM disk groups to ACFS volumes Databases DATA DATA DATA ARC ARC ARC REDO REDO REDO ACFS Volumes datastore-286 datastore-360 datastore-386 ASM Disk Groups +DATA +RECO +REDO Page 15

16 ACFS storage Default for any new database creation Default volumes configured at first database creation > Same for all single instance databases > Dedicated volumes for each container database ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/asm/datastore G 49G 14G 79% /u01/app/oracle/oradata/datastore /dev/asm/datastore T 243G 1.5T 15% /u02/app/oracle/oradata/datastore /dev/asm/datastore T 5.0G 2.2T 1% /u01/app/oracle/ fast_recovery_area/datastore Page 16

17 ACFS storage Volumes can be displayed in ASMCMD > volinfo G <diskgroup> -a ASMCMD> volinfo -G DATA -a Diskgroup Name: DATA Volume Name: DATASTORE Volume Device: /dev/asm/datastore-286 State: ENABLED Size (MB): Resize Unit (MB): 64 Redundancy: MIRROR Stripe Columns: 8 Stripe Width (K): 1024 Usage: ACFS Mountpath: /u02/app/oracle/oradata/datastore Page 17

18 ACFS storage ACFS commit on write feature > Data files are stored in snapshots > Folder.ACFS datastore]# pwd /u02/app/oracle/oradata/datastore datastore]# ls -a... lost+found datastore]# cd.acfs ls repl snaps cd snaps snaps]# ls DBIPROD DBITEST Page 18

19 ACFS storage ACFS commit on write feature > Provides databases cloning features > Supported for > Single Instance > RAC One Node > RAC > Not supported for CDB > OAKCLI CREATE SNAPSHOTDB snaps]# oakcli create snapshotdb -h Usage: oakcli create snapshotdb -db <db_name> -from <db_name> where: db_name from - Name of the database to be created. - Source database for creating the snapshot database. Page 19

20 ACFS storage Volumes management > Up to ODA > ACFSUTILS as root > > OAKCLI CREATE DBSTORAGE > OAKCLI DELETE DBSTORAGE > OAKCLI RESIZE DBSTORAGE > > OAKCLI SHOW DBSTORAGE ~]# oakcli create dbstorage -h Usage: oakcli create dbstorage -db <db_name> [-cdb] where: db_name - Setup the required ACFS storage for the database <db_name> cdb - This needs to be passed in case of cdb database Page 20

21 Container databases Supported in OAKCLI commands > Option -cdb ~]# oakcli create database -h Usage: oakcli create database -db <db_name> [[[-oh <home>] [-version <version>]] [-params <params_file>] [-cdb]] where: db_name - Name of the database to be created. home - Existing oracle home for creating the database. By default we create a new database home. version - Database Version information for creating the database home. [ex ] If not provided create the database home from latest available bits. params_file - Name of the db_config_parameter file [This file can be created using using 'oakcli create db_config_params']. If not provided, create the database using default configuration file cdb - Creates this database as a container database Page 21

22 Container databases All options installed on CDB > Allows to deploy any type of PDB > Requires about 2 hours No PDB created by default > To be done manually Generates dedicated ACFS volumes > Size defined during database creation /dev/asm/rdocdb G 3.2G 1.9G 63% /u01/app/oracle/oradata/ rdocdb1 /dev/asm/datcdb G 3.9G 1.2G 77% /u02/app/oracle/oradata/ datcdb1 /dev/asm/rcocdb G 89M 6.0G 2% /u01/app/oracle/ fast_recovery_area/rcocdb1 Page 22

23 Cache fusion - performances Feature of Real Application Cluster databases > Cross-nodes SGA sharing > Reduce disk I/Os Node 0 Node 1 Data not found in SGA-0 Check GCS Global Cache Service (GCS) Send request to SGA-1 New request comes in SGA 0 SGA 1 Send data to SGA-0 using interconnect Page 23

24 In-Memory support Introduced in version > New database type in OAKCLI CREATE DATABASE > In-Memory Please select one of the following for Database type [1.. 3]: 1 => OLTP 2 => DSS 3 => In-Memory 3 Selected value is : In-Memory Templates defines In-Memory buffer size > From 1GB to 64GB > Can be manually adjusted > Requires database restart Page 24

25 In-Memory support Defines a new static pool in the SGA > Size controlled by INMEMORY_SIZE parameter > Contains two subpools: > IMCU pool Stores column data in In Memory Compression Unit (IMCU) > SMU pool Stores Snapshot Metadata Units for metadata and transactional information System Global Area (SGA) Shared Pool Buffer Cache In-Memory Library block block IMCU pool cache block block CU CU CU CU CU block block row store SMU pool column store Page 25

26 In-Memory support Loading tables in In-Memory > Default loading alter table SH.SALES INMEMORY; > Excluding some columns alter table SH.SALES INMEMORY NO INMEMORY(tax_region); > Set population priority alter table SH.SALES INMEMORY PRIORITY CRITICAL; Page 26

27 In-Memory support Duplicate feature > Used in cluster environment > Only available on Engineered System > Requires Infiniband > Ensure In-Memory column store content consistency across nodes > Data populated in all nodes IMCU > Other RAC environments need to use parallel queries and DOP Page 27

28 Licensing Not that brand new > Change came with X4-2 > Was not widely communicated Licensing model > Pay as you grow > Minimum of 2 cores per node 4 per ODA > Cores enabled per increment of 2 per node > For both Bare Metal and Virtualized since X4-2 Virtualized mode specificities > All remaining cores available for applications domains > Weblogic or any other applications including Oracle Standard Edition Page 28

29 Infrastructure at your Service. Any questions? Please do ask. David Hueber Senior Consultant COO Mobile We look forward to working with you! Page 29