In this article, I will provide a detailed guide on how to resolve ASM compatibility issue. We’ll walk you through each step of the process with proper screenshots.
Table of Contents
1.Open MobaXterm and log in to your server as a grid user. If you have not installed MobaXterm on your host machine yet, then follow my other article to download MobaXterm and set it up. Once logged in go to the bin folder location under grid home and run asmca command:
[grid@node1 ~]$ ps -ef|grep pmon grid 860 576 0 13:07 pts/1 00:00:00 grep --color=auto pmon grid 7637 1 0 11:52 ? 00:00:00 asm_pmon_+ASM1 [grid@node1 ~]$ . oraenv ORACLE_SID = [grid] ? +ASM1 ORACLE_HOME = [/home/oracle] ? /u01/app/19.3.0/grid The Oracle base has been set to /u01/app/grid [grid@node1 ~]$ cd $ORACLE_HOME/bin [grid@node1 bin]$ ls -ld *asmca -rwxr-x--- 1 root oinstall 7910 Mar 11 03:35 asmca [grid@node1 bin]$ file asmca asmca: POSIX shell script, ASCII text executable, with very long lines [grid@node1 bin]$ asmca
2. Select ASM and click on Disk Groups:
3. Check if all the disk groups are mounted. Here the DATADISKDG is mounted on one node. To mount it on both nodes select the DATADISKDG and click on Mount All.
4. To change the attributes you need to select the disk group and right-click on it. Now click on Edit Attributes and change the ASM & database compatibility value to 19.0.0.0.0
5. Let’s do the same for the OCRVDDG disk group.
Hope this article helped you to resolve ASM compatibility issue in oracle.
