< Previous  | TOC | Index | Next  >

Creating starter database tablespaces on CFS using dbca (option 2)

When creating a starter database on a cluster file system, create a disk group and volume for the tablespaces before running the dbca utility.

1. Create a disk group (for example, oradatadg):

   # vxdg -s init oradatadg HDS0_20

2. Create a single shared volume (for example, rac_vol1) large enough to contain a file system for all the tablespaces. The tablespaces require about 6.8 GB:

   # vxassist -g oradatadg make rac_vol1 6600M

3. Start the volume in the disk group:

   # vxvol -g oradatadg startall

4. Create a VxFS file system in this volume. From one node, type:

   # mkfs -V vxfs /dev/vx/rdsk/oradatadg/oradatavol

5. Create a mount point for the shared file system:

   # mkdir /oradata

6. From the same node, mount the file system:

   # mount -V vxfs -o cluster /dev/vx/dsk/oradatadg/oradatavol \ /oradata

7. Set "oracle" as the owner of the file system and "775" as the permissions:

   # chown oracle:dba /oradata

   # chmod 755 /oradata

8. On the other node(s), complete step 5 through step 7.

Running the dbca Utility for Cluster File System

As oracle user, use the dbca utility on the master node to create a general purpose database on a cluster file system. This utility is a graphical user interface and requires setting the DISPLAY environment variable.

1. Make sure an oracle account is created on all nodes.
2. Verify that rsh works among all the nodes under the oracle account.
3. Examine the /var/opt/oracle/srvConfig.loc configuration file and note the path defined for the srvconfig_loc variable. For example:

   srvconfig_loc=/db/srvm.ora

   where /db/srvm.ora is the path to the SRVM configuration file.

   1. Use the ls -l pathname command to display the long listing for the defined path. The file is initialized if the output shows a file size greater than zero bytes.
   2. If the variable is not initialized (size is 0), type:

      $ srvconfig -init

   3. If the path is not yet defined (listing does not appear), initialize the variable after using the touch command to create it:

      $ touch /db/srvm.ora

      $ srvconfig -init

4. Start the Oracle Real Application Clusters Manageability daemon on each node:

   $ gsdctl start

5. From one node, log in as oracle user.
6. For Oracle9i, create and start the Oracle listener using NETCA utility (refer to the Oracle9i Installation Guide):

   $ netca

7. Run the dbca utility. When starting the utility with a cluster file system, use the -datafileDestination option to specify the mount point. For example:

   $ dbca -datafileDestination /oradata

Refer to the Oracle documentation for details on the dbca utility.