Upgrading the PDB$SEED takes always longer than any other container.
What is the reason for an upgrade of the PDB$SEED taking so much longer in a real world environment?
How does an upgrade with Oracle Multitenant work?
I have written several blog posts in the past about the different techniques to upgrade an Oracle Multitenant environment:
- Upgrade Everything At Once
- Upgrade via Unplug/Plug/Upgrade
The interesting case happens in the “Everything At Once“.… [Read More]
There’s a new and improved version of the preupgrade.jar (build 5 – May 2017) available for download from MyOracle Support:
The same note will get you access also to the most recent builds of preupgrd.sql for upgrades to Oracle Database 12.1 and utlu112i.sql for the unlikely event you’ll have to upgrade a database to Oracle 18.104.22.168.… [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 22.214.171.124 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 126.96.36.199 the upgrade – regardless of DBUA or catctl.pl – will fail with an
ORA-1450: maximum key length (1478) exceeded.… [Read More]
A while back I did blog about the new
-R option of the parallel upgrade tool catctl.pl in Oracle Database 12.2.
Restarting a failed Database Upgrade with catctl.pl
And in case you will do a real Multitenant upgrade and fail – as it happened to me today due to “
no space left on device” (no audit files could be written anymore) I tried the
-R option as well based on Joe’s (our lead
catctl.pl developer) recommendation:
$ $ORACLE_HOME/perl/bin/perl catctl.pl -n 6 -R -l /home/oracle/mike2 catupgrd.sql
Argument list for [catctl.pl]
Run in c = 0
Do not run in C = 0
Input Directory d = 0
Echo OFF e = 1
Simulate E = 0
Forced cleanup F = 0
Log Id i = 0
Child Process I = 0
Log Dir l = /home/oracle/mike2
Priority List Name L = 0
Upgrade Mode active M = 0
SQL Process Count n = 6
SQL PDB Process Count N = 0
Open Mode Normal o = 0
Start Phase p = 0
End Phase P = 0
Reverse Order r = 0
AutoUpgrade Resume R = 1
Script s = 0
Serial Run S = 0
RO User Tablespaces T = 0
Display Phases y = 0
Debug catcon.pm z = 0
Debug catctl.pl Z = 0
catctl.pl VERSION: [188.8.131.52.0]
/u01/app/oracle/product/184.108.40.206/rdbms/admin/orahome = [/u01/app/oracle/product/220.127.116.11]
/u01/app/oracle/product/18.104.22.168/bin/orabasehome = [/u01/app/oracle/product/22.214.171.124]
catctlGetOrabase = [/u01/app/oracle/product/126.96.36.199]
Analyzing file /u01/app/oracle/product/188.8.131.52/rdbms/admin/catupgrd.sql
Log file directory = [/home/oracle/mike2]
catcon: ALL catcon-related output will be written to [/home/oracle/mike2/catupgrd_catcon_10640.lst]
catcon: See [/home/oracle/mike2/catupgrd*.log] files for output generated by scripts
catcon: See [/home/oracle/mike2/catupgrd_*.lst] files for spool files, if any
Number of Cpus = 2
Database Name = CDB1
DataBase Version = 184.108.40.206.0
Parallel SQL Process Count (PDB) = 2
Parallel SQL Process Count (CDB$ROOT) = 6
Concurrent PDB Upgrades = 3
PDB$SEED Open Mode = [READ ONLY] NO UPGRADE WILL BE PERFORMED
PDB1 Open Mode = [MOUNTED] NO UPGRADE WILL BE PERFORMED
PDB2 Open Mode = [MOUNTED] NO UPGRADE WILL BE PERFORMED
PDB4 Open Mode = [READ WRITE] NO UPGRADE WILL BE PERFORMED
Generated PDB Inclusion:[PDB3 PDB5]
Components in [CDB$ROOT]
Installed [CATALOG CATPROC XDB]
Not Installed [APEX APS CATJAVA CONTEXT DV EM JAVAVM MGW ODM OLS ORDIM OWM RAC SDO WK XML XOQ]
** Database CDB$ROOT has already been upgraded successfully.
… [Read More]
I did blog about this topic a while back.
Upgrade PDBs – Everything At Once (Full CDB Upgrade)
Theory is nice but it’s a big difference when you do it the first time with a non-lab deployment at a customer with a real Multitenant database with almost 100 PDBs.Then you learn that neither the documentation nor my previous blog post contain all the necessary steps.… [Read More]
We discussed an interesting upgrade case last week together with our upgrade colleagues in Support – and learned the double-hop (or triple-hop) upgrade case is not described in the documentation somewhere.
What is a multiple-hop upgrade?
Triple Jump – Willie Banks – Olympics 1988 Seoul
Actually this describes the case where somebody can’t upgrade directly and has to do several upgrades in a sequence to reach the targeted release.… [Read More]
2 customers requested a bit more explanation on how to:
Convert and Plugin an Oracle 12.1 non-CDB database into an Oracle 12.2 container database
Cool, I like that 🙂 I will do this right away and use the approach to Upgrade first, then Plugin afterwards.
Upgrading an Oracle 220.127.116.11 database to Oracle 18.104.22.168
First the preupgrade.jar must be executed – please download always the most recent version from MOS Note:884522.1 as the version we publish is usually newer including important improvements (and fixes) than the version you’ll get with the release drop.… [Read More]