1 Overview of Oracle Database Installation

1.3.1 Completing a Minimal Linux Installation

To complete a minimal Linux installation, select a minimal install option (either a custom installation where you select the Minimal option from Package Group Selection, or where you deselect all packages except for the Base pack). This installation lacks many RPMs required for installation. However, when you install the Oracle Validated RPM for your platform, the RPM downloads the minimum number of packages required to run Oracle Clusterware and Oracle Database.

Unbreakable Linux Network (ULN) customers can obtain the Oracle Validated RPM by using up2date. If you are not a ULN customer, and your operating system is Red Hat or Oracle Enterprise Linux, then you can obtain the Oracle Validated RPM at the following URLs:

Enterprise Linux 4:

http://oss.oracle.com/el4/oracle-validated/

Enterprise Linux 5:

http://oss.oracle.com/el5/oracle-validated/

1.3.2 Completing a Default Linux Installation

If you do not install the Oracle Validated RPM, then Oracle recommends that you install your Linux operating system with the default software packages (RPMs). This installation includes most of the required packages and helps you limit manual checks of package dependencies. Oracle recommends that you do not customize the RPMs during installation.

For information about a default installation, log on to My Oracle Support (formerly OracleMetaLink):

https://metalink.oracle.com

Search for "Default RPM."

After installation, start system-config-packages and add all the Legacy Software Development packages. Review system requirements for the distribution to ensure that you have all required kernel packages installed, and complete all other configuration tasks required for the distribution, and for the system configuration.

1.3.3 About the Oracle Validated Configuration RPM

If the Linux distribution is Oracle Enterprise Linux, or Red Hat Enterprise Linux, and you are an Unbreakable Linux customer, then you can complete most preinstallation configuration tasks by using the Oracle Validated Configurations Setup packages, available from the Unbreakable Linux Network (ULN).

When Unbreakable Linux Network is installed, the Oracle Validated Configuration packages sets and verifies system parameters based on recommendations from the Oracle Validated Configurations program, and installs any additional packages needed for installing Oracle Clusterware and Oracle Database. It also updates sysctl.conf settings, system startup parameters, user limits, and driver parameters to values which extensive testing shows will provide better performance.

To become an Oracle Unbreakable Linux customer, contact your sales representative, or purchase a license from the Unbreakable Linux store:

http://oraclestore.oracle.com/OA_HTML/ibeCZzpHome.jsp

To register your server on the Unbreakable Linux Network, or to find out more information, refer to the following URL:

https://linux.oracle.com

1.3.4 Installing the Oracle Validated Configuration RPM

Use the following procedure to subscribe to Oracle Unbreakable Linux channels, and to add the Oracle Software for Enterprise Linux channel that distributes the Oracle Validated Configurations Setup RPM:

1. Complete a default Oracle Enterprise Linux workstation installation, or a default Red Hat Enterprise Linux installation.

2. Register the server with Unbreakable Linux Network (ULN). By default, you are registered for the Enterprise Linux Latest channel for the operating system and hardware.

3. Log in to ULN at the following URL:

   https://linux.oracle.com

4. Click the Systems tab, and in the System Profiles list, select a registered server. The System Details window opens, and displays the subscriptions for the server.

5. From the Available Channels list, select the Oracle Software for Enterprise Linux channel that is appropriate for the installation of Linux. For example: Oracle Software for Enterprise Linux 4 (x86-64).

6. Click Subscribe.

7. From a terminal session, as a root user, enter the following command:

   # up2date --nox --show-channels
   

   An output similar to the following is displayed. This output indicates that you have subscribed to the Oracle Software for Enterprise Linux channel. For example:

   el4_i386_latest
   el4_i386_oracle
   

8. Open a terminal session as a root user, and install the Oracle Validated Configurations Setup RPM with up2date with the following command:

   # up2date --install oracle-validated
   

1.4.1 Hardware and Software Certification

The platform-specific hardware and software requirements included in this guide were current when this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support (formerly OracleMetaLink) Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support (formerly OracleMetaLink) Web site is available at the following URL:

http://metalink.oracle.com/

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in, click Certify on the top right-hand side of the screen. The Certifications page appears. You can choose the certification either by product or by platform.

Other options include Oracle's Certification Matrices, Desupport Notices, and Product Availability.

1.4.2 Multiple Oracle Homes Support

This product supports multiple Oracle homes. This means, you can install this release or earlier releases of the software more than once on the same system, in different Oracle home directories.

1.4.3 Grid Infrastructure for a Standalone Server

The grid infrastructure for a standalone server provides the infrastructure to include your single instance database in an enterprise grid architecture. Oracle Database 11g Release 2 (11.2) combines these infrastructure products into one software installation called the grid infrastructure home. On a single instance database, the grid infrastructure home includes Oracle Restart and Automatic Storage Management (ASM) software.

If you want to use Automatic Storage Management or Oracle Restart, then you should first install Oracle grid infrastructure for a standalone server, and then install Oracle Database 11g Release 2 (11.2).

1.4.4 Oracle Cluster Synchronization Services

When you install Oracle grid infrastructure for a standalone server, it will configure the single-node version of Oracle Cluster Synchronization Services (CSS). The CSS service is required to enable synchronization between an Automatic Storage Management instance and the database instances that rely on it for database file storage. Because the service must be running before any Automatic Storage Management instance or database instance starts, it is configured to start automatically by Oracle Restart before the Automatic Storage Management instance is started.

For Oracle RAC installations, the CSS daemon is installed with Oracle Clusterware in a separate Oracle home directory (also called the grid infrastructure directory). For single instance installations, the CSS daemon is installed in and runs from the grid infrastructure home which is the same home that runs Automatic Storage Management.

1.4.5 Installing Oracle Database Vault in an Oracle Data Guard Environment

If you plan to use Oracle Data Guard with Oracle Database Vault, then refer to Note 754065.1 on the My Oracle Support (formerly OracleMetaLink) Web site at the following URL:

http://metalink.oracle.com/

1.4.6 Oracle Database Vault Default Audit Policy and Initialization Parameters

Oracle Database Vault installs a baseline database auditing policy. This policy covers the access control configuration information stored in Database Vault database tables, information stored in Oracle Catalog (rollback segments, tablespaces, and so on), the use of system privileges, and Oracle Label Security configuration. When you install Oracle Database Vault, the security specific database initialization parameters are initialized with default values.

1.5.1 Interactive Installation Types

When you use the interactive method to install Oracle Database, Oracle Universal Installer displays a series of screens that enable you to specify all the required information to install the Oracle Database software and optionally create a database.

Starting with Oracle Database 11g Release 2 (11.2), Oracle Universal Installer provides you the following options:

• Desktop Class: Select this option if you are installing on a laptop or desktop class system. This option includes a starter database and allows minimal configuration. This option is designed for those who want to quickly set up a database.

• Server Class: Select this option if you are installing on a server class system, such as what you would use when deploying Oracle in a production data center. This option allows for more advanced configuration options. Advanced configuration options available with this option include Oracle RAC, Automatic Storage Management, backup and recovery configuration, integration with Enterprise Manager Grid Control, and more fine-grained memory tuning, among others.

  Furthermore, the Server Class option provides you with the following installation types:

  • Typical: Select this installation method if you want to quickly install Oracle Database. This installation type requires minimal user input. It installs the software and optionally creates a general-purpose database using the information that you specify on the screen. It is the default installation type.

  • Advanced: Select this installation type if you want to complete any of the following tasks:

    • Select a database character set or different product languages

    • Create the EXAMPLE tablespace during the installation

    • Create a database on a different file system from the software

    • Specify different passwords for administrative schemas

    • Configure automated backups or Oracle Enterprise Manager notifications

    • Configure Oracle Configuration Manager

    • Customize components from the available components list. In the Select Database Edition screen, if you select Enterprise Edition, then Oracle Universal Installer automatically selects the components most customers need for their Oracle Database installation. You can also click Select Options to customize components from the components list.

      See Also:

      "Reviewing Component-Specific Installation Guidelines" for additional information on Oracle database installation

1.5.2 Automated Installation Methods Using Response Files

By creating a response file and specifying this file when you start Oracle Universal Installer, you can automate some or all of the Oracle Database installation. These automated installation methods are useful if you must perform multiple installations on similarly configured systems or if the system where you want to install the software does not have X Window system software installed.

When you use a response file, you can run Oracle Universal Installer in the following modes, depending on whether you specify all of the required information or not:

• Silent Mode: Oracle Universal Installer runs in silent mode if you use a response file that specifies all required information, and specify the-silent option when starting Oracle Universal Installer. None of the Oracle Universal Installer screens are displayed.

• Response File Mode: Oracle Universal Installer runs in response file mode if you do not specify all required information in the response file.

For more information about these modes and about how to complete an installation using response files, refer to Appendix A.

1.7.1 Preconfigured Database Types

Oracle provides the following preconfigured database types that you can create or customize during the installation:

• General Purpose/Transaction Processing

• Data Warehouse

Refer to the online help provided by either Oracle Universal Installer or Oracle Database Configuration Assistant for a description of these preconfigured database types.

1.7.2 Installation Choices that Affect Database Creation

Oracle Universal Installer runs Oracle Database Configuration Assistant in one of two modes, depending on the choices that you make during the installation:

• Silent or response file mode

  If you choose either the Enterprise Edition or Standard Edition database edition, then choose to create a preconfigured database type. Oracle Universal Installer prompts you for the minimum amount of information required to create a database of the type you choose. It then runs Oracle Database Configuration Assistant in silent or response file mode to create the database after it installs the software.

  Note:

  Oracle recommends that you use this method to create a database if you have not previously created one.

• Interactive mode

  If you choose Advanced database configuration option, then Oracle Universal Installer does not prompt you for database information. Instead, it installs the software and then runs Oracle Database Configuration Assistant in interactive mode. Using the screens in Oracle Database Configuration Assistant, you can either modify one of the preconfigured database types or customize the database.

  Note:

  If you choose this method to create a database, then click Help on any of the Oracle Database Configuration Assistant screens for a description of the information that you must specify on that screen.

1.7.3 Creating a Database After Installation

If you decide not to create a database during the installation, then you can use Oracle Database Configuration Assistant to create one after you have installed the software. For more information about using Oracle Database Configuration Assistant to create a database after installation, refer to the Oracle Database 2 Day DBA manual.

1.8.1 File System

If you choose the file system option, then Oracle Database Configuration Assistant creates the database files in a directory on a file system mounted on the computer. Oracle recommends that the file system you choose be separate from the file systems used by the operating system or the Oracle software. The file system that you choose can be any of the following:

• A file system on a disk that is physically attached to the system

  If you are creating a database on basic disks that are not logical volumes or RAID devices, then Oracle recommends that you follow the Optimal Flexible Architecture (OFA) recommendations and distribute the database files over more than one disk.

• A file system on a logical volume manager (LVM) volume or a RAID device

  If you are using multiple disks in an LVM or RAID configuration, then Oracle recommends that you use the stripe and mirror everything (SAME) methodology to increase performance and reliability. Using this methodology, you do not need to specify more than one file system mount point for database storage.

• A network file system (NFS) mounted from a certified network attached storage (NAS) device. You also have the option to use the Direct NFS feature, which simplifies the administration of NFS configurations and also offers performance improvements.

  See Also:

  "Direct NFS Client" for more information on the Direct NFS feature

  If the NAS device is certified by Oracle, then you can store the database files on them.

If you choose the Advanced database creation option, then you can also choose to use the Oracle-managed files feature with the new database. If you use this feature, then you must specify only the database object name instead of file names when creating or deleting database files.

1.8.2 Automatic Storage Management

Automatic Storage Management is a high-performance storage management solution. For Oracle Database files, it simplifies the management of a dynamic database environment, such as creating and laying out databases and managing disk space.

Automatic Storage Management can be used with single database installations, multiple database installations, and in Oracle RAC environments. It can be used with databases created in Oracle Database 10g Release 1 (10.1.0.3 or later). However, Oracle Database 11g Release 2 (11.2) databases must use Automatic Storage Management from Oracle Database 11g Release 2 (11.2) or later. Automatic Storage Management is installed as part of the grid infrastructure installation. If you plan to use Automatic Storage Management, then you must install the grid infrastructure before installing your database. If you want to upgrade an existing Automatic Storage Management installation, then you must upgrade Automatic Storage Management by running an Oracle grid infrastructure upgrade.

Automatic Storage Management manages the storage of all database files, such as redo logs, control files, and data pump export files. Automatic Storage Management can manage the Oracle Database executable binary files as well as any other non-database file by creating a file system with Oracle Automatic Storage Management Cluster File System. Though Oracle Automatic Storage Management Cluster File System is cluster aware it works as a file system on a single instance database also.

At a high level, implementing Automatic Storage Management involves allocating partitioned disks for Oracle Database with preferences for striping and mirroring. Automatic Storage Management manages the disk space for you. This helps avoid the need for traditional disk management tools, such as Logical Volume Managers (LVM), file systems, and the numerous commands necessary to manage both. The synchronization between Automatic Storage Management and the database instance is handled by CSS.

The following are components of an Automatic Storage Management installation:

• Automatic Storage Management Disk Groups

• Automatic Storage Management Instance

Automatic Storage Management Disk Groups

A disk group is a set of disk devices that Automatic Storage Management manages as a single unit. Each disk device can be an individual physical disk, a multiple disk device, such as a RAID storage array or logical volume, or even a partition on a physical disk. However, in most cases, disk groups consist of one or more individual physical disks. To enable Automatic Storage Management to balance input-output operation and storage efficiently within the disk group, you must ensure that all devices in the disk group have similar, if not identical, storage capacity and performance.

You can set the redundancy and striping attributes of individual file types within a disk group by using Automatic Storage Management disk group templates. When you create a disk group, Automatic Storage Management creates a set of default templates for that disk group. Default template settings depend on the disk group type. For example, the default template for control files for a normal redundancy disk group sets three-way mirroring. All other file templates are two-way mirrored. For a high redundancy disk group, the default mirroring cannot be changed, which implies that all files are always three-way mirrored in a high redundancy disk group. You can modify the default templates to suit your site's needs. Refer to Oracle Database Storage Administrator's Guide for more information.

Automatic Storage Management spreads data evenly across all the devices in the disk group to optimize performance and utilization. You can add or remove disk devices from a disk group without shutting down the database. When you add or remove disks, Automatic Storage Management rebalances the files across the disk group. You can create multiple disk groups to handle specific tasks, such as backup and recovery operations, in addition to regular file storage activities.

When you add a device to a disk group, you can specify a failure group for that device. Failure groups identify disk devices that have common failure characteristics, for example, devices that are attached to the same controller. If the controller fails, then all devices attached to it become unavailable. By default, each device also belongs to its own failure group. By using the failure groups you specify, Automatic Storage Management can distribute data among the devices in the disk group to minimize the risk of data loss caused by component failures.

Automatic Storage Management Instance

The Automatic Storage Management instance is a special Oracle instance that manages Automatic Storage Management disk groups. The Automatic Storage Management instance is created and started, if necessary, when you install Oracle grid infrastructure. Oracle recommends that you have the Automatic Storage Management instance in its own Oracle home. Oracle also recommends that you run this instance before you start a database instance that uses Automatic Storage Management.

For an Oracle Database installation, you only need one Automatic Storage Management instance, regardless of the number of database instances on the computer.

1.9.1 Management Options for Preconfigured Databases

When you choose to create a preconfigured database during the installation, you must select the Oracle Enterprise Manager interface that you want to use to manage the database. The following options are available:

• Use Grid Control for central database management

  This option is available only if an Enterprise Manager Database Control Agent is installed on the system. When Oracle Universal Installer detects an Oracle Management Agent on the system, you can choose this option and specify the Oracle Management Service that you want to use to manage the database.

  If an Oracle Management Agent is not installed, then you must use Database Control to manage the database. However, if Oracle Management Agent is installed after Oracle Database, then you can use Grid Control to manage this database.

• Use Database Control for local database management

  This option is selected by default if an Oracle Management Agent is not installed on the system. However, even if a Management Agent is installed, you can still choose to configure Database Control to manage the database.

1.9.2 Management Options for Custom Databases

If you choose the Advanced database configuration option, then Oracle Universal Installer runs Oracle Database Configuration Assistant in interactive mode. Using a screen in Oracle Database Configuration Assistant, you can specify the Oracle Enterprise Manager interface that you want to use to manage the database. Alternatively, you can also choose not to configure the database with Enterprise Manager.

Oracle recommends that you configure the database to use Enterprise Manager during installation. However, if you choose not to configure the database to use Enterprise Manager during the installation, then you can use Oracle Database Configuration Assistant after the installation to configure the database to use it.

1.9.3 Features Provided by Oracle Enterprise Manager Database Control

Oracle Enterprise Manager Database Control provides a Web-based user interface that enables you to monitor, administer, and maintain an Oracle database. You can use it to perform all database administration tasks. You can also use it to determine information about the database, such as:

• Instance name, database version, Oracle home location, media recovery options, and other instance data

• Current instance availability

• Database alert information

• Session and SQL-related performance information

• Space usage matrix

In addition, it provides you with automatic notification of security alerts, and the ability to download and apply patches for the software.

1.10.1 Enabling Automated Backups

If you enable automated backups, then Oracle Enterprise Manager schedules a daily backup job that uses Oracle Recovery Manager (RMAN) to back up all of the database files to a disk storage area called the fast recovery area. The first time the backup job runs, it creates a full backup of the database. Subsequent backup jobs perform incremental backups, which enable you to recover the database to its state at any point during the preceding 24 hours.

To enable automated backup jobs during installation, you must specify the following information:

• The location of the fast recovery area

  You can choose to use either a file system directory or an Automatic Storage Management disk group for the fast recovery area. To set the default values for fast recovery area and data file location, use Oracle base as the starting point.

  • Default fast recovery area: $ORACLE_BASE/recovery_area

  • Default data file location: $ORACLE_BASE/oradata

  The default disk quota configured for the fast recovery area is 2 GB. For Automatic Storage Management disk groups, the required disk space depends on the redundancy level of the disk group that you choose. Chapter 2 describes how to choose the location of the fast recovery area and identifies its disk space requirements.

• An operating system user name and password for the backup job

  Oracle Enterprise Manager uses the operating system credentials that you specify when running the backup job. The user name that you specify must belong to the UNIX group that identifies database administrators (the ORA_DBA group). This user also must have Logon As A Batch Job privilege.

1.10.2 Backup Job Default Settings

If you enable automated backups after choosing one of the preconfigured databases during the installation, then automated backup is configured with the following default settings:

• The backup job is scheduled to run nightly at 2 a.m.

• The disk quota for the fast recovery area is 2 GB.

If you enable automated backups by using Oracle Database Configuration Assistant, either during or after the installation, then you can specify a different start time for the backup job and a different disk quota for the fast recovery area.

1.13.1 Upgrading an Oracle Database Installed on Red Hat Enterprise Linux 2.1

If you have the 8.1.7, 9.0.1, 9.2.0, or 10.1 release of Oracle Database installed on Red Hat Enterprise Linux 2.1, then you must first upgrade the operating system to Red Hat Enterprise Linux 4 (update 3) before you upgrade the database. To do this, perform any one of the following procedures:

• Upgrade the operating system. Then, upgrade the database either manually or by using Oracle Database Upgrade Assistant.

• Copy the database files. This procedure involves the following steps:

  1. Copy the database files from the computer running Red Hat Enterprise Linux 2.1 to the one running Red Hat Enterprise Linux 4.0.

  2. Re-create the control files on the computer running Red Hat Enterprise Linux 4.0.

  3. Manually upgrade the database.

  Note:

  You cannot use Oracle Database Upgrade Assistant if you follow this method. However, this method lets you easily revert to the earlier database.

• Upgrade the database by using the Export/Import utilities.

1.13.2 Automatic Storage Management Is Installed with Oracle Grid Infrastructure

In previous releases, Oracle Automatic Storage Management (ASM) was installed as part of the Oracle Database installation. With Oracle Database 11g Release 2 (11.2), Automatic Storage Management is part of an Oracle grid infrastructure installation, either for a cluster, or for a standalone server.

If you want to upgrade an existing Automatic Storage Management installation, then you must upgrade Automatic Storage Management by running an Oracle grid infrastructure upgrade. If you do not have Automatic Storage Management installed and you want to use Automatic Storage Management as your storage option, then you must complete an Oracle grid infrastructure installation before you start your Oracle Database installation.

1.13.3 Daylight Savings Time Upgrade

Refer to "Daylight Savings Time Upgrade of Timestamp with Timezone Data Type" for information about Daylight Savings Time Upgrade.