ORA-15221: ASM operation requires compatible.asm of string or higher

While trying to create an SPFILE for ASM instance on a diskgroup, oracle threw ORA-15221: ASM operation requires compatible.asm of 11.2.0.0.0 or higher.

COMPATIBLE.ASM is an attribute associated with every diskgroup. This attribute describes the minimum software version required for the ASM instance that can access the
diskgroup.
Here, the ASM instance version that was used was 11.2.0.1.0 and the error threw that the compatible parameter must be set to a minimum of 11.2.0.0.0

[oracle@10gnode1 bin]$ ./sqlplus / as sysasm

SQL*Plus: Release 11.2.0.1.0 Production on Fri Dec 27 11:54:13 2013

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

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Real Application Clusters and Automatic Storage Management options

SQL> create spfile='+DATA/ASM/spfileASM.ora' from pfile;
create spfile='+DATA/ASM/spfileASM.ora' from pfile
*
ERROR at line 1:
ORA-17502: ksfdcre:4 Failed to create file +DATA/ASM/spfileASM.ora
ORA-15221: ASM operation requires compatible.asm of 11.2.0.0.0 or higher

SQL> select group_number, name,compatibility, database_compatibility from v$asm_diskgroup;

GROUP_NUMBER NAME  COMPATIBILITY DATABASE_COMPATIBILITY
------------ ----- ------------- -------------------------
 1           DATA  10.1.0.0.0    10.1.0.0.0
 2           FRA   10.1.0.0.0    10.1.0.0.0

Here you can see that the compatibility was set to 10.1.0.0 and which is why ASM instance was unable to access the diskgroup.
After changing the COMPATIBILITY to 11.2.0.0.0, the issue resolved.

SQL> alter diskgroup DATA set attribute 'compatible.asm'='11.2.0.0.0';

Diskgroup altered.

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

Diskgroup altered.

SQL> select group_number, name,compatibility, database_compatibility from v$asm_diskgroup;

GROUP_NUMBER NAME COMPATIBILITY DATABASE_COMPATIBILITY
------------ ---- ------------  --------------------------------
 1           DATA 11.2.0.0.0    10.1.0.0.0
 2           FRA  11.2.0.0.0    10.1.0.0.0

There is also another attribute called “compatible.rdbms” which determines the minimum COMPATIBLE database initialization parameter setting for the database instance
to access the diskgroup. Here, in my case, the attribute was set to 10.1.0.0.0 but the Dataabse instance compatiblity that had to access the diskgroup was 11.2.0.1.0

SQL> alter diskgroup DATA set attribute 'compatible.rdbms'='11.2.0.0.0';

Diskgroup altered.

SQL> alter diskgroup FRA set attribute 'compatible.rdbms'='11.2.0.0.0';
Diskgroup altered.

SQL> select group_number, name,compatibility, database_compatibility from v$asm_diskgroup;

GROUP_NUMBER NAME COMPATIBILITY DATABASE_COMPATIBILITY
------------ ---- ------------- -------------------------
 1           DATA 11.2.0.0.0    11.2.0.0.0
 2           FRA  11.2.0.0.0    11.2.0.0.0

After setting the “compatible.asm” attribute to 11.2.0.0.0, ASM instance was able to access the diskgroup and was able to create the spfile on the diskgroup.

[oracle@10gnode1 bin]$ ./sqlplus / as sysasm

SQL*Plus: Release 11.2.0.1.0 Production on Fri Dec 27 12:05:07 2013

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

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Real Application Clusters and Automatic Storage Management options

SQL> create spfile='+DATA/ASM/spfileASM.ora' from pfile;

File created.

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 -
Production
With the Real Application Clusters and Automatic Storage Management options

[oracle@10gnode1 bin]$ ./asmcmd
ASMCMD> cd DATA/ASM
ASMCMD> ls
spfileASM.ora

Here we go !!

COPYRIGHT

© Shivananda Rao P, 2012 to 2018. Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Shivananda Rao and http://www.shivanandarao-oracle.com with appropriate and specific direction to the original content.

DISCLAIMER

The views expressed here are my own and do not necessarily reflect the views of any other individual, business entity, or organization. The views expressed by visitors on this blog are theirs solely and may not reflect mine.