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

Oracle9i Database Certified Configuration

Oracle9i Database Certified Configuration consists of a gold image and tools. The tools are 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

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 a single-instance Oracle database, and Real Application Clusters environments. It also includes a single-instance seed 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/plnfs5/vol/build/FSL/project/solaris64/dbcc/9.2.0.2 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.

Before 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.

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.

Operating System File Layout

The following table lists the operating system file layout for Oracle9i Database Certified Configuration.

Table 1-1 Oracle9i 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`.
/oem	1 GB	Oracle Enterprise Manager installation.
swap	4 GB	Recommended swap space size is 2 times the size of RAM.

Oracle Files Layout

The following table 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 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 located at the following address:

http://files.oraclecorp.com/content/AllPublic/Workspaces/Outsourcing%20Standards-Public/CC_OFA_Dir_Structure_Stds.doc

Users and Groups

The following table 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.
db`dbname`	Group that owns the `DBNAME` database.
dba	Group that owns the Oracle `UDLM` package required for Real Application Clusters.
ordbcc	User that owns the `/admin/dbcc` directory. This 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. The default shell is `/bin/ksh` and the home directory is `/``dbname``/oracle`.

Tools and Scripts

Oracle9i Database Certified Configuration contains the following tools and scripts.

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

Validation Tool

Oracle9i Database Certified Configuration hardware and operating system are validated before installation and configuration by the ocheck tool. After installation and configuration, the ocheck tool ensures the installation and configuration are 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 [-o outputfile]

The following table 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 conversion from single-instance to Real Application Clusters. `-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, see Appendix A, "Environment Checking Tool".

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 and run by the root user. It will perform 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

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 creation:

/admin/dbcc/3.1.0/install/dbcc_image.sh -create -single|-rac  \
-dbname DBNAME -imagefile GOLDIMAGE [-includedb|-includeconfig]

The following table describes the options for the preceding commands:

Table 1-5 Image Restoration and Creation Options

Option	Description
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.
single	Specifies to restore a single-instance database. This is optional.

Reconfiguration Script

The reconfiguration script applies only to single-instance databases.

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 host names, 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 [-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 this option.

Configuration Script for Real Application Clusters

The config.sh script configures the Oracle cluster environment, 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 -raw \
[-silent]

The following table lists the script parameters.

Table 1-6 config.sh Script Parameters

Parameter	Description
dbname	Specifies the database name.
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 that the data files will be in shared raw volumes.
silent	Enables a silent, non-interactive installation. Use this parameter with caution.

Note:

Use the silent option with caution. The genocc utility must be used to modify the configuration files before reconfiguring the database with the silent option.

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.

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. Real Application Clusters configuration also creates the /etc/init.d/rc.dbora file on all nodes.