3.5.1 Matrix Server Administration Guide

Chapter 7: Configure PSFS Filesystems 128

1. Create a subdirectory in /oracle for each machine type and then create

a bin and sbin directory in the new machine-type directories. You now

have the following directories in the /oracle PSFS filesystem:

/oracle/<machine-type1>/bin

/oracle/<machine-type1>/sbin

/oracle/<machine-type2>/bin

/oracle/<machine-type2>/sbin

2. Copy the appropriate binaries to the new bin and sbin directories.

3. Create CDSLs for /oracle/bin and /oracle/sbin:

ln -s {MACH}/bin /oracle/bin

ln -s {MACH}/sbin /oracle/sbin

The ls -l output looks like this on each server:

ls -l /oracle/*bin

lrwxrwxrwx 1 root root 10 Jun 16 16:40 /oracle/bin -> {MACH}/bin

lrwxrwxrwx 1 root root 11 Jun 16 16:40 /oracle/sbin -> {MACH}/sbin

When you log in on serv1, the /oracle/bin and /oracle/sbin symbolic links

resolve to /oracle/<machine-type1>/bin and /oracle/<machine-type1>/sbin. On

serv2, the links resolve to /oracle/<machine-type2>/bin and /oracle/<machine-

type2>/sbin.

Locate a Target That Is Not on a PSFS Filesystem

In the earlier examples, both the symbolic links and the targets were on

PSFS filesystems. However, only the symbolic link must be on a PSFS

filesystem. The target can be located on a non-PSFS filesystem.

This example uses a CDSL to link the /oracle/etc directory on the PSFS

filesystem to a non-PSFS directory on serv1 or serv2.

1. On each server, create a target directory in /etc that has the same name

as the server’s hostname:

mkdir /etc/serv1.xvz.com

mkdir /etc/serv2.xvz.com

2. Populate the new directories with the appropriate files.

3. Create the CDSL:

ln -s /etc/{HOSTNAME} /oracle/etc