In principle the move from 12.2. to 18.3 should be no more doom-laden than the
move from 12.1 to 12.2.
It's always being on the look-out for known threats that might apply to your
system, of course. So you might want to know about this one, which could be a
disaster if your code generators end up generating single-use prepared
statements that do "insert ... returning":
The problem doesn't exist in 19.2.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Patrice sur GMail <patrice.boivin@xxxxxxxxx>
Sent: 18 April 2019 19:14
Subject: going from 12.2 to 18c
Possibly foolish question, but at some point Oracle claimed the quarterly
patches were going to change the version numbers of database instances.
Did anyone run into problems upgrading from 12.2 to 18.3 or 18.4? Or is 18c
just 12c with a different versioning style (YY instead of version number
because they didn't want to use 13).
If 18 and 19 are just 12c with a different name, it's tempting to just move to
18c as it it was a patch.
(I know it would be like going from 12.1. to 12.2 etc.)