SGA

MGA Issue – and it is fixed with Oracle 19.8.0 and newer

Posted on August 20, 2020 by ASM / RAC / GI Flaws and Pitfalls 6

Where do I start? One of the customer accounts I worked the longest time with recently upgraded to Oracle 19c on Exadata. They are an Exadata customer since 2009. After going live on 19c, a few days later they hit an MGA Issue – and it is fixed with Oracle 19.8.0 and newer. But question no.1 was: Why hasn’t Oracle warned us – and how could we have learned about it?

MGA Issue - and it is fixed with Oracle 19.8.0 and newer

Photo by Scott Webb on Unsplash

What is the MGA?

OK, I have heard of SGA and PGA. But MGA? The first two hits when I search with …

Continue reading...

Less is more – faster Oracle database upgrades with less memory

Posted on April 30, 2020 by Best Practice 9

The title of this post sounds a bit weird: Less is more – faster Oracle database upgrades with less memory. Just a few weeks ago, I posted about How long will my upgrade take … revisited. And Daniel adds a very useful piece to the upgrade speed topic. Read about his tests below.

Less is more – faster Oracle database upgrades with less memory

Photo by Franck V. on Unsplash

Less is more – faster Oracle database upgrades with less memory

by Daniel Overby Hansen, Senior Principal Product Manager,
Oracle Database Upgrades and Cloud Migrations
Less is more – faster Oracle database upgrades with less memory by Daniel Overby Hansen

Daniel Overby Hansen

Mike and I had a talk with a customer the other …

Continue reading...

Monitor SGA/PGA while Database Upgrade is running

Posted on July 6, 2015 by Upgrade / Migration 4

This blog is always a reminder to myself as well – just in case you wonder about that simple example and all steps here 😉

Currently I work with an important customer from Switzerland – and they upgrade their database landscape to Oracle Database 12.1.0.2. But in some rare cases we see the upgrade failing at different stages with dying PQ slaves or running out of memory. The reason may be that the customer is using only MEMORY_TARGET=1G – but actually our preupgrd.sql has nothing too complain about. And from reading the docs all seems to be fine as …

Continue reading...
Mike Dietrich
Oracle Senior Director of Product Manager for Database Upgrade, Migrations and Patching writing just another blog.

Opinions certainly are my own as is this page.

Archives

Categories

Upgrade @YouTube

Subscribe via Email

Join 7,849 other subscribers

Follow me on Twitter