Managing Serviceguard Extension for SAP, December 2007

SAP Master Data Management (MDM)
Installation and Configuration Considerations
Chapter 5244
The MDM SGeSAP File System Layout
The following file system layout will be used for the MDM Server
components.
/oracle/MDM
For performance reasons, the MDM database (MDB) file systems will be
based on local and relocatable storage (the physical storage volume / file
system can relocate between the cluster nodes, but only ONE node in
the cluster will mount the file system). The file system will be mounted
by the cluster node on which the database instance is started/running.
The directory mount point is /oracle/MDM. All I/O is local to the cluster
node.
/home/mdmuser
/export/home/mdmuser
These are the file systems for the MDM server components (These are
MDS, MDSS and MDIS) that are of dynamic in nature – e.g.
configuration files, log files, import files, export files). These file systems
will be based on NFS. One cluster node mounts the physical storage
volume and runs as a NFS server, exporting the file systems to NFS
clients. Mount point for the NFS server file system is
/export/home/mdmuser.
All nodes in the cluster mount the NFS exported files systems as NFS
clients. Mount point for the NFS client file system is /home/mdmuser.
Each of the MDM server (mds, mdss and mdis) components will use it’s
own directory (e.g.: /home/mdmuser/mds, /home/mdmuser/mdss,
/home/mdmuser/mdis) within /home/mdmuser.
Should the NFS server node fail – then the storage volume will be
relocated to another cluster node, which then will take over the NFS
server part.