Roy just uploaded a newer version of our Upgrade Hands-On Lab – Oracle Database 126.96.36.199 – May 2018.
The previous version had – I believe – and early drop of Oracle 188.8.131.52 installed. And recently somebody complained that certain Multitenant operations such as Hot Cloning with Oracle Database 184.108.40.206 don’t work but result in errors. Therefore, we updated it.
Upgrade Hands-On Lab – Oracle Database 220.127.116.11 – May 2018
The size requirements unfortunately are still the same. Your machine should have 8GB of RAM and you will need a bit more than 60GB free space on disk. You “could” run the lab also from an USB 3.0 external drive – but expect some slowness. And in our labs we sometimes see corruptions in this case with external drives.
Inside the lab you will find:
- Oracle Database 18.104.22.168
- Oracle Database 22.214.171.124
- Oracle Database 126.96.36.199
and databases to upgrade, to migrate and Oracle Multitenant.
This picture demonstrates what is setup by ourselves – but of course it’s a playground environment. So feel free to change, try out, alter etc. And you can always go back to a Snapshot if you create any upfront or in-between.
The lab has been patched I believe with January 2018 PSU for Oracle 188.8.131.52, BP for Oracle 184.108.40.206 and RU for Oracle 220.127.116.11. In case you wonder why there aren’t the April 2018 patch bundles installed. Copying the lab to the OTN page is no easy process and takes a while for us. Roy started the process weeks ago when I had the patches already applied but his version of the lab didn’t have them yet. And we can’t share a 60GB lab easily unfortunately over the pond.
And yes, a newer version with Oracle 18c will be available as soon as Oracle 18c on-premises is available as well (July 2018 most likely).
Thanks for a great blog. I tend to read quite a few of them, but never really get to the hands-on.
So perhaps a stupid question, but can I get the hands-on lab? Is it online for download, or how does it work?
This is the 18.104.22.168 version with the Jan 2018 patches in it.
I’m reshaping the lab right now for 18.3.0 but can upload it only once 18c on-prem is generally available (mid of July 2018).
Mike, We need the old lab 12.1 to 12.2.
no, you don’t need the old lab 🙂 Trust me!
Take the 18c one as 18c is nothing else than 22.214.171.124. And if you want, 126.96.36.199 is installed within minutes. If you REALLY REALLY need it.
The old lab is not stored on OTN anymore – and actually I by myself would need to dig deep into my TimeMachine backups to dig it out again.
Now to the next level. Multiple Instances off one 12.1 home, want to upgrade to 12.2 apply RU as well.
opatch Upgraded to v13 (v12 needed as minimum)
RU applied to 12.2 ORACLE_HOME
re-home to 12.2
Do I need to run $ORACLE_12.2HOME/OPatch/opatch datapatch verbose
Is this indeed a valid way of upgrading?
“First of all, let me tell you that this is not an issue when you do a command line upgrade to Oracle Database 12c with catctl.pl – you’ll only need to take care when using the DBUA.”
But you are right, I never blogged about “catctl.pl does not require datapatch to be run”.
In fact, catctl.pl (or the wrapper, dbupgrade) always executed datapatch as part of the upgrade.