Re: going from 12.2 to 18c

From: Shane Borden <sborden76_at_gmail.com>
Date: Thu, 18 Apr 2019 14:36:44 -0400
Message-Id: <17511A94-E759-46B2-97D9-53C393FB20FB_at_gmail.com>



You also don’t get a ton of time benefit of RU support with 18. If you are already 12.2, if time allows, I’d wait for 19.

Shane Borden
sborden76_at_gmail.com
Sent from my iPhone

> On Apr 18, 2019, at 2:33 PM, Andy Sayer <andysayer_at_gmail.com> wrote:
> 
> If you are using Goldengate, you must also upgrade that to 18, earlier versions will not work. Not sure if that’s mentioned in the video.
> 
> Thanks,
> Andy
> 
>> On Thu, 18 Apr 2019 at 19:27, Andy Wattenhofer <watt0012_at_umn.edu> wrote:
>> 18.1 is said to be the same release as what would have been called 12.2.0.2. It is just that they switched the naming convention in there.
>> All of your questions are answered in this reference from Mike Dietrich on the topic: https://youtu.be/pmyxUzs6TVM
>> 

>>> On Thu, Apr 18, 2019 at 1:16 PM Patrice sur GMail <patrice.boivin_at_gmail.com> wrote:
>>> 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.)
>>>
>>> -- Patrice
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 18 2019 - 20:36:44 CEST

Original text of this message