Infrastructure at your Service

Oracle Team

Oracle Grid Infrastructure: fixing the PRVG-10122 error during installation

Making errors is human and when you configure a new Oracle Grid Infrastructure environment (especially one with a large number of nodes), mistakes can happen when configuring ASMLIB on all nodes. If you get an error looking like”PRVG-10122 : ASMLib configuration…does not match with cluster nodes”, there is a simple solution to fix it.

When you are installing Grid Infrastructure, the following error can occor in cluvfy output or directly in the pre-requisites check step of the OUI:

 

ERROR:
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_UID” on the node “srvora01” does not match with cluster nodes
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_GID” on the node “srvora01” does not match with cluster nodes
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_ENABLED” on the node “srvora01” does not match with cluster nodes
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_UID” on the node “srvora02” does not match with cluster nodes
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_GID” on the node “srvora02” does not match with cluster nodes
PRVG-10122 : ASMLib configuration value set to configuration parameter “ORACLEASM_ENABLED” on the node “srvora02” does not match with cluster nodes
Result: Check for ASMLib configuration failed.

 

The three parameters ORACLEASM_UID, ORACLEASM_GID and ORACLEASM_ENABLED displayed in the error should be defined when configuring ASMLIB on the system (see Grid Infrastructure 12c pre-requisites for installation, configure ASM step). To check if the configuration is coherent between the nodes specified in the error above, run the following command as root on all concerned nodes. In my case, srvora01 and srvora02 are the involved servers:

 

On srvora01

[[email protected] ~]# oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=grid
ORACLEASM_GID=asmadmin
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=””
ORACLEASM_SCANEXCLUDE=””
ORACLEASM_USE_LOGICAL_BLOCK_SIZE=”false”

 

On srvora02

[[email protected] ~]# oracleasm configure
ORACLEASM_ENABLED=false
ORACLEASM_UID=..
ORACLEASM_GID=..
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=””
ORACLEASM_SCANEXCLUDE=””
ORACLEASM_USE_LOGICAL_BLOCK_SIZE=”false”

 

As we can see, it seems that ASMLIB has not been configured on srvora02: ORACLEASM_ENABLED is false, and no UID or GID are provided. Thse are the default values! The parameters are different between the two nodes.

To solve the issue, simply reconfigure ASMLIB on the second node by running the following command with the right parameters:

On srvora02

[[email protected] ~]# oracleasm configure -i

 

Configuring the Oracle ASM library driver.This will configure the on-boot properties of the Oracle ASM library
driver.  The following questions will determine whether the driver is
loaded on boot and what permissions it will have.  The current values
will be shown in brackets (‘[]’).  Hitting without typing an
answer will keep that current value.  Ctrl-C will abort.

 

Default user to own the driver interface []: grid
Default group to own the driver interface []: asmadmin
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done

 

Now, the parameters are the same between the two nodes:

 

[[email protected] ~]# oracleasm configure
ORACLEASM_ENABLED=true
ORACLEASM_UID=grid
ORACLEASM_GID=asmadmin
ORACLEASM_SCANBOOT=true
ORACLEASM_SCANORDER=””
ORACLEASM_SCANEXCLUDE=””
ORACLEASM_USE_LOGICAL_BLOCK_SIZE=”false”

 

The Grid Infrastructure installation can now continue. I know that the error message was quite explicit, but after having spent hours to configure all nodes of my cluster, it took me some time to understand my big mistake. I hope this will help you.

2 Comments

  • Michael says:

    I had this error happen to me, but my cause was something else. Note that a system admin set up the storage and installed oracleasm for me (and had to do a package update) so I don’t know the exact history of how this happened – but one of my nodes had a literal /etc/sysconfig/oracleasm file, while the others had /etc/sysconfig/oracleasm as a symlink to /etc/sysconfig/oracleasm-_dev_oracleasm
    So, all of them were configured properly, but on one the contents of /etc/sysconfig/oracleasm never got updated properly so the Installer’s validation failed. As root, I deleted “oracleasm” and created a symlink in its place, and all was well.

  • Burak says:

    I got the following similar error during installation grid 12.2 on Linux 7. unfortunately, it is an oracle bug. Oracle Doc ID 2262130.1

    PRVG-0802 : Storage type for path “/dev/oracleasm/disks/disk04” could not be determined on node “node02”.
    PRVG-0801 : invalid internal command tags  
    – Cause:  An error occurred while attempting to determine the storage type of the indicated path. Accompanying messages provide further details.
     – Action:  Resolve the issues described in any accompanying messages and retry.

    CAUSE

    Bug 25784424 – PRVG-0802 : STORAGE TYPE FOR PATH “” COULD NOT BE DETERMINED ON NODE

    SOLUTION

    Apply/Request the patch for Bug 25784424 and this fix will be included 12.2.0.2

    A strange solution :S

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Oracle Team
Oracle Team