How to Manually Configure multipathed fcp/scsi devices for use with Oracle ASM 11.2 on IBM: Linux on System z under SLES 11 SP 2 and later
(Doc ID 1584934.1)
Last updated on MARCH 12, 2021
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
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.
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
|1) How to configure multi-pathing for Oracle 11.2 ASM for fcp/scsi Devices with Linux on System z on SLES 11 SP2 (or later Service Pack Levels).|