Our doc team has put a lot of effort together with the help of my team mates and created these 9 Upgrade and Migration Scenarios as part of the official Oracle documentation.
The idea is to cut out the most common use cases and give a quick and comprehensive overview on all necessary steps.
9 Upgrade and Migration Scenarios
These comprehensive 9 scenarios cover non-CDB and PDB/CDB as well as changing to new hardware:
- Migrating and Converting Non-CDBs to a PDB with a Different Endian Operating System
HTML
PDF
Show Details - Migrating Non-CDBs to New Hardware with a Different Endian Operating System and for a New Release
HTML
PDF
Show Details - Migrating Non-CDBs to New Hardware with a Different Endian Operating System and for the Same Release
HTML
PDF
Show Details - Migrating Non-CDBs to New Hardware with the Same Operating System and for a New Release
HTML
PDF
Show Details - Migrating Non-CDBs to New Hardware with the Same Operating System and Release
HTML
PDF
Show Details - Unplugging, Plugging, and Upgrading a PDB to a New CDB
HTML
PDF
Show Details - Upgrading and Converting Non-CDBs to a PDB with the Same Operating System
HTML
PDF
Show Details - Upgrading Non-CDBs on the Same System
HTML
PDF
Show Details - Upgrading PDBs in Parallel on the Same System
HTML
PDF
Show Details
Further Information
Of course you will find some of these examples here on the blog as well, such as:
- Upgrade to Oracle 18.3.0 on premises
- Unplug a 12.2.0.1 PDB and Plug into 18c in the Cloud
- Upgrade PDB via unplug/plug/upgrade – One at a time
–Mike
this is crazy. So much detailed information on each topic. Someone has put much hard work making into this.
Thanks for the sharing !
Mike,
If the SYS password in 11g database is only version 10G, it will not get changed to 11G 12C, no matter what. The USER$ table still has the hash for the password. All documented methods of changing the password version do not work for SYS. I have a SR open, but nothing from support so far.
Do you have any insight?
Thanks,
Arun