2 Installation

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

Requirements
Single Instance Installation
Real Application Clusters Installation
Image Creation

2.1 Requirements

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

Hardware Requirements
Partition Requirements
Software Requirements

2.1.1 Hardware Requirements

Table 2-1 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
Memory	2 GB, 1GB per CPU recommended
Private network for Real Application Clusters node Interconnect only	1 Ethernet network interface cards (NIC), 1 Gbps
Processor	2 Intel CPUs, each 700 MHz
Processor power	1400 (2 x minimum required CPU clock speed)
Public network	2 Ethernet NICs, each 10/100 Mbps
Storage	Local for system: 2 mirrored local disks, each with 36 GB free Real Application Clusters: NAS or SAN shared storage
Storage redundancy	RAID Level 1 (mirrored) for local storage
Swap space	4 GB of disk space on swap partition

2.1.2 Partition Requirements

Table 2-2 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.
/boot	115 MB	Local.
/`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, NAS 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, if the datafiles reside on a NAS. 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.
/oracm/oracle	9 GB	Local, NAS or SAN. Contains the cluster manager instance, `oracm`.
/oracm/oradata	512 MB	NAS or SAN. Has to be on shared storage. Contains cluster manager configuration files. This directory is needed when cluster manager is configured on NAS or SAN.
swap	4 GB	Local. Two times RAM is recommended, with a maximum of 8 GB.

2.1.3 Software Requirements

Table 2-3 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
C compiler	Gnu gcc 2.96-108.1
Clusterware, Real Application Clusters only	Included with the database
Java	Automatically installed with the database
Operating system	Red Hat Linux Advanced Server 2.1
Operating system packages	`ksh` and `bc` Linux packages
Operating system patches	None
Perl, TCL	Automatically installed with the database

2.1.4 Operating System Configuration Requirements for Real Application Clusters

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

2.2 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 procedures describe the installation:

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 will do the following tasks:
- Create the ordbcc user.
- Create the dbdbcc group.
- Ensure the /admin directory exists.
- Restore 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 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
```
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 will check 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 will do the following tasks:
- Create the ordbname user.
- Create the dbdbname group.
- Run /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.
- Restore the database image. The database will be restored under the /DBNAME/oracle directory according to the Oracle Outsourcing file layout standard.
Once 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 2. The following tasks describe how to reconfigure the database:
1. Log in as the ordbname user.
2. Set the following variables:
  - SRC_CC_DBNAME. Enter DGOLD.
  - DST_CC_DBNAME. Enter the new database name or SID.
  - SRC_CC_HOSTNAME. Enter the local host name.
  - DST_CC_HOSTNAME. Enter the new host name.
  - SRC_CC_LISTENER_PORT. Enter 10650.
  - DST_CC_LISTENER_PORT. Enter the desired listener port number.
3. Run the reconfig.sh script using the following command:
```
/admin/dbcc/3.1.0/ref_config/reconfig.sh -single [-silent]
```
  The script will do the following tasks:
  - Run /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.
  - Modify the configuration files to reflect the correct hostnames and port numbers.
  - Regenerate the control files, if needed.
  - Run /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.
Note:
The silent option should be used with extreme care.

2.3 Real Application Clusters Installation

The following procedure describe Oracle9i Database Certified Configuration installation for 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 will do the following tasks:
- Create the ordbcc user.
- Create the dbdbcc group.
- Ensure the /admin directory exists.
- Restore 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 -cm -imagefile GOLDIMAGE  
```
The script can be run from any node, and will install the cluster manager on both nodes. The script will do the following tasks:
- Prompt for node name. The user should enter the private node names.
- Check rsh access for the root user to all nodes on the private network.
- Create the ororacm user on all node with identical user IDs.
- Create the dboracm group on all nodes with identical group IDs.
- Run /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -preimage -rac to check that the system configuration requirements are met. The output of ocheck will be logged in the /var/tmp/ocheck.preimage.ORACM.log file.
- Restore the /oracm directory on every node.
- Run /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -postimage -rac to check that the image restoration was successful. The output of ocheck will be logged in the /var/tmp/ocheck.postimage.ORACM.log file.
The dbcc_image.sh script will log its actions in the /var/tmp/dbcc_image.restore.ORACM.log file.

Run the cmconfig.sh script using the following command:
```
/admin/dbcc/3.1.0/ref_config/cmconfig.sh
```
The script is run from one node only, and will configure the cluster manager for all nodes. The script will do the following tasks:
- Configure and start gsd processes on all nodes.
- Create the srvconfig and quorum devices as files for NAS, or raw volumes for storage that is not NAS, depending on the shared storage configuration. If the shared storage is NAS, then the files will be placed in the /oracm/oradata directory.
The script logs its actions in the /var/tmp/cm_config.log file.
Run the dbcc_image.sh script using the following command:
```
/admin/dbcc/3.1.0/install/dbcc_image.sh -restore -rac -imagefile GOLDIMAGE \

[-includedb] -dbname DBNAME 
```
In the preceding command, the -includedb option is supported only for NAS datafiles.

The script will do the following tasks:
- Run /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.
- Check that oracm is up and running.
- Restore the spfile file from the ORACLE_HOME/dbs directory to the /dbname/oradata/data01 directory.
- Create links to the spfile file on every node.
- Run /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.
The dbcc_image.sh script logs its actions in the /var/tmp/dbcc_image.restore.DBNAME.log file.
Reconfigure or configure the database, based on the following criteria:
- If the -includedb parameter was used, then reconfigure database to set the hostnames and port numbers for the new installation. The control files may need to be regenerated for the database image if files were moved from their original directories. To reconfigure the database, log in as the ordbname user, set the SRC_CC_DBNAME variable to DGOLD, the DST_CC_DBNAME variable to the new database name, and run the following script:
```
/admin/dbcc/3.1.0/ref_config/reconfig.sh -rac [-silent]
```
  Note:
  The silent option should be used with extreme care.
  
  The preceding command will perform the following tasks:
  - Run /admin/dbcc/3.1.0/reconfig/ocheck/ocheck -reconfig -rac to perform all pre-requirements checks. The output of ocheck will be logged in the /var/tmp/ocheck.reconfig.DBNAME.log file.
  - Modify configuration files to reflect the correct hostnames. The port numbers will not be changed.
  - Regenerate control files, if necessary.
  - Run /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.
  The reconfig.sh script logs its actions in the /admin/dbcc/3.1.0/ref_config/logs/reconfig.log file.
- If the -includedb parameter was not used and the user wants a seed database restored on raw volumes, then configure the database using the config.sh script. In this release, the config.sh script is only supported for Real Applications Clusters. The following command shows the syntax for the script:
```
/admin/dbcc/3.1.0/ref_config/config.sh -rac -raw -dbname DBNAME
```
  The config.sh script should be used in the following scenarios:
  - The dbcc_image.sh script was not able to create the datafiles for the seed database because the datafile storage is not a NetApp NAS storage. The config.sh script will create the seed database.
  - The database was restored without the -includedb option, and the user wants to create a seed database.
  The config.sh script logs its actions in the /admin/dbcc/3.1.0/ref_config/log/conf_DBNAME.log file.
- If the -includedb parameter was not used and the user wants a seed database restored on NAS storage, then configure the database using the config.sh script. In this release, the config.sh script is only supported for Real Applications Clusters. The following command shows the syntax for the script:
```
/admin/dbcc/3.1.0/ref_config/config.sh -rac -nas -dbname DBNAME
```
  The config.sh script should be used in the following scenarios:
  - The dbcc_image.sh script was not able to create the datafiles for the seed database because the datafile storage is not a NetApp NAS storage. The config.sh script will create the seed database.
  - The database was restored without the -includedb option, and the user wants to create a seed database.
  The config.sh script logs its actions in the /admin/dbcc/3.1.0/ref_config/log/conf_DBNAME.log file.

2.4 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 the gold image be used 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, or the database name is not oracm. The oracm database name is reserved for the cluster manager and does not include datafiles. 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.