My Oracle Support Banner

How to Manually Configure Disk Storage devices for use with Oracle ASM 11.2 and 12.1 on IBM: Linux on System z under SLES (Doc ID 1350008.1)

Last updated on FEBRUARY 13, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
IBM: Linux on System z
***Checked for relevance on 28-May-2013***

Goal

This article is applicable to SLES 11 SP4 and SLES 12 SP1 (and later). The configuration has changed between SLES11 and SLES12 to set up alias names and permissions for fcp/scsi multipath devices.

Even though ASMLib can be obtained from SUSE via the orarun rpm package, you will encounter issues creating ASM diskgroups with 512 byte FCP/SCSI storage devices and ASMLib with Linux on System z

ASMLib is not recommended for Oracle 11gR2 and above with fcp/scsi devices due to a 512 byte compatibility Bug:12346221 on Linux for System z. UDEV rules are recommended per this note.

This article provides platform specific examples for manually configuring multi-path scsi/fcp/LUNS via udev rules and multipathing which provides the same functionality, flexibility and device persistence as ASMLib.

NOTE: If using an Oracle single instance database without ASM, with SLES 11 SP4 or later operating system then a xfs filesystem is the recommended file system type for database datafiles.



Solution

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
Goal
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.