Blog - ORACLE-DB12c

[Pour les lecteurs français, cliquez sur le drapeau en haut à gauche pour basculer sur la page en français]

Monday 09 septembre was in Paris (France) a big Oracle show for the launch of the Oracle Database 12c.

Tom Kyte was the "guest guest" of this exhibition. His presentation was very clear, specially if you consider that he was the only one who talked in english. It was a really nice moment.
As he said, he lived 2 majors rupture of Oracle Database:
* First, 34 years ago with Oracle 6, when the database became multi-processes.
* And now, with the 12c, and the 600 new features, specially the plugable databases.

It's why I put the title "a new era?".

In a quick presentation, it was showed how to duplicate a database inside a CDB (Container DataBase). The operation is very fast, as it's just a declaration. The datafiles are not duplicated immediatly. It's like in VirtualBox, when a server is linked to the source. Only the blocks modified are written to disk.
It's very impressive. But I notice a limitation: the source database was stopped. This feature should be better with a kind of "begin backup" mode, to not impact the end-users, specially for duplicating a production DB? It's something to investigate.

It's a lot of new features for DataGuard (DG), actually in "Active DG" payable option, of course.
* Now standby environment are not solely, and trying to connect to each other. A new kind of structure, similar of the RAC architecture, bounds them and improve the communication as a global system.
* Another improvement is the synchronous replication (FAR Sync) on long range, with the "repeater" server.
* It's coupled with the "FAST Sync" to speed up the synchronous commit on DB database.

It's was another nice presentation from the CERN which is a beta-tester of the 12c. They have more than 100 PB (1PB = 1024 TB) of datas, and still increasing. They were facing 2 difficulties::
* Long range duplication of datas: eased with the new DG features.
* Transaction errors: when a transaction is lost (disconnected) around the commit, it's possible to redo it automatically through the JDBC driver (only this one for the moment). This sounds useful for them a they have massive insertion of datas. But for standard OLTP/ERP users, they just have to reconnect, query the datas inside the application to search if the insert was done or not.

Another interesting presentation of the automatic "online compression" without any scripting, coupled with the "multi-tiering" of datas on different quality of disks. Available in "advanced compression" payable option.
This is only available for SUN/zfs storage. I guess, in the next versions, more storage vendors (EMC, Netapp, ...) will be compatible.

No big announcements for the RAC. The only one, is the "FLEX ASM". This means that a Node of the RAC is not obliged to run a ASM instance, it can be a client of an another one.

Concerning the licensing, no mentions, of course.
It seems that the CDB multi-tennant will an additionnal license from the database. And CDB single-tennant will be included in the cost of the DB.
It's also possible to create a database in the traditionnal way. But the use of the CDB single-tennant will ease the migration process.



Finally, at the end, a very non-oracle presentation of Jean-François CLERVOY, a french astronaut, who went 3 times in space.
His presentation of his experience was impressive, and would think to remain humble face to the vastness of the space and the fragility of our planet.
 

Close