1 Overview

This chapter describes the Oracle9i Database Certified Configuration, the procedures necessary to install and configure the certified configuration, and the tools provided with the certified configuration. It contains the following topics:

Oracle9i Database Certified Configuration
File Layout
Users and Groups
Tools and Scripts

1.1 Oracle9i Database Certified Configuration

Oracle9i Database Certified Configuration is comprised of a gold image and tools. The tools can be used for the following:

Rapidly install a single-instance or a Real Application Clusters database, including binaries and data
Configure a database
Clone a database
Convert a single-instance to a Real Application Clusters database
Add new instances to an existing Real Application Clusters database

1.1.1 Gold Image

The Oracle9i Database Certified Configuration includes an image, known as the gold image, which can be used to install and restore the Oracle9i database. The gold image is a single image that includes the binaries for an Oracle database single instance, and Real Application Clusters environments. It also includes a seed single-instance database, and a seed Real Application Clusters database. The seed database can be used as an example, and allows the administrator to verify proper installation and configuration of the Oracle software.

The gold image is located on the /net/plnfs2/vol/build/LNX/project/linux/dbcc/9.2.0.3.0 server which is NFS mountable within the Oracle firewall. The user should download the gold image and the dbcc_install_admin.sh script from this server.

Prior to installing or configuring the image, the Oracle9i Database Certified Configuration tools check the system by running the ocheck script. This script will ensure that the hardware, operating system, file layout and patches comply with the standard certified configuration specifications.

1.2 File Layout

The Oracle9i Database Certified Configuration tools are designed to be as flexible as possible, however the user should ensure the file system layout is compliant with Oracle Outsourcing File System and Naming Standards. The tools have been tested only on systems that conform to the Oracle Outsourcing standards. The gold image follows the file system and naming standards for Oracle Outsourcing.

1.2.1 Operating System File Layout:

Table 1-1 lists the operating system file layout for Oracle9i Database Certified Configuration:

Table 1-1 Oracle9i Database Certified Configuration Operating System File Layout

Directory	Minimum Size	Description
/	9 GB	Root file system which also contains the directories `/var`, `/tmp`, `/usr`, and so on.
/admin	4 GB minimum or rest of the disk	Top-level directory for certified configuration scripts and tools. There will be a sub-directory for each certified configuration type such as `/admin/dbcc/``version`.
/boot	128 MB	Operating system kernel.
/oem	1 GB	Oracle Enterprise Manager installation.
swap	4 GB	Recommended swap space size is 2 times the size of RAM.

1.2.2 Oracle Files Layout

Table 1-2 lists the Oracle files layout for Oracle9i Database Certified Configuration. In the table, SID represents DBNAME for single-instance databases, and DBNAME plus instance number for Real Application Clusters databases.

Table 1-2 Oracle9i Database Certified Configuration Oracle FIles Layout

File System/Directory	Description
/`SID`/arch	File system for database archive logs.
/`SID`/backup	File system for database backup files. This partition is currently only created for the Production instance.
/`SID`/oracle	File system containing the oracle database binaries and configuration files
/`SID`/oradata	File system containing `data01`, `data02` and `data03` directories.
/`SID`/oradata/data01	All data files except system and temp data files. For example, data files for Oracle Portal, Oracle Files, e-mail, tools, and so on. These are mainly the `data.dbf`, `idx.dbf`, and `control01.ctl` files.
/`SID`/oradata/data02	Contains the system and temp files. These are mainly the `system.dbf`, `temp.dbf`, and `control02.ctl` files.
/`SID`/oradata/data03	Log files only. These are mainly the `log*.dbf`, and `control03.ctl` files.

See Also:

For more information about file layout, refer to File Systems and Other Naming Standards for Outsourcing by Rajesh Shah

1.3 Users and Groups

Table 1-3 lists the users and groups used during the installation and configuration of the Oracle9i Database Certified Configuration.

Table 1-3 Oracle9i Database Certified Configuration Users and Groups

User or Group	Description
dbdbcc	Group that owns the `/admin/dbcc` directory. The `dbcc` scripts are stored in the directory.
dboracm	Group that owns the `/oracm` directory. The directory contains the cluster manager binary and configuration files.
db`dbname`	Group that owns the `DBNAME` database.
ordbcc	User that owns the `/admin/dbcc` directory. The directory contains the `dbcc` scripts. This user is a member of the `dbdbcc` group.
or`dbname`	User that owns the `DBNAME` database. There are as many of these users as there are databases on the system. For example, there may be a database named `DBA`, and one named `DBB`. The user would be `ordba` for the first one, and `ordbb` for the second one. This user is a member of the `db``dbname` group.
ororacm	User that owns the `/oracm` directory. The directory contains the cluster manager binary and configuration files. This user is a member of the `dboracm` group.

1.4 Tools and Scripts

Several scripts and tools are included with the certified configuration.

Validation Tool
Installation Script
Image Restoration and Creation Script
Reconfiguration Script
Cluster Manager Configuration Script
Configuration Script for Real Application Clusters
Conversion Utility
Administration Scripts

1.4.1 Validation Tool

Oracle9i Database Certified Configuration hardware and operating system are validated before installation and configuration by the ocheck tool. After installation and configuration, it checks to ensure the installation and configuration were successful. It can also compare a system to a known standard state. Output is displayed on the screen, and logged in the /var/tmp directory.

The following command shows the syntax for the tool:

/admin/dbcc/3.1.0/ref_config/ocheck/ocheck -product prod_name phase  \

-dbname DBNAME

Table 1-4 lists the tool parameters.

Table 1-4 ocheck Tool Parameters

Parameter	Description
dbname	Identifies the database to be checked by the tool.
product	Checks the product name defined by the `prod_name` option. The `ocheck.chk` file lists the product names.
phase	Defines the phase of the installation. The `ocheck.chk` file lists the phases. Currently, the following phases are available: `-preinstall` and `-postinstall` run checks before and after product installation. `-preconfig` and `-postconfig` run checks before and after product configuration. `-preimage` and `-postimage` run checks before and after installation of a product image. `-reconfig` runs checks before product reconfiguration, such as cloning, and single-instance to Real Application Clusters conversion. `-system` runs checks to ensure suitability of system hardware and operating system configuration for installation of Oracle products. `-all` runs all available checks for a given product.

The following examples show system states that can be checked using the ocheck tool and parameters:

The system hardware and operating system will allow an Oracle installation (-system)
A system is ready for image restoration (-phase preimage)
Image restoration was successful (-phase postimage)
A system is ready for reconfiguration (-phase reconfig)
A system is ready for configuration (-phase preconfig)
The configuration or reconfiguration was successful (-phase postconfig)

See Also:

For more information on the ocheck tool, refer to Appendix A, " Environment Checking Tool"

1.4.2 Installation Script

The dbcc_install_admin.sh script is used to install the Oracle9i Database Certified Configuration scripts on a server. The script must be downloaded with the gold image. It is run by the root user, and will do the following tasks:

Create the ordbcc user and dbdbcc group which will own the /admin/dbcc directory.
Restore the Oracle9i Database Certified Configuration scripts under the /admin/dbcc/version directory. For this release, the version is 3.1.0. The dbcc_install_admin.sh script is restored under the /admin/dbcc/version /install directory.

The following command shows the syntax:

dbcc_install_admin.sh IMAGEFILE

1.4.3 Image Restoration and Creation Script

The dbcc_image.sh script restores a database image from the gold image or from an image created by the script. The dbcc_image.sh script must be run by the root user.

The following command shows the syntax for image restoration:

/admin/dbcc/3.1.0/install/dbcc_image.sh -restore -single|-rac \

-imagefile GOLDIMAGE[-includedb|includeconfig] -dbname DBNAME

The following command shows the syntax for image restoration for an instance dedicated to cluster manager:
```
/admin/dbcc/3.1.0/install/dbcc_image.sh -restore -cm -imagefile GOLDIMAGE
```

The following command shows the syntax for image creation:

/admin/dbcc/3.1.0/install/dbcc_image.sh -create -single|-rac  \

-dbname DBNAME -imagefile GOLDIMAGE [-includedb|-includeconfig]

Table 1-5 describes the options for the preceding commands:

Table 1-5 Image Restoration and Creation Options

Option	Description
cm	Specifies to restore an instance dedicated to the cluster manager under the `/oracm/oracle` and `oracm/oradata` directories. This is optional.
imagefile	Specifies the `IMAGEFILE` to use for the restoration. This is mandatory.
includeconfig	Specifies to include the instance configuration files such as `init.ora`, `SPFILE`, password file, `listener.ora` and `tnsnames.ora` along with the binaries. This is optional, and only used with the `create` option.
includedb	Specifies the datafile and configuration files should be restored along with the database binaries. If the option is not used, then only the database binaries are restored for the database.
rac	Specifies to restore a Real Application Clusters database. Only two nodes can be created with this script, but more nodes can be added using the `convex` utility. This is optional.
single	Specifies to restore a single-instance database. This is optional.

1.4.4 Reconfiguration Script

After an image has been restored with the includedb option, the image must be reconfigured to become functional. The instance configuration files need the proper hostnames, port numbers, file system layout, and so on.

The reconfig.sh script should be used to start up the database when reconfiguration is complete. The reconfig.sh script can also be used as part of the cloning procedure. The following command shows the syntax for the reconfig.sh script. The script must be run by the ordbname user, where dbname is the name of the database.Syntax

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

In the preceding command, the silent option can be used if the environment variables have been set prior to running the script. The recoverdb option allows the reconfig.sh script to perform recovery of the database using the backup control files. Refer to Chapter 2, " Installation " for more information about the option.

1.4.5 Cluster Manager Configuration Script

The cmconfig.sh script configures the cluster manager and gsd processes on all nodes of an Oracle9i Database Certified Configuration across all cluster nodes. It is run after the /admin/dbcc/3.1.0/install/dbcc_image.sh -restore -cm -imagefile GOLDIMAGE command. The cmconfig.sh script must be run by the root user. The following command shows the syntax:

/admin/dbcc/3.1.0/ref_config/cmconfig.sh

The cmconfig.sh script will also create a script, /admin/dbcc/3.1.0/ref_config/oracm_gsd, which can be used to start and stop the cluster manager and gsd processes. The following command shows the syntax:

/admin/dbcc/3.1.0/ref_config/oracm_gsd start|stop

This script is linked to the /etc/rc.d/init.d/oracm_gsd script.

1.4.6 Configuration Script for Real Application Clusters

The config.sh script configures the Oracle cluster manager, and creates a seed database. The script also configures the following:

Auto-startup of Oracle services
Listener
Oracle agent
Service name
Transparent Application Failover (TAF) for Real Application Clusters environments

The following command shows syntax for the script. The script must be run by the root user.

/admin/dbcc/3.1.0/ref_config/config.sh -dbname DBNAME -rac [-nas|-raw] \

[-silent]

Table 1-6 lists the script parameters.

Table 1-6 config.sh Script Parameters

Parameter	Description
dbname	Specifies the database name.
nas	Specifies the data files will be on a shared NAS file system.
rac	Configures the clusterware, and creates and configures a seed database on the external shared disks. It also creates the raw volumes on the disks.
raw	Specifies the data files will be in shared raw volumes.
silent	Enables a silent, non-interactive installation. This parameter should be used with caution.

Note:

The silent option should be used with extreme care. The genocc utility should be used to modify the configuration files before reconfiguring the database with the silent option.

1.4.7 Conversion Utility

The convex utility can convert a single-instance database into a Real Application Clusters database. It can also expand the number of nodes of an existing Real Application Clusters environment. The script must be run by the ordbname user where dbname is the name of the database. The following command shows the syntax for the script:

/admin/dbcc/3.1.0/ref_config/convex

See Also:

For more information about the convex utility, refer to Chapter 4, " Single-node Database to Real Application Clusters Database Conversion"

1.4.8 Administration Scripts

Oracle9i Database Certified Configuration includes administration scripts to start and shut down an instance, or cluster manager. The localoradb script can start and shutdown an Oracle instance as well as the associated listener and OEM SNMP agent. The oracm_gsd script can be used to start and stop the cluster manager and gsd processes.

1.4.8.1 localdbora Script

The localoradb script can start and shutdown an Oracle instance. The script must be run as the ordbname user who owns the database. The following command shows the syntax for the script:

/admin/dbcc/3.1.0/ref_config/localdbora start|stop

The script will start or shut down an instance locally. For Real Application Clusters environments, the script must be run on each node.

1.4.8.2 oracm_gsd Script

The oracm_gsd script is created by the cmconfig.sh script, and must be run by the root user. The following command shows the syntax for the script:

/admin/dbcc/3.1.0/ref_config/oracm_gsd start|stop

The script will start or shut down cluster manager and other services such as listener and agent. For Real Application Clusters environments, the script must be run on each node.

Note:

There is only one oracm and gsd process per node, and they are shared by all Real Application Clusters running on a node. Using the oracm_gsd script on a node running multiple Real Application Clusters instances will impact all instances on the node.