My Oracle Support Banner

New 11.2 Grid Infrastructure Installation (root.sh) Is Removing Candidate mknod devices Or Symbolic Link Devices Created At /dev/asm Directory. (Doc ID 1366159.1)

Last updated on JULY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 18-Jul-2013***

Symptoms


i) Sometimes, in order to define and associated meaningful device names to Candidate or Member physical ASM Disks on Linux/Unix, mknod devices <Document 1313687.1> or symbolic links are used to reference the real raw devices, this practice is completely valid and supported.

ii) But on ASM 11.2 release, there is a specific issue, when you place/create mknod devices or symbolic links at the "/dev/asm" directory, as the following example:



1) The /dev/asm/ASMDISK directory is created on each RAC node.

2) Then several mknod devices were created at the "/dev/asm/ASMDISK" directory referencing the real raw devices (e.g. /dev/rdsk Solaris):



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.