oracles next database version - new...

The Author Pluggable DBs AC RMAN Data Guard ILM Flex ASM Flex Cluster Misc

Oracles next Database Version -New Features

... or: the new features of the successor of 11g Release 2

Ronny Egner

Presentation at "Frankfurter Datenbanktage" in March 2013

14-March-2013

Ronny Egner Presentation at "Frankfurter Datenbanktage" in March 2013

Oracles next Database Version - New Features


Table of contents

Pluggable DBs

AC

RMAN

Data Guard

ILM

Flex ASM

Flex Cluster

Misc




Analysis, opinions, and representations expressed in thispresentation are solely those of the author and have not

been approved or endorsed by Oracle.

As Beta program is still ongoing:I No slides will be publishedI No recordings will be made and published




I Oracle Database 12c Beta SlidesI Oracle Database 12c Beta DocumentationI own testing scenarios




The Author

I Ronny EgnerI Freelancer specialized in

I Oracle DatabasesI Oracle EXADATAI UNIX / Linux / WindowsI EMC Networker

I 12 years of experienceI Participating in the 12c Beta Program since start - thats

what this presentation is about




Pluggable Databases

I Key Feature of new Release 12cI Solves the challenge of having more and more databases

causing increased maintenance and costsI Oracles answer to that are ’Pluggable Databases’I Container Database identical to ’pre 12c’-Database: has a

SGA, Processes (LGWR, CKPT, DBW, ...)I In a CDB there can be up to 254 (minus 1 for the SEED

DB) ’pluggable databases’; they ’exist’ within a CDB




Pluggable Databases - cont.

I A PDB is completely backwards compatible to a pre-12.1database; A foreground session sees the PDB as a’normal’ DB – no code changes required

I PDB is completely RAC-aware, RMAN-integrated andDataGuard-enabled

I Resource Management on CDB-level (= distribution ofresources among PDBs) possible




Pluggable Databases - Key Benefits

I Fast provisioning of new databases (usually withinseconds)

I Transport of PDBs between CDBs via ’UNPLUGDATABASE’ and ’PLUG DATABASE’

I Same mechanism will be used for Upgrade starting with12c




Pluggable Databases - How does it work?I Separation of Oracle metadata (stored in CDB) from User

metadata (stored in each PDB):




Pluggable Databases - High-Level Overview,Provisioning and Cloning




Pluggable Databases - Users and Groups

I There can be GLOBAL (’common’) or LOCAL (to a PDB)users and groups

I GLOBAL users and groups must have a prefix ’C##’I Permissions of common users can be enhanced on PDB

levelI DBA and SYSDBA permissions can be given to users at

PDB level ; Users will be SYSDBA or DBA for thatparticular PDB




Pluggable Databases - High-Level Overview, Accessvia SQLNet




Pluggable Databases - High-Level Overview, PhysicalStorage




Pluggable Databases - The scope counts

I Depending on where the action is started the output isdifferent: on CDB it affects the whole CDB plus all PDBs,on PDB it affects only the PDB

I In addition to the well know ’USER_’, ’ALL_’ and ’DBA_’there will be new ’CDB_’ views for the whole CDB

I Some initialization parameters can be modified at PDBlevel (new column in V$PARAMETER)

I RMAN point-in-time recovery on PDB level possibleI Flashback database on PDB in 12c Release 2




Pluggable Databases - Want to know more?

Don’t miss the presentation on PDBs tomorrow (15.03.201310:00 - 10:45)




Application Continuity - Pre-Oracle 12c

I Pre-Oracle 12c:I RAC protects from failure of an instance - Protection

against compete outage in case of a node failureI Depending on the application this failure might lead to

errors popping upI for planned downtimes: Service needed relocation;

Application needs to be stopped in certain cases




Application Continuity - Oracle 12c

I Oracle 12c:I Oracle 12c preserves COMMIT outcomeI Ensures Application continuityI No service interruption on application side in case of node

failures or planned maintenanceI works with Oracle RAC and Active Data GuardI available for JDBC-Thin, UCP, WebLogicI PeopleSoft, Siebel, Fusion in-progressI Database supports SQL and PL/SQL, Query, PQ, DML,

DDL




Application Continuity - Oracle 12c




Application Continuity - Restrictions

I Restrictions - no AC available:I XAI SYSDBAI Database serviceI JAVA Concrete classesI JAVA best effort on streamsI Restricted Calls (alter system / alter database)I Logical StandbyI Golden Gate




Application Continuity - Side Effects

I Side effects: Some replays may be repeated during AC.AC may need to be disabled for:

I Autonomous transactionsI UTL_HTTPI UTL_URLI UTL_FILEI UTL_FILE_TRANSFERI UTL_SMTPI UTL_TCPI UTL_MailI DBMS_PIPEI DBMS_ALERT




Recovery Manager - New Features

I Recovery at Object-Level (Tables)I Cross-Plattform Backup and RestoreI Support of Pluggable DatabasesI Duplicate from ACTIVE now supported SECTION SIZE

and compressionI SECTION SIZE support for image copies and incremental

backupsI New SYSBACKUP privilege for backup operations




Recovery Manager - Object-Level Recovery

I Pre-12c: Restore database to auxiliary database, recover,export data, import data to target db

I 12c: Automated processI Recovered data in aux db is either:

I Exported to a Dump FileI Directly imported to target db




Recovery Manager - Cross-Plattform Backup andRestore

I Backup performs backup of tablespace plus TTS exportwith data pump

I Restore converts tablespace and imports TTSI Incremental backups can be applied to restored data files




Recovery Manager - Pluggable Database Support

I Seamless integration of new pluggable database conceptI Backup of whole CDB plus PDBs, selected or all PDBs,

Tablespaces from PDBsI Restore of whole CDB plus PDBs, selected or all PDBs,

Tablespaces from PDBsI Duplicate to clone CDB plus PDBs or selected PDBs only




Data Guard

I Support for PDBI Far Sync StandbyI Fast SyncI Online Move of Data FilesI New Privilege for Data Guard administration: SYSDGI DML on Temporary TablesI Global and Session SequencesI Cascading Standby: Real-Time cascadeI High Available UpgradeI Resumable Switchover




Support for PDBs

I Standby on container database level (= all PDBs in acontainer are protected by a standby)

I Role changes on container level (= switchover affects allPDBs)

I Enhancement Request to change that on PDB Level for12.2




Far Sync Standby

I Synchronous configurations are limited by distanceI Practical limit between 50 and 100 kmI Far Sync Standby solves this problem by introducing a

local sync transport hub




Far Sync Standby -cont.I Far Sync Server stores: standby control file, redo log file,

archived redo logs (NO user data, no media recovery, nolicense required)

I Far Sync Server receives redo from primary database(sync)

I Far Sync Server forwards redo async to up to 30 remotedestinations

I Alternate Far Sync Server supported for HAI If Primary fails:

I Far Sync Server has all the redoI Far Sync ships all the redo to Remote StandbyI Switchover to Remote StandbyI Even faster due to Fast Sync




Fast Sync

I Can be enabled optionallyI Reduced impact of SYNC data guard configurationsI 11g: COMMIT waits until the request has reached the disk

on standbyI 12c: COMMIT is acknowledged when it has reached the

local cacheI Elimination of standby I/O roundtrip timeI If network round-trip latency < local time write ; no

performance impact of having a standby database




Online Datafile Move

I Move of datafiles without downtimeI Supported on primary and standby databaseI Moves does not affect each otherI Online Move on Standby requires Active Dataguard license




New Privilege: SYSDG




DML on Temporary Tables

I Active Data Guard Standby databases used for reportingoften require intermediate tables

I Idea: Temporary TablesI in 11g: Temporary Tables still create REDO, conflict with

read-onlyI in 12c: Temporary Tables do not create REDO (optionally)I Enables DML on Temporary Tables




Global and Session Sequence

I Sequences from the primary DB are now visible andusable on the standby DB




Real-Time cascade

I 11g: Standby 2 is always at least one log sequence behindSB1

I 12c: Active Data Guard Real-Time Cascade: Standby DBsare now always up-to date with the primary




High-Available Upgrade




Resumable Switchover

I Failed switchovers in previous versions often neededmanual intervention

I Data Guard Broker in 12c can now RESUME a switchover,i.e. continue where it failed




Information Lifecycle Management (ILM)

I Size of databases increases (estimated growth of 20 timeover next 10 years)

I Cost for storage significantI Storage IOPS staleI Archiving of infrequently used database e.g. to cheaper

storage a manual and error-prone effort




ILM - General concept cont.I ILM creates a ’heat map’ of the database

I Database Level Heat Map: which tables, indexes andpartitions are used

I Row Level Heat Map: accesses at row levelI Distinguished between Reads and WritesI Last Access TimeI Histogram of Accesses over timeI Enabled at Tablespace or Table LevelI Object Level at now cost, row level < 5%I Stored in SYSAUXI Dictionary Views availableI Tracking can be enabled/disabled via ALTER SYSTEM




ILM - Criterias

I Conditions are:I Time period after creationI AccessI Modification of data

I Actions can be:I Compression TieringI Tablespace Tiering

I Policies are inherited from tablespace or tableI Policies can be executed in background or immediate




ILM - Simple Example




Flex ASM

I Pre-Oracle 12c:I an local Oracle database instance depends on a working

local ASM instanceI a failure to the local ASM instance leads to a complete

outage of all local instancedI Idea: One big "storage" cluster for ALL DBs




I Oracle 12c:I less per-node ASM overheadI Increased database availability as databases can use

remote ASM instances




Flex Cluster

I New type of ClusterI Further enhance the ability to build bigger clusters to host

oracle applications and 3rd party softwareI Flex Clusters consist of up to 64 HUB and LEAF nodes (no

limit know at the moment) -they all belong to one big clusterI Together with Server Pools easy management of big

clusters is possible (manual mode still possible)I Hub Nodes are like ’normal’ cluster nodes: tightly

connected with access to shared storage




Flex Cluster - conted.

I In a Flex Cluster the Hub Nodes provide storage for theLeaf Nodes

I Leaf Nodes do not need shared storage access; theyaccess it indirectly over the Hub Nodes

I Database Instances can run on both hub and leaf nodesI Flex Clusters without Leaf Nodes are possible; Leaf Nodes

without Hub Nodes notI Transition from ’normal’ cluster to Flex Cluster and vice

versa possible




Larger columns

I Oracle Database 12c increases VARCHAR2,NVARCHAR2 and RAW columns to 32 KB size

I Easy migration of existing databases to UNICODE (nocode changes necessary)

I Easy migration of non-Oracle schemas




Policy-managed Databases

I Pre-Oracle 12c:I Organize Server in Server PoolsI Assign databases to server poolsI Clusterware automatically starts instances on the serverI Simplifies management of many node




I Oracle 12c:I addNode.sh simplifiedI can use different sized serversI Server Pools now understand differences in servers




What-If EvaluationI Changes in Cluster resources might leaded to

unpredictable resultsI not possible to test the outcome of the change beforehandI What-IF evaluation helps to solved that for server pool,

resource and server modification




Oracle Grid Home ServerI Oracle Grid Home Server allows:

I Centralized management and deployment of:I Database application homes (atm no Grid Infrastructure

homes and Operating system homes supported)I 3rd Party software images

I Update hundreds databases at onceI Group gold images into ’patching units’ (e.g. organized by

db version, application)




OtherI Global Index Maintanance delayable for DROP and

TRUNCATE partitionsI Online MOVE Partitions (non-blocking DDL, DML can be

performed while being moved, Global indexes aremaintained so no rebuild necessary)

I Adaptive Query optimization (plans can change duringexecution if estimation and therefore joining mechanismproofs to be wrong)

I Automatic Group Column Detection (no need for the DBAto know about columns referenced together)

I Concurrent Statistics Gathering (gathering of statisticsamong multiple tables / schemas / tables / partitions orsub-partitions)




Other -cont.

I New type of statistics type for tables with more than 254NDV:

I Top-Frequency Histogram: for tables where a small numberof NDV occupy most of the data (99%)

I Hybrid Histogram: Combines Height-based and frequencyhistogram

I Online Statistics Gathering during Bulk Load (e.g. CTAS,Direct Load)

I Parallel DML on Secure FilesI Degree of DATA PUMP Compression can be controlled

(LOW, MEDIUM, HIGH)I DATA PUMP option to disable redo logging during import




Other -cont.I ASM Disk Scrubbing and automatic repair in the

backgroundI PGA_AGGREGATE_SIZE_LIMIT: Guaranteed limit of

PGA; if limit exceeded session with highest consumption isstopped

I Queryable Patch InventoryI ACFS Support for ALL Database Files (including Data

Files)I ACFS writeable snapshotsI Support for IPv6 on RAC Public NetworkI SQLNet data compression from server to clientI HA-IP ("multicast") support on Windows




Q&A

Fragen?

Kontakt:Ronny [email protected]



oracles next database version - new...

Documents