2014/07/25

Oracle Multitenant - PDB Clone New Features (12.1.0.2.0) - Part III

As you know, Oracle Database 12c Release 1 (12.1.0.2.0) already released at July 22, 2014. You can download new release from here.

With this new release coming some new features. This article series covers PDB Clone new features of Oracle Multitenant option of Oracle Database 12c Release 1 (12.1.0.2.0).

This article is in four parts:
  1. Excluding Data When Cloning a PDB
  2. Non-CDB Adopt to CDB as a PDB.
  3. PDB Subset Cloning 
  4. PDB Snapshot Cloning
Part III. PDB Subset Cloning

Sometimes we using many schemas that each supported a different application in a database (Schema Consolidation).  With Oracle Database 12c coming new option Oracle Multitenant, which is helpful for simplify consolidate databases.Database Consolidation means, each pluggable database (PDB) support a different application and all pluggable databases adopted in same Multitenant Container Database (CDB).

If we move a non-CDB to a PDB, and the non-CDB had different schemas that each supported a different application, then we need database consalidation. In other words we must separate schemas to defferent PDB. We can use USER_TABLESPACES, which is new clause in 12.1.0.2.0, to separate the data belonging to each schema into a separate PDB, assuming that each schema used a separate tablespace in the non-CDB.

USER_TABLESPACES clause to specify one of the following options:
  • List one or more tablespaces to include.
  • Specify ALL, the default, to include all of the tablespaces.
  • Specify ALL EXCEPT to include all of the tablespaces, except for the tablespaces listed.
  • Specify NONE to exclude all of the tablespaces.
The tablespaces that are excluded by this clause are offline in the new PDB, and all data files that belong to these tablespaces are unnamed and offline.This clause does not apply to the SYSTEM, SYSAUX, or TEMP tablespaces. Do not include these tablespaces in a tablespace list for this clause.

Follow my examples:

2014/07/24

Oracle Multitenant - PDB Clone New Features (12.1.0.2.0) - Part II

As you know, Oracle Database 12c Release 1 (12.1.0.2.0) already released at July 22, 2014. You can download new release from here.

With this new release coming some new features. This article series covers PDB Clone new features of Oracle Multitenant option of Oracle Database 12c Release 1 (12.1.0.2.0). 

This article is in four parts: 
  1. Excluding Data When Cloning a PDB
  2. Non-CDB Adopt to CDB as a PDB.
  3. PDB Subset Cloning 
  4. PDB Snapshot Cloning

Part II. Non-CDB Adopt to CDB as a PDB.

The new release of Oracle Multitenant fully supports remote full and snapshot clones over a database link. A non-multitenant container database (CDB) can be adopted as a pluggable database (PDB) simply by cloning it over a database link.

This feature further improves rapid provisioning of pluggable databases. Administrators can spend less time on provisioning and focus more on other innovative operations. Follow examples:

I'll create a PDB using database link from following non-CDB:

Oracle Multitenant - PDB Clone New Features (12.1.0.2.0) - Part I

As you know, Oracle Database 12c Release 1 (12.1.0.2.0) already released at July 22, 2014. You can download new release from here.

With this new release coming some new features. This article series covers PDB Clone new features of Oracle Multitenant option of Oracle Database 12c Release 1 (12.1.0.2.0). 

This article is in four parts: 
  1. Excluding Data When Cloning a PDB
  2. Non-CDB Adopt to CDB as a PDB.
  3. PDB Subset Cloning 
  4. PDB Snapshot Cloning
      Part I:  Excluding Data When Cloning a PDB

      We can create clone of PDB with CREATE PLUGGABLE DATABASE ... FROM statement from existing PDB. All clones of PDB contains all object definitions and data in PDB. Sometimes we need quickly creating clones of a PDB with only the users object definitions and no data. New NO DATA clause included the CREATE PLUGGABLE DATABASE ... FROM statement in 12.1.0.2.0 version. The NO DATA clause specifies that a PDB's data model definition is cloned but not the PDB's data. When you using NO DATA Clause in CREATE PLUGGABLE DATABASE ... FROM statement, the dictionary data in the source PDB is cloned, but all user-created table and index data from the source PDB is excluded. Follow examples :

      2014/07/23

      Oracle Database 12c Release 1 (12.1.0.2) New Features

      Oracle Database 12.1.0.2 is available for download now.  here

      1. Advanced Index Compression

      Advanced Index Compression works well on all supported indexes, including those indexes that are not good candidates for the existing prefix compression feature; including indexes with no, or few, duplicate values in the leading columns of the index.

      Advanced Index Compression improves the compression ratios significantly while still providing efficient access to the index.

      2. Approximate Count Distinct

      The new and optimized SQL function, APPROX_COUNT_DISTINCT(), provides approximate count distinct aggregation. Processing of large volumes of data is significantly faster than the exact aggregation, especially for data sets with a large number of distinct values, with negligible deviation from the exact result.

      The need to count distinct values is a common operation in today's data analysis. Optimizing the processing time and resource consumption by orders of magnitude while providing almost exact results speeds up any existing processing and enables new levels of analytical insight.

      3. Attribute Clustering

      Attribute clustering is a table-level directive that clusters data in close physical proximity based on the content of certain columns. This directive applies to any kind of direct path operation, such as a bulk insert or a move operation.

      Storing data that logically belongs together in close physical proximity can greatly reduce the amount of data to be processed and can lead to better compression ratios.

      4. Automatic Big Table Caching

      In previous releases, in-memory parallel query did not work well when multiple scans contended for cache memory. This feature implements a new cache called big table cache for table scan workload.

      This big table cache provides significant performance improvements for full table scans on tables that do not fit entirely into the buffer cache.

      5. FDA Support for CDBs

      Flashback Data Archive (FDA) is supported for multitenant container databases (CDBs) in this release.

      Customers can now use Flashback Data Archive in databases that they are consolidating using Oracle Multitenant, providing the benefits of easy history tracking to applications using pluggable databases (PDB) in a multitenant container database.

      6. Full Database Caching

      Full database caching can be used to cache the entire database in memory. It should be used when the buffer cache size of the database instance is greater than the whole database size. In Oracle RAC systems, for well-partitioned applications, this feature can be used when the combined buffer caches of all instances, with some extra space to handle duplicate cached blocks between instances, is greater than the database size.

      Caching the entire database provides significant performance benefits, especially for workloads that were previously limited by I/O throughput or response time. More specifically, this feature improves the performance of full table scans by forcing all tables to be cached. This is a change from the default behavior in which larger tables are not kept in the buffer cache for full table scans.

      7. In-Memory Aggregation

      In-Memory Aggregation optimizes queries that join dimension tables to fact tables and aggregate data (for example, star queries) using CPU and memory efficient KEY VECTOR and VECTOR GROUP BY aggregation operations. These operations may be automatically chosen by the SQL optimizer based on cost estimates.


      2014/07/17

      OTN Article : Oracle Database 12c – Nuevas Características de "Oracle Partitioning"

      Oracle Technology Network - OTN (Latina America) published our 6th article in Spanish Language.
      This article entitled : Oracle Database 12c – Nuevas Características de "Oracle Partitioning") 
      by Joel Perez (Oracle ACED) and Mahir M. Quluzade (OCE)  Published : 17 July 2014

      Article link : Oracle Database 12c: Nuevas Características de “Oracle Partitioning”
      This article covers a bit new features of "Oracle Partitioning" on Oracle Database 12c (12.1)















      Regards
      Mahir M. Quluzade