ORA-15032 ORA-59303 ORA-15221: ASM operation requires compatible.asm of 11.1.0.0.0 or higher

For upgrading 12.1.0.2 GI to 12.2.0.1 GI, after running rootupgrade.sh, there are some disk groups are not mounted.

NAME                  STATE       COMPATIBILITY      V
-------------------- ----------- ------------------- -
GIMR                  DISMOUNTED  0.0.0.0.0          N
FRA                   DISMOUNTED  0.0.0.0.0          N
DATA                  MOUNTED     12.1.0.0.0         N
OCR_VOTE              MOUNTED     11.2.0.4.0         Y
SQL> alter diskgroup FRA mount;
alter diskgroup FRA mount
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-59303: The attribute compatible.asm (10.1.0.0.0) of the 
           diskgroup being mounted should be 11.2.0.2.0 or higher.
ORA-15221: ASM operation requires compatible.asm of 11.1.0.0.0 
           or higher
SQL> alter diskgroup FRA mount restricted;

Diskgroup altered.

SQL> alter diskgroup FRA set attribute 'compatible.asm'='11.2.0.4';

Diskgroup altered.

SQL> alter diskgroup FRA dismount;

Diskgroup altered.

SQL> alter diskgroup GIMR mount restricted;

Diskgroup altered.

SQL> alter diskgroup GIMR set attribute 'compatible.asm'='11.2.0.4';

Diskgroup altered.

SQL> alter diskgroup GIMR dismount;

Diskgroup altered.

SQL> alter diskgroup FRA mount;

Diskgroup altered.

SQL> alter diskgroup GIMR mount;

Diskgroup altered.



SQL>   select NAME, STATE, COMPATIBILITY  from  v$asm_diskgroup;

NAME                           STATE       COMPATIBILITY
------------------------------ ----------- -------------------
DATA                           MOUNTED     12.1.0.0.0
FRA                            MOUNTED     11.2.0.4.0
OCR_VOTE                       MOUNTED     11.2.0.4.0
GIMR                           MOUNTED     11.2.0.4.0

Upgrading to 12.2.0.1 Reports Missing Patch 21255373 Even Though It has been Applied

While upgrading Grid Infrastructure (GI) from 12.1.0.2 to 12.2.0.1, gridSetup.sh reports missing pre-requisite patch 21255373 even though patch is already available

$ /u01/app/12.1.0/grid/OPatch/opatch lsinventory|grep 21255373
22393909, 21255373, 25164540, 18868829, 20408163, 20579351, 20350915

It is a bug. the workaround is to use ‘gridSetup.sh -skipPrereqs’ after verifying all other pre-requisites successfully.

$ /u01/app/12.2.0.1/grid/gridSetup.sh -skipPrereqs

ORA-01102: cannot mount database in EXCLUSIVE mode

One of the RAC instance is up, but the rest RAC instances failed to start up.

$sqlplus / as sysdba
SQL> startup;
ERROR at line 1:
ORA-01102: cannot mount database in EXCLUSIVE mode
.....
..
.
2025-02-18T13:46:48.148505+11:00
Error: Shutdown in progress. Error: 1102.
USER (ospid: 90061): terminating the instance due to ORA error 1102
2025-02-18T13:46:49.188764+11:00
Instance terminated by USER, pid = 90061

Subscribe to get access

Read more of this content when you subscribe today.

ORA-00449: background process ‘RBAL’ unexpectedly terminated with error 448

When startup a RAC database or its instances, and get “ORA-00449: background process ‘RBAL’ unexpectedly terminated with error 448”.

Checked all cluster resources are ONLINE.

SQL> startup 
ORA-00449: background process 'RBAL' unexpectedly terminated with error 448
SQL>

Subscribe to get access

Read more of this content when you subscribe today.

ORA-12547: TNS:lost contact

[oracle@racnode1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Mon Jan 13 16:31:25 2020

Copyright (c) 1982, 2014, Oracle. All rights reserved.

ERROR:
ORA-12547: TNS:lost contact


Enter user-name:
ERROR:
ORA-12547: TNS:lost contact

Subscribe to get access

Read more of this content when you subscribe today.