Re: Pluggable database duplication
From: vit\.spinka <vit.spinka_at_vitspinka.cz>
Date: Thu, 18 Feb 2016 21:29:01 +0100
Message-Id: <O2RFKD$87595B33AF391272618E6A416F2825A1_at_vitspinka.cz>
> I have been asked that by a user who is used to restoring SQL Server databases to another machine, without stopping the access. Strange that Oracle didn't think of something that common in SQL Server world or DB2 world. I am pretty sure they did think about it. It just did not get done in time to be included in 12.1. After all, multittenant is a major change to the database internals and there are still features of the database that does not work with it (from top of my head: Heat Map and Automatic Data optimization, flashback per PDB, memory limits...) or those that were added only in 12.1.0.2 (FDA, remote clones)...
Date: Thu, 18 Feb 2016 21:29:01 +0100
Message-Id: <O2RFKD$87595B33AF391272618E6A416F2825A1_at_vitspinka.cz>
> I have been asked that by a user who is used to restoring SQL Server databases to another machine, without stopping the access. Strange that Oracle didn't think of something that common in SQL Server world or DB2 world. I am pretty sure they did think about it. It just did not get done in time to be included in 12.1. After all, multittenant is a major change to the database internals and there are still features of the database that does not work with it (from top of my head: Heat Map and Automatic Data optimization, flashback per PDB, memory limits...) or those that were added only in 12.1.0.2 (FDA, remote clones)...
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Feb 18 2016 - 21:29:01 CET