Updates to ASMLib Configuration File "/etc/sysconfig/oracleasm" Not Effective
(Doc ID 868352.1)
Last updated on JULY 12, 2019
Applies to:Linux OS - Version Oracle Linux 5.0 and later
Oracle Cloud Infrastructure - Version N/A and later
The configuration file /etc/sysconfig/oracleasm parameters "ORACLEASM_SCANORDER" and "ORACLEASM_SCANEXCLUDE" were updated, but after restarting the Oracleasm service the changes were not put into effect.
For example: multipath was configured and the "dm-" devices are presented.The "/etc/sysconfig/oracleasm" file was configured accordingly:
# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
Command "service oracleasm restart" was run, but still the single-path (/dev/sd*) devices are used by ASMLib, not the mulitpath (/dev/dm-*) devices, as evidenced by comparing outputs from commands "ls -l /dev/oracleasm/disks" and "cat /proc/partitions"
brw-rw---- 1 oracle dba 3, 65 May 14 12:08 DATA1
# cat /proc/partitions
3 65 4974448 sda
253 1 4974448 dm-1
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