Interested in running Oracle Database 12c on Exadata? My Oracle Support Note 1571789.1 has some exciting news! Here are the highlights....
o
Support for Oracle Database Releases 12c Release 1 (12.1) and 11g Release
2 (11.2)
§ Oracle
Exadata Storage Server Software12c Release 1
(12.1) supports Oracle Database releases 12c Release
1 (12.1) and 11g Release 2 (11.2) running on a
single Oracle Exadata Database Machine. The database servers get full
performance, such as smart scans, fast file creation, and fast incremental
backup, from all Exadata Storage Servers running Oracle Exadata Storage Server
Software re12c Release 1 (12.1)
o
IORM Support for Container Databases and
Pluggable Databases
§ Oracle Database 12c Release 1 (12.1)
supports I/O Resource Management (IORM) priorization to manage I/O resource
utilization among different pluggable databases (PDBs) as well as manage the
workloads within each PDB.
o
Cell to Cell Data Transfer
§ Minimum
software: Oracle Database 12c Release 1 (12.1)
or later, and Oracle Exadata Storage Server Software 12c Release
1 (12.1) or later.
§ In
earlier releases, Exadata Cells did not directly communicate to each other. Any
data movement between the cells was done through the database servers. Data was
read from a source cell into database server memory, and then written out to
the destination cell. Starting with Oracle Exadata Storage Server Software 12c Release 1 (12.1), database server processes can
offload data transfer to cells. A database server instructs the destination
cell to read the data directly from the source cell, and write the data to its
local disk. This reduces the amount of data transferred across the fabric by
half, reducing Infiniband bandwidth consumption, and memory requirements on the
database server. In addition, Oracle Automatic Storage Management (Oracle ASM)
resynchronization, resilver, and rebalance use this feature to offload data
movement. This provides improved bandwidth utilization at the Infiniband fabric
level as well as saving PGA memory in Oracle ASM instances. No configuration is
needed to utilize this feature