Those of you who have been to our workshops in the past 3 years know that we promote one feature as the ultimate killer feature for moving to Oracle Database 19c and 23ai: Refreshable Clones. These work not only from PDB to PDB, but magically also with a non-CDB. And our teams works with a good number of customers using exactly this technique to Oracle 23ai. Now, we talked about it. And we blogged about it (see below). But there is a brand-new MOS note out there showcasing an AutoUpgrade migration to Oracle 23ai Exascale with Refreshable Clones.
Photo by Peter Hoogmoed on Unsplash
Why is this so important?
Moving to Oracle Database 23ai Exascale can be done directly. And the customers we worked with wanted to have native (non-virtualized) Exascale from scratch. Especially its superb snapshot capabilities are amazing as I can tell after working with customers. The easiest way into it, especially when you are going to test it multiple times, are clearly Refreshable Clone PDBs. And AutoUpgrade fully automates this procedure, Daniel and Alex blogged about it multiple times, and you will find the links below.
New MOS Note
This MOS note describes the approach:
It shows the entire approach including encryption – and AutoUpgrade is the key to it. We do exactly this with several large customers right now, and once you follow the best practices, it works absolutely smoothly.
Further Links and Information
- MOS Note: 3086805.1 – 19c ASM to 23ai Exascale Direct Migration using AutoUpgrade via Refreshable Clone
- DOHdatabase.com: When a refreshable clone takes over the service
- DOHdatabase.com: Using Refreshable Clones from a standby
- DOHdatabase.com: Let me kill your network
- AlexZaballa.com: Refreshable Clones for ExaCS
–Mike
