1 Overview of Oracle Database Installation

1.3.1 Installation Differences Between Windows and UNIX Systems

If you are experienced with installing Oracle components in UNIX environments, note that many manual setup tasks required on UNIX are not required on Windows. The key differences between UNIX and Windows installations are:

• Startup and shutdown services

  With Windows, Oracle Universal Installer creates services at installation time that can be configured to automatically start the Oracle software components when the host computer starts. On Linux and UNIX systems, database or system administrators must manually configure the oratab file.

• Environment variables

  With Windows, Oracle Universal Installer sets environment variables such as PATH, ORACLE_BASE, ORACLE_HOME, and ORACLE_SID in the registry. In UNIX systems, you must manually set these environment variables.

  If you have multiple Oracle homes installed, then only the SID of the last Oracle home is set in the registry. See Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for more information about managing Oracle homes.

• Operating System Groups

  On Windows systems, Oracle Universal Installer creates the ORA_DBA, ORA_OPER, ORA_SID_DBA and ORA_SID_OPER groups, which are used for operating system authentication for Oracle instances. On Linux and UNIX systems, you must create these operating system groups manually, and they are used for granting permission to access various Oracle software resources and for operating system authentication. Windows does not use an Oracle Inventory group.

• Account for running Oracle Universal Installer

  With Windows, you log in with Administrator privileges. You do not need a separate account. On Linux and UNIX systems, you must create and use a software owner user account, and this user must belong to the Oracle Inventory group.

1.3.2 Recommended File System

Oracle strongly recommends that you install the Oracle database home (Oracle database binaries, trace files, and so on) on Oracle ACFS or NTFS; the database files themselves must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS instead of FAT32 is recommended to ensure security of these files.

1.3.3 Managing User Accounts with User Account Control

To ensure that only trusted applications run on your computer, Windows Vista, Windows Server 2008, Windows Server 2008 R2, and Windows 7 provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.

You must have Administrator privileges to run some Oracle tools, such as Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly invoke these tasks with Windows Administrator privileges. All the Oracle shortcuts that require Administrator privileges start as "Administrator" automatically when you click the shortcuts. However, if you run the above tools from a Windows command prompt, you must run them from an Administrator command prompt. OPatch does not have a shortcut and has to be run from an Administrator command prompt.

To start a command prompt window with Windows Administrator privileges:

1. On your desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the desktop.

2. Right-click the icon for the newly created shortcut, and specify "Run as administrator."

When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.

1.3.4 Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time 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. This Web site also provides compatible client and database versions, patches, and workaround information for bugs. The My Oracle Support (formerly OracleMetaLink) Web site is available at

https://support.oracle.com/

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in, click More and then select Certifications from the list. On the Certification Information page, the Certification Options list appears. Other options include Product Roadmap, Product Availability, and Lifetime Support Policy.

1.3.5 Multiple Oracle Homes Support

Oracle Database supports multiple Oracle homes. You can install this release or previous releases of the software more than once on the same system, in different Oracle home directories. This allows flexibility in deployment and maintenance of the database software. For example, it enables you to run different versions of the database simultaneously on the same system, or it enables you to upgrade specific database instances on a system without affecting other running databases. However, when you have installed multiple Oracle Homes on a single system, there is also some added complexity introduced that you must consider allowing these Oracle Homes to coexist.

You must install this product into a new Oracle home directory. You cannot install products from one release of Oracle Database into an Oracle home directory of a different release. For example, you cannot install Oracle Database 11g Release 2 (11.2) software into an existing Oracle9i Oracle home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation fails.

You can install this release more than once on the same system if each installation is installed in a separate Oracle home directory.

1.3.6 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 (Oracle 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.3.7 Oracle Cluster Synchronization Services

When you install the grid infrastructure for a standalone server, it configures the single-node version of the 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.

1.3.8 Oracle Universal Installer Overview

Oracle Universal Installer is a Java-based graphical user interface (GUI) tool that enables you to install Oracle software. Oracle Universal Installer provides the following capabilities:

• Component and suite installations

• Globalization support

• Distributed installation support

• Unattended silent installations using response files

• Removal of installed components

• Multiple Oracle homes support

Oracle Universal Installer can run a silent or response file installation of Oracle software using response files. See Appendix C, "Installing and Configuring Oracle Database Using Response Files" for more information.

You must use the Oracle Universal Installer 11g to install components into an Oracle Database 11g Release 2 (11.2) Oracle home directory.

Oracle Universal Installer automatically installs the Oracle version of the Java Runtime Environment (JRE). This version is required to run Oracle Universal Installer and several Oracle assistants. Do not modify the JRE, unless doing so with a patch provided by My Oracle Support (formerly OracleMetaLink). Visit the following site to find Oracle patches to download:

https://support.oracle.com/

When Oracle Universal Installer runs, it creates an dbhome_n directory, which keeps track of the components you are installing. Do not modify the contents of this directory. By default, this directory is located at the same directory level as ORACLE_HOME.

1.3.9 Oracle Base Directory

If you install Oracle Database 11g Release 2 (11.2) on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, then one or more Oracle base directories already exist. In the latter case, Oracle Universal Installer offers you a choice of Oracle base directories to install Oracle Database.

In a default Windows installation, the Oracle base directory appears as follows:

DRIVE_LETTER:\app\username

1.3.10 Oracle Home Directory

This section covers the following topics:

• Contents of the Oracle Home Environment

• Multiple Oracle Home Components

DRIVE_LETTER:\app\username\product\11.2.0\dbhome_1

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

https://support.oracle.com/

1.3.12 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 of the required information to install the Oracle Database software and optionally create a database. There are two options that you can use to install Oracle Database:

• 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 get up and running with the database quickly.

• 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 using 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 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 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

    • 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"

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.

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, see Appendix C.

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 the Enterprise Edition, Standard Edition, or Personal Edition as the 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 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 choose this method to create a database, click the Help button 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, you can use Oracle Database Configuration Assistant to create one after you have installed the software.

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 on your 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 follow the Optimal Flexible Architecture (OFA) recommendations and distribute the database files over multiple disks.

• A file system on a logical volume manager (LVM) 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 must not specify multiple file system mounting points 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 about 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.

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

To use Automatic Storage Management, you allocate partitioned disks to Oracle with preferences for striping and mirroring. Automatic Storage Management manages the disk space for you, thus eliminating 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 Oracle Cluster Synchronization Services (CSS).

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 manage the database. The following options are available:

• Use Grid Control for central database management.

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

  If an Oracle Management Agent is not installed, you must use Database Control to manage the database. However, if you install Oracle Management Agent after you install Oracle Database, 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 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 manage the database. Alternatively, you can 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, 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, which is installed by default with Oracle Database, provides a Web-based user interface that you can use to monitor, administer, and maintain an Oracle database. You can use it to perform all of your 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

• Automatic notification of security alerts

• Ability to apply patches

• Session and SQL-related performance information

• Space usage metrics

1.10.1 Enabling Automated Backups

If you enable automated backups, Oracle Enterprise Manager schedules a daily backup job that uses Oracle Database Recovery Manager (RMAN) to back up all of the database files to an on-disk storage area called the fast recovery area. The size of the fast recovery area is determined by the size of the database you must back up. 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. If you want to create an online backup, you must run the backup job in ARCHIVELOG mode.

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 Automatic Storage Management disk group for the fast recovery area. 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 Windows 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, 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, you can specify a different start time for the backup job and a different disk quota for the fast recovery area.

1.12.1 Automatic Storage Management Is Installed with Oracle Grid Infrastructure

In previous releases, Oracle Automatic Storage Management (Oracle 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.12.2 Daylight Savings Time Upgrade

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

1.12.3 Policies for Client and Application Software Installations

If you upgrade your Oracle Database to 11g Release 2 (11.2), then Oracle recommends that you upgrade the client software to Oracle Database 11g Release 2 (11.2) as well. Keeping the server and client software at the same release number ensures maximum stability for your applications. In addition, the latest Oracle client software may provide added functionality and performance enhancements that were not available with previous releases.

1.12.4 Downgrading a Database

Steps to downgrade a database, including steps to change the word size, are covered in Oracle Database Upgrade Guide.