2 Installation

This chapter describes the installation requirements and procedures for an Oracle9i Database Certified Configuration. This chapter contains the following topics:

Requirements
Single-Instance Installation
Real Application Clusters Installation
Image Creation

Requirements

This section describes the requirements for Oracle9i Database Certified Configuration. It contains the following topics:

Hardware Requirements
Partition Requirements
Software Requirements

Hardware Requirements

The following table lists the hardware requirements for Oracle9i Database Certified Configuration. The requirements are for both single-instance and Real Application Clusters, unless otherwise noted in the table.

Table 2-1 Oracle9i Database Certified Configuration Hardware Requirements

Component	Minimum Requirement	Additional Requirements for Real Application Clusters
Memory	2 GB RAM (Recommended: 1 GB per CPU)	None
Storage	Local: 2 disks each with 36 GB free space External: 36 GB SAN	Shared external storage required
Storage redundancy	RAID level 1 for local storage	None
Network - public	2 Ethernet NICs, each 10/100 Mbps	None
Network - private (Real Application Clusters node interconnect)	N/A	2 Ethernet NICs of 1 Gbps

Partition Requirements

The following table lists the minimum required partitions for Oracle9i Database Certified Configuration.

Table 2-2 Minimum Required Partitions

File Partition or Mount Point	Size	Comments
/	9 GB	Local.
/admin	4 GB	Local or NFS. Contains the certified configuration scripts.
/`DBNAME`/oracle	9 GB total with at least 5 GB free	Local or NFS. The `/``DBNAME``/oracle` directory is ORACLE_BASE.
/`DBNAME`/oradata	9 GB	Local or SAN which has to be shared storage for Real Application Clusters. The `/``DBNAME``/oradata` file systems contain the database files for the single-instance or Real Application Clusters. The `data01`, `data02` and `data03` directories should be created under the `/DBNAME/``oradata` file system. Optionally, the user can create 2 more file systems: `/DBNAME/``arch` for archive logs `/DBNAME/``backup` for backups
/oem	1 GB	Local or NFS. Location for Oracle Enterprise Manager (OEM) installation. It is separated from the `/` directory so that OEM can continue to work when the `/` directory is full.
swap	4 GB	Local. Two times RAM is recommended, with a maximum of 8 GB.

Software Requirements

The following table lists the software requirements for Oracle9i Database Certified Configuration. The requirements are for single-instance and Real Application Clusters, unless otherwise noted in the table.

Table 2-3 Oracle9i Database Certified Configuration Software Requirements

Component	Minimum Requirement	Additional Requirements for RAC
Operating system	Solaris8 v2.8 (02/2002 label)	None
Java	JRE/JDK automatically installed with Oracle	None
Clusterware	Not required	SunCluster 3.0 update 3 (05/2002)
Volume Manager	None	VxVM 3.1 or higher
Required OS patches	For Solaris 2.8, use 108528-16 or higher.	For Solaris 2.8, use 110648-20. For Solaris 2.9, use 112563-01.
`gzip` Package	Version 1.3 or higher	None

Operating System Configuration Requirements for Real Application Clusters

The rsh access for the root user on the private network must be enabled before starting a Real Application Clusters installation. In addition, the clocks for each node on the cluster must be synchronized with each other.

Single-Instance Installation

The Oracle9i Database Certified Configuration single-instance installation consists of three parts: installation of the certified configuration scripts, restoration of the image, and configuration of the database. The following procedure describes the installation:

Log in as the root user.
Run the dbcc_install_admin.sh script using the following command:
```
dbcc_install_admin.sh GOLDIMAGE
```
In the preceding command, GOLDIMAGE is the name of the downloaded file containing the gold image.

This script performs the following tasks:
- Creates the ordbcc user.
- Creates the dbdbcc group.
- Ensures the /admin directory exists.
- Restores the part of the gold image that contains the /admin/dbcc/dbcc_version directory. The certified configuration scripts are restored to the /admin/dbcc/3.1.0 directory, and are owned by the ordbcc user and the dbdbcc group.

Run the dbcc_image.sh script using the following command:

/admin/dbcc/3.1.0/install/dbcc_image.sh -restore -single  \
-imagefile GOLDIMAGE [-includedb] -dbname DBNAME

Note:

Oracle does not recommend using the -ignoreocheck option although you can use this option if you can ignore the errors from running the script. Use the -ignoreocheck option with caution.

In the preceding command, GOLDIMAGE is the name of the downloaded file containing the gold image, and DBNAME is the database name. The -includedb option restores the database files. When the script runs, it checks that the /DBNAME/oracle and /DBNAME/oradata directories exist, and have enough space. If the -includedb option is not used, then only the database binaries will be restored for the image.

The script performs the following tasks:

Creates the ordbname user.
Creates the dbdbname group.

Note:
For security reasons, the ordbname password has not been set. You must set it before proceeding to the next step.
Runs /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -preimage -single to perform all requirement checks. The output will be logged in the /var/tmp/ocheck.preimage.DBNAME.log file.
Restores the database image. The database will be restored under the /DBNAME/oracle directory according to the Oracle Outsourcing file layout standard.

When restoration is complete, run /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -single -postimage to check that the image was restored properly. The output will be logged in the /var/tmp/ocheck.postimage.DBNAME.log file.

Reconfigure the database using the reconfig.sh script, if the -includedb option was used in Step 3. The following procedure describes how to reconfigure the database:

Log in as the ordbname user.
Set the following variables:
- SRC_CC_DBNAME. Enter DGOLD.
- DST_CC_DBNAME. Enter the new database name or SID.
- SRC_CC_HOSTNAME. Enter localhost.us.oracle.com or the full source host name if you are cloning.
- DST_CC_HOSTNAME. Enter the new host name.
- SRC_CC_LISTENER_PORT. Enter 10650.
- DST_CC_LISTENER_PORT. Enter the desired listener port number.

Run the reconfig.sh script using the following command:

/admin/dbcc/3.1.0/ref_config/reconfig.sh -single [-silent]

Note:

The -silent option should be used with caution.

Oracle does not recommend using the -ignoreocheck option although you can use this option if you can ignore the errors from running the script. Use the -ignoreocheck option with caution.

The script performs the following tasks:

Runs /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -reconfig -single to perform all requirement checks. The output will be logged in the /var/tmp/ocheck.reconfg.DBNAME.log file.
Modifies the configuration files to reflect the correct host names and port numbers.
Regenerates the control files, if needed.
Runs /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -postconfig -single to check that the reconfiguration was successful. The output will be logged in the /var/tmp/ocheck.postconfig.DBNAME.log file.

This script actions are logged in the /admin/dbcc/3.1.0/ref_config/logs/reconfig.log file.

A .profile.oradb file, which sets up the Oracle environment, is created in the /dbname/oracle directory. Source the .profile.oradb file from the .profile file of the user to make use of the .profile.oradb file.

Real Application Clusters Installation

The following sections describe installation of Real Application Clusters for Oracle9i Database Certified Configuration.

Setting Up for Real Application Clusters Installation

Before installing, ensure that you meet all documented minimum hardware requirements. These requirements will be checked by the installation tool. Ensure that the following requirements are met before installation:

All required file systems exist and meet the minimum size requirements.
All standard Solaris components for Solaris 8 update 7 are installed on the system.
If the ordbname user has already been created, the home directory for this user is /dbname/oracle and the ordbname user is part of the dba and dbdbname groups.

If the dba and dbdbname groups do not exist, the installation tool will create them. The installation tool will also create the ordbname user home directory (/dbname/oracle).
SunCluster 3.0 update 3 is installed and configured on the two nodes. The following packages must be installed:
- SUNWcvm SUNWcvmr
- SUNWscucm SUNWudlm SUNWudlmr
VERITAS Cluster Volume Manager VxVM 3.1 or higher is installed.
The 64-bit version of the ORCLudlm package is installed. This package is also known as the "Parallel Server Patch."

You can download this package from the Oracle9i Release 2 shiphome located at:
```
/net/plnfs5/vol/build/FSL/project/solaris64/920/ship/ship_9201/Disk1/racpatch 
```
Licenses for SunCluster software and VERITAS Volume Manager (including CVM) is properly arranged.

Installing Real Application Clusters

Use the following steps to install Real Application Clusters:

Log in as the root user.
Enable rsh access for the user to all nodes using Interconnect.
Run the dbcc_install_admin.sh script using the following command:
```
dbcc_install_admin.sh GODLIMAGE
```
In the preceding command, GOLDIMAGE is the name of the downloaded file containing the gold image.

This script performs the following tasks:
- Creates the ordbcc user.
- Creates the dbdbcc group.
- Ensures the /admin directory exists.
- Restores the part of the gold image that contains the /admin/dbcc/dbcc_version directory. The certified configuration scripts are restored to the /admin/dbcc/3.1.0 directory, and will be owned by the ordbcc user and dbdbcc group.

Run the dbcc_image.sh script using the following command:

/admin/dbcc/3.1.0/install/dbcc_image.sh -restore -rac -imagefile GOLDIMAGE \
-dbname DBNAME

Note:

Oracle does not recommend using the -ignoreocheck option although you can use this option if you can ignore the errors from running the script. Use the -ignoreocheck option with caution.

The script performs the following tasks:

Runs /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -preimage -rac to check that the system configuration requirements are met. The output will be logged in the /var/tmp/ocheck.preimage.DBNAME.log file.
Restores the spfile file from the ORACLE_HOME/dbs directory to the /dbname/oradata/data01 directory.
Creates links to the spfile file on every node.
Runs /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -postimage -rac to check that the image restoration was successful. The output will be logged in the /var/tmp/ocheck.postimage.DBNAME.log file.
Creates the ordbname user.
Creates the dbdbname group.

The dbcc_image.sh script logs its actions in the /var/tmp/dbcc_image.restore.DBNAME.log file.

Setting Up for Real Application Clusters Configuration

Use the following steps to set up Real Application Clusters for configuration:

Set the password for the ordbname user and ensure that the .rhosts entries have been created for this user.
Configure two disk drives for the shared storage. These drives must been seen by all the nodes. They will be mirrored and populated by the seed database. The configuration tool prompts you to enter the disk devices that will contain the seed database. Oracle recommends using RAID-5 LUNS hardware. You must enter the two raw devices in the form of cXtXdX.

Note:
By default, the configuration tool will create the VERITAS volumes with layout="mirror,log". You can manually change this after configuration.

The seed database will be created with the minimum recommended sizes. If you want to change the table space sizes, run /admin/dbcc/3.1.0/ref_config/genocc.sh -rac -dbname DBNAME

Configuring Real Application Clusters

If the user wants a seed database restored on raw volumes, configure the database using the config.sh script. In this release, the config.sh script is only supported for Real Application Clusters. Use the following steps to configure Real Application Clusters:

Log in as the root user on the node that contains the Veritas volume manager master (the master node). To determine the location of the master node, run the following commands on the nodes:

vxdctl -c mode

This command will display cluster active - MASTER on the master node and cluster active - SLAVE on the other nodes.

Warning:

Before you continue, ensure that you are on the master node. The config.sh script must be run on one node with the master role only. Attempting to run the config.sh script simultaneously on more than one node will cause the configuration to fail.

Do not rerun the config.sh script after you have successfully configured Oracle9i Database Certified Configuration. Rerunning the config.sh script will cause destruction of all disk volumes and all database files allocated to the oracle_dg disk group.

Run the config.sh script with the following syntax:

/admin/dbcc/3.1.0.ref_config/config.sh -rac -raw -dbname DBNAME

Note:

Oracle does not recommend using the -ignoreocheck option although you can use this option if you can ignore the errors from running the script. Use the -ignoreocheck option with caution.

The config.sh script should be used when the database was restored without the -includedb option, and the user wants to create a seed database.

The /admin/dbcc/3.1.0/ref_config/log/conf_DBNAME.log file contains the log files for the config.sh script.

Image Creation

Use the dbcc_image.sh script to create an IMAGEFILE compressed archive file of the database specified by the DBNAME option.

To create a single-instance image, use the following command:

./dbcc_image.sh -create - single -dbname DBNAME [-includedb] \
-imagefile GOLDFILE

To create a Real Application Clusters image, use the following command:

./dbcc_image.sh -create -rac -dbname DBNAME [-includedb|includeconfig] \
 -imagefile GOLDFILE

Note:

Oracle recommends using the gold image instead of an image created by the user.

If the -includedb option is not used, then only the database binaries will be archived by the script. In that case, the -includeconfig option will add the following configuration files to the image:

$ORACLE_HOME/dbs/*SID* files such as the initdbname.ora, spfile, and passwd files
$ORACLE_HOME/network/admin/listener.ora
$ORACLE_HOME/network/admin/tnsnames.ora

The -includedb option is not supported if database files are in raw volumes. In addition, the option halts if the database is up.

The script logs its actions in the /var/tmp/dbcc_image.create.DBNAME.log file.