Oracle^® Solaris Cluster Data Service for Oracle Database Guide

Creating an Oracle Database

After verifying the Oracle Database installation, create the Oracle databases that you require.

• If you are using Oracle Database without standby databases, perform the procedure How to Create a Primary Oracle Database.

• If you are using Oracle Data Guard, create the following database instances:

  • Primary database instance. For instructions for creating a primary database, see How to Create a Primary Oracle Database.

  • Standby database instances. A standby database instance can be either a physical standby database instance or a logical standby database instance. For instructions for creating standby database instances, see your Oracle Database documentation.

  • Far sync database instances. For instructions for creating far sync database instances, see your Oracle Database documentation.

How to Create a Primary Oracle Database

1. Prepare database configuration files.

   Place all of the database-related files (data files, redo log files, and control files) on either shared raw global devices or on the cluster file system. See Preparing the Oracle Solaris Cluster Nodes and Disks for information about installation locations.

   ---

   Note -  If the database exists in the non-global zone, do not place the database-related files on the shared raw devices.

   ---

   Within the init$ORACLE_SID.ora or config$ORACLE_SID.ora file, you might need to modify the assignments for control_files and background_dump_dest to specify the locations of the control files and alert files.

   ---

   Note -  If you use Oracle Solaris authentication for database logins, set the remote_os_authent variable in the init$ORACLE_SID.ora file to True.

   ---

2. Start the creation of the database by using a supported Oracle Database creation utility.

   During creation, ensure that all the database-related files are placed in the appropriate location, either on shared global devices, on the cluster file system, or on a highly available local file system.

3. Verify that the file names of your control files match the file names in your configuration files.
4. Create the v$sysstat view.

   Run the catalog scripts that create the v$sysstat view. The HA for Oracle Database fault monitor uses this view. For more information, see your Oracle Database documentation.

Next Steps

When you have completed the work in this section, go to Setting Up Oracle Database Permissions.