1 Overview of Oracle Database Installation

1.2.1 Completing a Default Linux Installation

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

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

1.2.2 About the Oracle Validated Configuration RPM

If your 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 RPM, available from the Unbreakable Linux Network (ULN).

When it is installed, the Oracle Validated Configuration RPM 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 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/linux

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.2.3 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 your server with Unbreakable Linux Network (ULN). By default, you are registered for the Enterprise Linux Latest channel for your 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 your installation of Linux (for example: "Oracle Software for Enterprise Linux 4 (x86_64)."

6. Click Subscribe.

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

   # up2date --nox --show-channels
   
   

   You should see output indicating 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 root, and install the Oracle Validated Configurations Setup RPM with up2date, using the following command:

   # up2date --install oracle-validated
   
   

1.3.1 Oracle Application Express

Oracle Application Express is a tool for development and deployment of Web applications for an Oracle Database. It improves the productivity, security, reliability, and performance of Oracle Database. With little programming or scripting on a Web browser, enables you to build reporting and data entry applications on existing tables, views, or data imported from spreadsheets.

1.3.2 Oracle Warehouse Builder

Oracle Warehouse Builder is the only enterprise business intelligence integration design tool that manages the full life-cycle of data and metadata for the Oracle Database. It provides an easy to use graphical environment to rapidly design, deploy, and manage business intelligence systems.

With the Standard and Enterprise Editions of Oracle Database, you can use Oracle Warehouse Builder which enables you to integrate and transform data into high quality information. When you install the Standard Edition or Enterprise Edition of Oracle Database, that installation provides you with components necessary for Oracle Warehouse Builder, including an unpopulated schema, OWB_SYS. Unlock the OWB_SYS schema and install the Oracle Warehouse Builder software on a client computer, as described in Oracle Warehouse Builder Installation and Administration Guide.

1.3.3 Oracle Configuration Manager

Oracle Configuration Manager is a utility that can be optionally configured when installing the Oracle Database. Oracle Configuration Manager is used to collect and upload the configuration information to the Oracle configuration repository.

The following are some of the benefits of Oracle Configuration Manager:

• Reduces time for resolution of support issues

• Provides pro-active problem avoidance

• Improves access to best practices and the Oracle knowledge base

• Improves understanding of customer's business needs and provides consistent responses and services

Oracle Configuration Manager can now be installed in two modes:

• Connected Mode: This mode is recommended if your server has direct connection to the Internet or connection through a proxy server. In this mode, configuration data is automatically collected and uploaded to the Oracle system. Updates to Oracle Configuration Manager occur automatically.

• Disconnected Mode: This mode is recommended if your server does not have a connection to Internet. In this mode, you can collect configuration data manually by using the emCCR collect command. When you run this command, the collected configuration data is stored in the $ORACLE_HOME/ccr/state/upload/ocmconfig.jar file. You can then upload this file to the Oracle server.

1.3.4 Oracle SQL Developer

Oracle SQL Developer is a graphical version of SQL*Plus that gives database developers a convenient way to perform basic tasks. Following are the functions you can perform with Oracle SQL Developer:

• Browse, create, edit, and delete (drop) database objects

• Run SQL statements and scripts

• Create, edit, compile and debug PL/SQL code

• Create, edit and update data

• Import data, export data and data definition language

• View and create reports

• View metadata and data of Microsoft Access, Microsoft SQL Server, and MySQL databases

1.3.5 Oracle Database Vault

Oracle Database Vault enables you to secure business data in ways that were not possible before. Database Vault uses a multifactored and multilayered approach to implementing database security. Before you plan the upgrade process, become familiar with the features of Oracle Database Vault. The Oracle Database Vault Administrator's Guide discusses the basic features of Oracle Database Vault.

1.4.1 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 OracleMetaLink Web site for the most up-to-date list of certified hardware platforms and operating system versions. The OracleMetaLink Web site is available at the following URL:

https://metalink.oracle.com

If you do not have a current Oracle Support Services contract, then you can access the same information at the following Web site:

http://www.oracle.com/technology/support/metalink/content.html

1.4.2 Multiple Oracle Homes Support

This product supports multiple Oracle homes. This means that 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 Oracle Cluster Synchronization Services

The first time you install Oracle Database 11g and choose Automatic Storage Management as the storage option on a system, the installation configures and starts a single-node version of the Oracle Cluster Synchronization Services (CSS) daemon. The CSS daemon is required to enable synchronization between an Automatic Storage Management instance and the database instances that rely on it for database file storage. By default, Oracle Universal Installer does not configure Oracle Cluster Synchronization Services. Oracle Universal Installer configures these services only if you choose Automatic Storage Management as a storage or recovery option. Because it must be running before any Automatic Storage Management instance or database instance starts, it is configured to start automatically when the system boots.

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

If you have installed Oracle Cluster Synchronization Services from the same Oracle home as Oracle Database, then use caution when removing Oracle Database 11g software from the system. Before you remove an Oracle home directory that contains Oracle Database 11g, you must either delete the CSS daemon configuration, or if necessary, reconfigure the CSS daemon to run from another Oracle home directory.

1.4.4 Using Network Attached Storage or NFS File Systems

Oracle Database 11g must be able to verify that writes to a disk are completed successfully. NFS file systems, including file systems on NAS devices, may not be able to guarantee that writes to a disk are completed successfully, and this may lead to possible data file corruption. Oracle recommends that you do not store files on NFS mounted file systems unless the storage vendor and storage device are listed in the Oracle Storage Compatibility Program list. This list is available from the following Web site:

http://www.oracle.com/technology/deploy/availability/htdocs/oscp.html

If a storage device is supported, then you can use it to store Oracle software files, Oracle database files, or both.

1.4.5 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 Methods

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.

With Oracle Database 11g release 1 (11.1) on Linux, Oracle Universal Installer provides two interactive methods that you can use to install Oracle Database:

• Basic: Select this installation method if you want to quickly install Oracle Database. This installation method 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 method.

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

  • Install Oracle Real Application Clusters

  • Upgrade an existing database

  • 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

  • Configure Automatic Storage Management for database storage

  • Specify different passwords for administrative schemas

  • Configure automated backups or Oracle Enterprise Manager notifications

  • Configure Oracle Configuration Manager

  • Perform a custom software installation, or choose a different database configuration

    The Available Product Components installation screen automatically selects the components most customers need in their Oracle Database installation. It also lists several components that are not selected by default, but which you may want to include. To find the listing of available components, select Advanced, and then in the Installation Type screen, select Custom.

    See Also:

    "Reviewing 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 need to 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. None of the Oracle Universal Installer screens are displayed.

• Suppressed Mode: Oracle Universal Installer runs in suppressed mode if you do not specify all required information in the response file. Oracle Universal Installer displays only the screens that prompt for the information that you did not specify.

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 Database Configuration Assistant for a description of these preconfigured database types.

1.7.2 Installation Choices that Affect Database Creation

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

• Noninteractive mode

  If you choose either the Enterprise Edition or Standard Edition installation type, 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 Database Configuration Assistant in noninteractive 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 the Custom installation type or choose the Advanced database configuration option, then Oracle Universal Installer does not prompt you for database information. Instead, it installs the software and then runs Database Configuration Assistant in interactive mode. Using the screens in Database Configuration Assistant, you can either modify one of the preconfigured database types or create a custom database and specify precisely how you want to configure it.

  Note:

  If you choose this method to create a database, then click Help on any of the 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 Database Configuration Assistant to create one after you have installed the software. For more information about using 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 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 described in Appendix D 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

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

  See Also:

  The "Using Network Attached Storage or NFS File Systems " for more information about certified NAS and NFS devices

If you choose the Custom installation type or 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 need to 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 1 (11.1) databases can use Automatic Storage Management from Oracle Database 10g release 1 (10.1). If a site has multiple single-instance databases, then you can use Oracle Clusterware to consolidate multiple islands of databases into a single clustered pool of storage managed by Automatic Storage Management. Automatic Storage Management manages the storage of all database files, such as redo logs, control files, data pump export files, and so on. However, it does not manage Oracle Database executable binary files.

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 Oracle Cluster Synchronization Services (CSS).

The following are components of an Automatic Storage Management installation:

• Automatic Storage Management Disk Groups

• Automatic Storage Management Instance

• General Steps for Installing Automatic Storage Management

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 I/O 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; that is, 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 Database 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 manages Automatic Storage Management disk groups. This instance must be running before you can start a database instance that uses Automatic Storage Management. When you choose Automatic Storage Management as a database storage mechanism, this instance is created and started, if necessary. For a single-instance Oracle Database installation, you only need one Automatic Storage Management instance, regardless of the number of database instances on the system. The Automatic Storage Management instance on any node in a single cluster can handle any combination of disk group types.

General Steps for Installing Automatic Storage Management

To install Automatic Storage Management, you use Oracle Universal Installer. This installation guide provides the following general steps for installing Automatic Storage Management:

1. Determine the disk requirements of the site and, if necessary, create one or more disk partitions for Automatic Storage Management.

   "Preparing Disk Groups for an Automatic Storage Management Installation" provides guidelines on how to determine the disk requirements of the site.

2. Run Oracle Universal Installer to install and create an Automatic Storage Management instance and to create Automatic Storage Management disk groups.

   "Step 1: Reviewing Automatic Storage Management Installation Considerations" provides guidelines on where to install Automatic Storage Management and other installation considerations.

   "Step 2: Creating the Automatic Storage Management Instance and Disk Groups" describes how to create an Automatic Storage Management instance and disk groups.

   After you create an Automatic Storage Management instance and its associated disk groups, subsequent databases that you create will be able to use Automatic Storage Management for file storage management. If you have databases that were created before you installed Automatic Storage Management, then you can migrate them to Automatic Storage Management by using the Enterprise Manager Migrate Database Wizard. This wizard is available in Enterprise Manager Grid Control or Database Control. Alternatively, you can use Oracle Database Recovery Manager (RMAN) to perform the migration.

3. To create an Oracle Database with Automatic Storage Management refer "Step 3: Installing Oracle Database to Use with Automatic Storage Management"

4. Test the Automatic Storage Management installation.

   "Step 3: Installing Oracle Database to Use with Automatic Storage Management" provides a simple test you can try to check that the Automatic Storage Management installation was successful. "Managing Automatic Storage Management" explains how to start and access Automatic Storage Management and which Oracle Database tools you can use to manage it.

1.8.3 Raw Devices

Raw devices are disk partitions or logical volumes that have not been formatted with a file system. Raw devices are not offered as a storage option when creating a database as a part of a new Oracle Database 11g installation. However, upgrading the existing version of raw devices are supported. Raw device is available as a storage option when you run Database Configuration Assistant from the following location:

$ORACLE_HOME/bin/dbca

When you use raw devices for database file storage, Oracle writes data directly to the partition or volume, bypassing the operating system file system layer. However, since raw devices can be difficult to create and administer, and because the performance gains over modern file systems are minimal, Oracle recommends that you choose Automatic Storage Management or file system storage in preference to raw devices.

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 Oracle Management 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 need to 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 or choose to create a database during a Custom installation, then Oracle Universal Installer runs Database Configuration Assistant in interactive mode. Using a screen in 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 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 of the 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 it provides 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 an on disk storage area called the flash 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 flash recovery area

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

  • Default Flash recovery area: $ORACLE_BASE/flash_recovery_area

  • Default data file location: $ORACLE_BASE/oradata

  The default disk quota configured for the flash 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 flash 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 OSDBA group, typically dba). The Oracle software owner user (typically oracle) that you use to install the software is a suitable choice for this user. Chapter 2 describes the requirements for the OSDBA group and Oracle software owner user and describes how to create them.

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 flash recovery area is 2 GB.

If you enable automated backups by using 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 flash recovery area.

1.12.1 AL24UTFFSS Character Set

Before you upgrade an existing database that uses the AL24UTFFSS character set, you must upgrade the database character set to UTF8. Oracle recommends that you use the Character Set Scanner (csscan) utility for data analysis before attempting to upgrade the existing database character set.

The Character Set Scanner utility checks all character data in the database and tests for the effects of, and problems with, changing the character set encoding. Before running the Character Set Scanner utility, set the shared library path environment variable for the platform to include the $ORACLE_HOME/lib directory. The shared library path environment path that you need to set is LD_LIBRARY_PATH.

1.12.2 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 3 (update 4) 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. The detailed information on preserving database environment while upgrading the operating system is available at the following URL:

  http://www.oracle.com/technology/tech/linux/pdf/rhel_23_upgrade.pdf

• 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 3.0.

  2. Re-create the control files on the computer running Red Hat Enterprise Linux 3.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.