1. Database Upgrade Guide
  2. Postupgrade Tasks for Oracle Database
  3. Recommended Tasks After Upgrading Oracle ASM

Recommended Tasks After Upgrading Oracle ASM

After you have upgraded Oracle ASM, Oracle recommends that you perform tasks such as resetting the Oracle ASM passwords and configuring disk groups.

Parent topic: Postupgrade Tasks for Oracle Database

Advancing the Oracle ASM and Oracle Database Disk Group Compatibility

You can advance the Oracle Database and the Oracle ASM disk group compatibility settings across software versions.

Caution:

If you advance the COMPATIBLE.RDBMS attribute, then you cannot revert to the previous setting. Before advancing the COMPATIBLE.RDBMS attribute, ensure that the values for the COMPATIBLE initialization parameter for all of the databases that use the disk group are set to at least the new setting for COMPATIBLE.RDBMS before you advance the attribute value.

Advancing compatibility enables new features only available in the new release. However, doing so makes the disk group incompatible with older releases of the software. Advancing the on disk compatibility is an irreversible operation.

Use the compatible.rdbms and compatible.asm attributes to specify the minimum software release required by the database instance and the Oracle ASM instance, respectively, to access the disk group. For example, the following ALTER DISKGROUP statement advances the Oracle ASM compatibility of the disk group asmdg2: 

ALTER DISKGROUP asmdg2 SET ATTRIBUTE 'compatible.asm' = '19.0.0.0.0'

In this case, the disk group can be managed only by Oracle ASM software of release 19c or later. The version of the databases that can use the disk group is controlled by compatible.rdbms. Before advancing compatible.rdbms, ensure that all databases using the disk group have their compatible.rdbms value set at least to the same value as compatible.asm, or to a higher value.

Note:

To prevent writing data formats or structures to disk that are not compatible with earlier releases, so that downgrades are possible, features that require a higher value of compatible.asm to work correctly may be restricted or disabled, even when you set compatible.rdbms to a higher value.

Parent topic: Recommended Tasks After Upgrading Oracle ASM