RE: Things to consider during upgrade/migration

From: Clay Jackson <"Clay>
Date: Sat, 13 Nov 2021 21:36:26 +0000
Message-ID: <CO1PR19MB49841DF2D90CC41F9D917DEE9B969_at_CO1PR19MB4984.namprd19.prod.outlook.com>



What Mladen and Andy said – I would pay very serious attention to their wisdom; born of many years 😊. ESPECIALLY the parts about

  1. How different 19 is from 11 and the Exadata is from the HP
  2. Collecting baselines for ALL SQL – the time you spend up from will save more than that troubleshooting on the “back end”
  3. TEST EVERYTHING
In my position, I talk to customers/prospects going through similar upgrades/migrations and those who follow(ed) Steps 2 and 3 (and understood the differences) had SIGNIFICANTLY better success than those who tried to “shortcut” the process.

Clay Jackson

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Lok P Sent: Saturday, November 13, 2021 10:47 AM To: Oracle L <oracle-l_at_freelists.org> Subject: Things to consider during upgrade/migration

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Hello Listers, With respect to having a safe upgrade(say from 11.2 to 19C) or migration(From HP to Exadata) experience with minimal performance issues. Is there any guideline we should follow like setting up exadata system stats in case the target database is going to be exadata, Or verifying dictionary stats/table stats etc in a certain way. Want to know experts' views, if there are any such guidelines?

Regards

Lok

--
http://www.freelists.org/webpage/oracle-l
Received on Sat Nov 13 2021 - 22:36:26 CET

Original text of this message