1 Overview of Oracle Database Installation

1.3.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 Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at:

https://support.oracle.com/

You must register online before using My Oracle Support. After logging in, click Certifications from the menu options. On the Certifications page, use the Certification Search options to search by Product, Release, and Platform. You can also search using the Quick Link options such as Classic Certify & Product Roadmap, Product Availability, and Lifetime Support.

1.3.2 Multiple Oracle Homes Support

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

1.3.3 Oracle Grid Infrastructure for a Standalone Server

The Oracle 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 Oracle Grid Infrastructure home. On a single-instance database, the Oracle Grid Infrastructure home includes Oracle Restart and Oracle Automatic Storage Management (Oracle ASM) software.

To use Oracle ASM or Oracle Restart, you must first install Oracle Grid Infrastructure for a standalone server before you install and create the database. Otherwise, you must manually register the database with Oracle Restart.

1.3.4 Oracle Cluster Synchronization Services

When you install Oracle Grid Infrastructure for a standalone server, Oracle Universal Installer (OUI) configures the single-node version of Oracle Cluster Synchronization Services (CSS). Specifically, CSS is a daemon process that is configured by the root.sh script.

The CSS service is required to enable synchronization between an Oracle ASM instance and the database instances that rely on it for database file storage. Because the service must be running before an Oracle ASM instance or database instance starts, it is configured to start automatically by Oracle Restart before the Oracle ASM instance is started. It must be running if an Oracle database is using Oracle ASM for database file storage.

For single-instance installations, the CSS daemon is installed-in and runs from the Oracle Grid Infrastructure home which is the same home that runs Oracle ASM.

1.3.5 Installing Oracle Database Vault in an Oracle Data Guard Environment

If you plan to use Oracle Data Guard with Oracle Database Vault, then see My Oracle Support note 754065.1 at:

https://support.oracle.com/

1.3.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 Oracle 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.4.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 Database in a production data center. This option allows for more advanced configuration options. Advanced configuration options available with this option include Oracle RAC, Oracle ASM, backup and recovery configuration, integration with Oracle 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 to quickly install Oracle Database. This installation type requires minimal user input. OUI 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 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 about Oracle database installation

1.4.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:

• 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, see 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

See 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

  Install the database using Oracle Universal Installer and start Oracle Database Configuration Assistant from the Oracle home. Oracle Database Configuration Assistant runs 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 use 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 did not create a database during the installation, then you can use Oracle Database Configuration Assistant to create a database after you install the software. For more information about using Oracle Database Configuration Assistant to create a database after installation, see "Creating and Managing a Database with DBCA" in Oracle Database 2 Day DBA.

1.8.1 File System

If you use 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 be separate from the file systems used by the operating system or the Oracle software. The file system 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 many disks.

• 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 have to specify multiple file system mount points for the 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 improves performance.

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

  See Also:

  • "General Configuration Guidelines for NAS Devices" for NAS device certification information

  • "Direct NFS Client"

If you use the Advanced database creation option, then you can also 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 Oracle Automatic Storage Management

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

Oracle ASM 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 Oracle ASM from Oracle Database 11g Release 2 (11.2) or later. Oracle ASM is installed as part of the Oracle Grid Infrastructure installation. If you plan to use Oracle ASM, then you must install Oracle Grid Infrastructure before you install and create the database. If you want to upgrade an existing Oracle ASM installation, then you must upgrade Oracle ASM by running an Oracle Grid Infrastructure upgrade.

Oracle ASM manages the storage of all database files, such as redo logs, control files, and data pump export files.

Oracle ASM can manage the Oracle Database executable binary files and any other non-database files by creating a file system with Oracle Automatic Storage Management Cluster File System. Although Oracle Automatic Storage Management Cluster File System is cluster-aware, it also works as a file system on a single-instance database.

At a high level, implementing Oracle ASM involves allocating partitioned disks for Oracle Database with preferences for striping and mirroring. Oracle ASM 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 Oracle ASM and the database instance is handled by CSS.

The following are components of an Oracle ASM installation:

• Oracle Automatic Storage Management Disk Groups

• Oracle Automatic Storage Management Instance

Oracle Automatic Storage Management Disk Groups

A disk group is a set of disk devices that Oracle ASM 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 a partition on a physical disk. In most cases, disk groups consist of one or more individual physical disks. To enable Oracle ASM to balance input/output operations 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 Oracle ASM disk group templates. When you create a disk group, Oracle ASM 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 both normal and high redundancy disk groups is set to three-way mirroring. Other files are configured with two-way mirroring for normal redundancy, or three-way mirroring when configured for high redundancy. 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. See Oracle Automatic Storage Management Administrator's Guide for more information.

Oracle ASM 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, Oracle ASM rebalances the files across the disk group. You can create multiple disk groups to do 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, Oracle ASM can distribute data among the devices in the disk group to minimize the risk of data loss caused by component failures.

Oracle Automatic Storage Management Instance

The Oracle ASM instance is a special Oracle instance that manages Oracle ASM disk groups. The Oracle ASM instance and the ASMSNMP account are created and started, if necessary, when you install Oracle Grid Infrastructure. Oracle Enterprise Manager uses this account to monitor Oracle ASM instances to retrieve data from Oracle ASM-related data dictionary views. The ASMSNMP account status is set to OPEN upon creation, and it is granted the SYSDBA privilege.

Oracle recommends that you have the Oracle ASM instance in its own Oracle home. Oracle also recommends that you run this instance before you start a database instance that uses Oracle ASM.

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

1.9.1 Management Options for Preconfigured Databases

When you create a preconfigured database during the installation, you must select the Oracle Enterprise Manager interface 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 Oracle 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 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 configure Database Control to manage the database.

1.9.2 Management Options for Custom Databases

Install the database using Oracle Universal Installer and start Oracle Database Configuration Assistant from the Oracle home. Oracle Database Configuration Assistant runs in interactive mode. Using a screen in Oracle Database Configuration Assistant, you can specify the Oracle Enterprise Manager interface to use to manage the database. You can also choose not to configure the database with Oracle Enterprise Manager.

Oracle recommends that you configure the database to use Oracle Enterprise Manager during installation. However, if you do not configure the database to use Oracle 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 use either a file system directory or an Oracle ASM 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. See "Oracle Base Directory" for more information on Oracle base.

  • 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 Oracle ASM 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 a preconfigured database during the installation, then automated backup is configured with the following default settings:

• The backup job is scheduled to run every morning at 2.00 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 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 7) before you upgrade the database. To upgrade the operating system, perform 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:

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

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

  3. Manually upgrade the database.

  Note:

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

• You can also upgrade the database by using the Export/Import utilities.

1.13.2 Oracle ASM Installed with Oracle Grid Infrastructure

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

If you want to upgrade an existing Oracle ASM installation, then you must upgrade Oracle ASM by running an Oracle Grid Infrastructure upgrade. If you do not have Oracle ASM installed and you want to use Oracle ASM as your storage option, then you must complete an Oracle Grid Infrastructure installation before you start your Oracle Database installation.

1.13.3 Daylight Saving Time Upgrade

See "Daylight Saving Time Upgrade of Timestamp with Timezone Data Type" for information about Daylight Saving Time Upgrade.

1.13.4 Upgrading an Oracle Database in the Same Oracle Home

See the Oracle Database Upgrade Guide for more information about performing an in-place Oracle Database upgrade.