Experiences with Oracle Database 10g on z/OS

22 Experiences Installing Oracle Database 10g on z/OS

2.7.2 The /oracle file system

The Oracle installer needs 2.5 GB of space in the UNIX file system to receive the

Oracle product. We chose to allocate a 2.5 GB file system and mount it as

/oracle. As well, we allocated a small file system for the Oracle userid to use as a

home directory when that userid uses z/OS UNIX System Services.

Allocating a file system

The JCL in Example 2-11 was used to allocate 2.5 GB of space for use in the

/oracle file system. It also allocates 10 MB of space for the use of the home

directory for the ORACLE1 userid. This JCL allocates the space; the space must

then be formatted and the file system mounted.

Example 2-11 Allocating file systems

//IBMUSER JOB (72,FB3),DESCRIPTION,COND=(0,NE),

// CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID

//S1 EXEC PGM=IDCAMS,REGION=0M

//SYSPRINT DD SYSOUT=*

DEFINE CLUSTER -

(NAME(ZFS.ORACLE) -

VOLUMES(ORA001) -

MEGABYTES(2500 500) -

LINEAR -

SHAREOPTIONS(2))

DEFINE CLUSTER -

(NAME(ZFS.U.ORACLE1) -

VOLUMES(ORA001) -

MEGABYTES(10 5) -

LINEAR -

SHAREOPTIONS(2))

Formatting a file system

We used the JCL in Example 2-12 to format the two file systems.

Example 2-12 Formatting file systems

//IBMUSER JOB (72,FB3),DESCRIPTION,COND=(0,NE),

// CLASS=A,MSGCLASS=H,NOTIFY=&SYSUID

//S1 EXEC PGM=IOEAGFMT,REGION=0M,

// PARM='-aggregate ZFS.ORACLE -compat'

//SYSPRINT DD SYSOUT=*

//STDOUT DD SYSOUT=*

//STDERR DD SYSOUT=*

//CEEDUMP DD SYSOUT=*

Chapter 2. Preparing to install Oracle Database 10g 23

//S2 EXEC PGM=IOEAGFMT,REGION=0M,

// PARM='-aggregate ZFS.U.ORACLE1 -compat'

//SYSPRINT DD SYSOUT=*

//STDOUT DD SYSOUT=*

//STDERR DD SYSOUT=*

//CEEDUMP DD SYSOUT=*

//

Mounting file systems

To mount these file systems, the mount command could be used. An example of

this is shown in Example 2-13.

Example 2-13 Mounting file systems with the mount command

IBMUSER:/u/ibmuser: >mount -f ZFS.ORACLE -t ZFS /oracle

IBMUSER:/u/ibmuser: >

IBMUSER:/u/ibmuser: >mount -f ZFS.U.ORACLE1 -t ZFS /u/oracle1

IBMUSER:/u/ibmuser: >

In our system we used these commands only for testing. To make these changes

active every time your system is IPLed, we recommend that you change the USS

startup member in the z/OS parameter library (PARMLIB). In our system the

PARMLIB member BPXPRMCS was used to initialize USS. We inserted the

lines in Example 2-14 into BPXPRMCS to cause the file systems to be mounted

at IPL.

Example 2-14 BPXPRMCS PARMLIB member changes

FILESYSTYPE TYPE(ZFS) ENTRYPOINT(IOEFSCM) ASNAME(ZFS)

MOUNT FILESYSTEM('ZFS.ORACLE')

TYPE(ZFS)

MODE(RDWR)

MOUNTPOINT('/oracle')

MOUNT FILESYSTEM('ZFS.U.ORACLE1')

TYPE(ZFS)

MODE(RDWR)

MOUNTPOINT('/u/oracle1')

Once these file systems are mounted, you should be able to log on to the userid

ORACLE1. On our system we got a permission failure, saying that the user

ORACLE1did not have permission to access /u/oracle1as a home directory. We

discovered that on our system the /u directory did not have the “x” permission bit