Oracle Database 12c "New features"

2,036 views

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,036
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
185
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Oracle Database 12c "New features"

  1. 1. New features in Oracle Database 12c SQL: Increased size limit for VARCHAR2, NVARCHAR2, and RAW datatypes to 32K (from 4K). We can make a column invisible. SQL> create table test (column-name column-type invisible); SQL> alter table table-name modify column-name invisible; SQL> alter table table-name modify column-name visible; Oracle Database 12c has new feature called "Identity Columns" which are auto-incremented at the time of insertion (like in MySQL). SQL> create table dept (dept_id number generated as identity, dept_namevarchar); SQL> create table dept (dept_id number generated as identity (start with 1 increment by 1 cache 20 noorder), dept_namevarchar); Temporary undo (for global temporary tables) will not generate undo. No need to shutdown database for changing archive log mode. Duplicate Indexes - Create duplicate indexes on the same set of columns. Till Oracle 11.2, if we try to create an index using the same columns, in the same order, as an existing index, we'll get an error. In some cases, we might want two different types of index on the same data (such as in a datawarehouse where we might want a bitmap index on the leading edge of a set of columns that exists in a Btreeindex). PL/SQL inside SQL: this new feature allows to use DDL inside SQL statements (i.e.: to create a one shot function) The object DEFAULT clause has been enhanced. Adding a column to an existing table with a default value (much faster with Oracle 12c and it consumes less space than before, pointer to the Oracle Data Dictionary), applies also to sequences, identity types etc... Pagination query, SQL keywords to limit the number of records to be displayed, and to replace ROWNUM records. select ... fetch first n rows only; select ... offset m rows fetch next n rows only; select ... fetch first n percent rows only;
  2. 2. select ... fetch first n percent rows with ties; Moving and Renaming datafile is now ONLINE, no need to put datafile in offline. The TRUNCATE command has been enhanced with a CASCADE option which follows child records. Reduces contents of regular UNDO, allowing better flashback operations. PL/SQL: PL/SQL Unit Security - A role can now be granted to a code unit. That means you can determine at a very fine grain, who can access a specific unit of code. SQL WITH Clause Enhancement - In Oracle 12c, we can declare PL/SQL functions in the WITH Clause of a select statement. Implicit Result Sets - create a procedure, open a ref cursor, return the results. No types, not muss, no mess. Streamlined data access (kind of a catch up to other databases). MapReduce in the Database - MapReduce can be run from PL/SQL directly in the database. We can use Booleans values in dynamic PL/SQL. Still no Booleans as database types. Database: New background processes - LREG (Listener Registration), SA (SGA Allocator), RM Oracle Database 12c Data Pump will allow turning off redo for the import operation (only). Enhanced statistics (Hybrid histograms for more than 254 distinct values, dynamic sampling up to eleven, and stats automatically gathered during load). Row pattern matching - "MATCH_RECOGNIZATION" (identification of patterns within a table ordered/sorted by the SQL statement). Adaptive execution plans (change of the plan at runtime). Oracle 12c includes database level redaction, allowing granular control of access to sensitive data. Oracle introduced parameter PGA_AGGREGATE_LIMIT which is a real/PGA memory limit. UNDO for temporary tables can now be managed in TEMP, rather than the regular UNDO tablespace. Oracle Enterprise Manage Express (lightweight EM Cloud Control 12c version), replaces the Oracle Database console and, is installed automatically. Reduces the size of redo associated with recovering the regular UNDO tablespace.
  3. 3. ASM: (Oracle Grid Infrastructure new features) Introduction of Flex ASM, ASM would run only on 3 instances on a cluster even if more than 3, the instances that not have an ASM would request remote ASM, typically like SCAN. In normal conditions in a node if ASM fails the entire node will be useless, where in 12c the ability to get the extent map from remote ASM instance makes the node useful. Introduction of Flex Cluster, with light weight cluster stack, leaf node and traditional stack hub node, application layer is the typical example of leaf nodes where they don't require any network heartbeat. RMAN: RMAN TABLE Point-In-Time Recovery (combination of Data Pump and RMAN, auxiliary instance required). Running SQL commands in RMAN without SQL keyword. Recover or copy files from Standby databases. Refresh a single datafile on the primary from the standby (or standby from primary). Table level restoration i.e object level. Incremental recovery more faster, many of the tasks removed. Rolling forward/Synchronizing a standby database. Partitioning: Partitioning enhancements (partition truncate, cascading, global index cleanup, online moving of a partition, ...) Multiple partition operations in a single DDL. Interval-Ref Partitions - we can create a ref partition (to relate several tables with the same partitions) as a sub-partition to the interval type. Cascade for TRUNCATE and EXCHANGE partition. Asynchronous Global Index maintenance for DROP and TRUNCATE. Command returns instantly, but index cleanup happens later. Online move of a partition(without DBMS_REDEFINTIION). Patching: Centralised patching. We can test patches on database copies, rolling patches out centrally once testing is complete.
  4. 4. Compression: Automated compression with heat map. Optimisation can be run on live databases with no disruption. Data optimization will monitor the data usage and with policy archive old data and hot data will be compressed for faster access. Inactive data can be more aggressively compressed or archived, greatly reducing storage costs. Advanced Row compression (for Hot Data). Columnar Query compression (for Warm Data). Columnar Archive compression (for Archive Data). Data Guard: Oracle Database 12c introduces a new redo transportation method which omits the acknowledgement (to primary) of the transaction on the standby. This feature is called "Fast Sync" redo transport. Creating a new type of redo destination called "Far Sync Standby". A "Far Sync Standby" is composed only of the standby control files, the standby redo logs and some disk space for archive logs which shall be sent to the Standby database. Failover & Switchover operations are totally transparent as the "Far Sync Standby" cannot be used as the target. Data Guard Broker commands have been extended. The "validate database" command to checks whether the database is ready for role transition or not. Dataguard Broker now supports cascaded standby. Global Temporary Tables can now be used on an Active Guard standby database. Pluggable Databases: In Oracle 12c, in a pluggable database environment, we can create a single database container, and plug multiple databases into this container. All these databases then share the exact same oracle server/background processes and memory, unlike the previous versions where each database has its own background processes and shared memory. This helps in database consolidation and reduces the overhead of managing multiple desperate databases. Container Database (CDB): Are the core data dictionary objects that come after an Oracle database installation. Pluggable Database (PDB): Data dictionary objects and data related to the application. We can have many PDB plugged into a single CDB. A new admin role "CDB Administrator" has been introduced in Oracle 12.1 release databases.
  5. 5. Multiple databases can then share a master LGWR process, but have their own dedicated LGWR process within the container. All Oracle database options/features are available on the PDB level. RMAN backup at CDB level. We can unplug a PDB from a CDB to another CDB. PDB's can be cloned inside the CDB. Management of PDB (clone/creation/plug/unplug/drop) are implemented as SQLs. Extremely fast PDB-provisioning (clone inside the CDB), because each CDB comes with a “PDB Seed”. Database patch/upgrade management very quick as CDB is a single point of installation. Each PDB has its own data dictionary. Data Guard configuration on CDB as whole. RMAN point-in-time recovery at PDB level (while other PDB's remains open). Resource Manager is extended for creating, unplugging, plugging in, and cloning, dropping or even setting up for the open mode of the PDB. Flashback of a PDB should be available for Oracle 12c Release 2. Entire containers can be backed up in single run, regardless of how many databases they contain. Upgrade one container database and all pluggable databases are upgraded. New Commands : create pluggable database ... alter pluggable database ... drop pluggable database ... New Views/Packages in Oracle 12c Release1: dba_pdbs v$pdbs cdb_data_files dbms_pdb
  6. 6. dbms_qopatch

×