In the newer releases of Oracle database you may see components with status OPTION OFF in the database’s registry. But what happens to components with OPTION OFF status during upgrade? Will those stay on the old release?
What happens to components with OPTION OFF status during upgrade?
You may have a quick look into your DBA_REGISTRY (or CDB_REGISTRY).… [Read More]
A customer of mine hit an issue recently when upgrading to Oracle Database 22.214.171.124. They did everything correctly but received a ton of issues from the Data Guard Broker. A rule says: When you upgrade, disable the Data Guard Broker. But I can’t blame the customer as this “rule” is well hidden in the documentation.… [Read More]
On a regular basis the Database Upgrade Team releases new and improved versions of the preupgrade tools via a MyOracle Support note. And it’s time again: the September 2017 releases of preupgrade.jar and preupgrd.sql are available for download.
September 2017 releases of preupgrade.jar and preupgrd.sql are available
Please ALWAYS download the most recent versions of preupgrade.jar for upgrades to Oracle Database 12.2 and preupgrd.sql (including utluppkg.sql) for Oracle Database 126.96.36.199 upgrade from MOS Note: 884522.1.… [Read More]
Enterprise Manager (EM) clean up in Oracle Database 11.2-12.2 is targeting Enterprise Manager Database Control only. EM DB Control does not exist anymore since Oracle Database 12c and got replaced by EM Express, a light-weight EM.
Enterprise Manager (EM) Clean Up in Oracle Database 11.2-12.2
As Enterprise Manager Database Control gets replaced by EM Express since Oracle Database 188.8.131.52 its repository must be removed when upgrading to Oracle Database 12c or later.… [Read More]
The script noncdb_to_pdb.sql gets run only once in the life span of your database. It gets executed when a regular Oracle database (non-CDB) gets move to become part of a Single-/Multitenant deployment as a pluggable database (PDB). But why does it take so long?
You will never run this script again for this database.… [Read More]
Recently we got alerted by a customer and a colleague from Italy about an issue with the upgrade from Oracle 12.1.0.x to Oracle 184.108.40.206 if – and only if – your database got created with 2k or 4k db block size.
If your database got created with 2k or 4k db block size, and you attempt an upgrade from any upgrade-supported Oracle version to Oracle Database 220.127.116.11 the upgrade – regardless of DBUA or catctl.pl – will fail with an ORA-1450: maximum key length (1478) exceeded.… [Read More]