Updates to ASMLib Configuration File "/etc/sysconfig/oracleasm" Not Effective (Doc ID 868352.1)

Last updated on MARCH 01, 2017

Applies to:

Linux OS - Version 2.0.4-1 and later
Linux x86
Linux x86-64
Linux Kernel - Version: 2.0.4-1


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_SCANORDER: Matching patterns to order disk scanning

# 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"

For example

# ls -l /dev/oracleasm/disks
brw-rw---- 1 oracle dba 3, 65 May 14 12:08 DATA1

# cat /proc/partitions
  3 65 4974448 sda
253  1 4974448 dm-1



Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms