![]() ![]() And of course, I will use the AutoUpgrade. But here, I will upgrade my 11.2.0.4 and 12.2.0.1 non-CDB databases in our Hands-On Lab at first. Whether you do this at first or after plugin, is up to you. And this data dictionary must be adjusted to match the dictionary version of the receiving CDB. But I leave it to you to choose your preferred option. I prefer the latter solution which I describe in this article for the simple reason that there’s proven fallback for the upgrade case whereas there’s no easy fallback once you plugged in. ![]() When your source is Oracle 12.2.0.1 or higher, you have more freedom if you’d like to plugin at first, and then upgrade, or if you upgrade first, and then plugin. Upgrade to matching version of CDB, then plugin non-CDB as PDB, and finally convert it to a PDBĭatabase Migration from non-CDB to PDB – Upgrade, plug in, convertĪs of now, you can’t plugin an Oracle 11.2 database. Upgrade, plugin, copy (optional) and noncdb_to_pdb.sql High Level Overview Endianness change possible: But since Oracle 12.2.0.1, there are a few other options available. I demonstrated this technique on the blog already a while ago. which I’ll showcase in the other blog posts. As first blog post of this series about Database Migration from non-CDB to PDB – Upgrade, plug in, convert I will explain the most straight forward approach of going to Single- or Multitenant. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |