My Oracle Support Banner

[PCA 2.x] MySQL Sanity Check WhenUpgrade PCA 2.2.x to 2.3.x Failed (Doc ID 2604491.1)

Last updated on AUGUST 26, 2022

Applies to:

Private Cloud Appliance - Version 2.1.1 to 2.2.2 [Release 2.0]
Linux x86-64

Goal

The MySQL database structure in PCA 2.3.x has been changed significantly from PCA 2.2.x, when upgrading from PCA software, there will be complicated operations of data exporting, importing, database/table recreating, objects importing, any failure will result in upgrade failure like:

"FATAL ERROR: Failure during database upgrade"

A typical scenario that MySQL database might be "polluted" after a failed/half-baked upgrading, or restored from a corrupted/invalid backup.

Even rebuild MySQL database (per km 2224820.1) may not eliminate some incorrect data such as mixing of OVM 3.4.x table/database.

This KM will show some practices on how to do a sanity check before kick-off another upgrading.

Prerequisite

Make sure the "data" and "dbbackup" under /u01/app/oracle/ovm-manager-3/mysql/data/mysql/ are symbolic links pointing to /nfs/shared_storage/ovmm_mysql/

You may need restore a valid MySQL database from /nfs/shared_storage/backups/, then chown to "oracle:dba".

Once the symbolic links are created, the statement of /u01/app/oracle/mysql/ is same as /nfs/shared_storage/ovmm_mysql/ in this KM. 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.