Re: 19C migration

May not be the exact answer to your question. But as in your case it would be a version upgrade without any hardware upgrade, so you may get beaten severely by the plan changes. So as I had got the recommendation from many here in this forum , you should better turn on the baselining of all the existing plans (considering your ~150TB database may not have an exact test replica available to you) and appropriately capture/store those. That will help you atleast to get back to the original path just as a quick bandaid without impacting your customers much. And we have very bad experience with version 19.9 so hopefully you are going for the latest i.e 19.12. I am not sure if there are any features which we must use in 19C, others can comment on this, but do you say wrt application code you want to utilize new good features and if required, you are ready to plan to change your application code for that?

On Fri, Dec 3, 2021 at 2:46 PM Pap <oracle.developer35_at_gmail.com> wrote:

> Hello Listers, We have one of the big hybrid (catering to Oltp+reporting
> type of workload) databases(~150TB in size) which is planned to move from
> 11.2 to 19C. it's already on an X8-M high capacity exadata box.
>
> I understand with most of the databases now on 19C+ versions and with many
> new features with this version as compared to 11.2.0.4, is there any key
> learning we should follow or say are there any specific features we must
> use or let our application code change to use to get best out of 19C in
> this upgrade? May be related to optimization, compression etc.
>

--
http://www.freelists.org/webpage/oracle-l