This chapter describes the different types of Oracle Database installations that you can perform and issues that you should consider before installing the software. It includes information about the following topics:
The Oracle Database installation process consists of five phases:
Read the release notes: Read Oracle Database Release Notes for HP OpenVMS Itanium before you begin the installation. The release notes are available with the platform-specific documentation. The latest version of the release notes is available at
Planning the installation: This chapter describes the Oracle products that you can install and issues that you must consider before starting the installation.
Completing preinstallation tasks: Chapter 2 describes preinstallation tasks that you must complete before installing the product.
Chapter 3 describes how to use Oracle Universal Installer to install Oracle Database.
If you want to install client tools, applications, and client interfaces that are not included on the Oracle Database DVD, then see the documentation for those products.
Chapter 6 describes how to remove Oracle Database.
Appendix B provides information on performing noninteractive (silent) installations, which you may want to use if you must perform multiple installations of Oracle Database.
Appendix C describes how to install, configure, and run the Oracle Enterprise Manager Agent.
Appendix F provides troubleshooting advice in case you encounter problems with the installation.
Appendix G describes how to install and configure Apache Server.
Completing postinstallation tasks:
Chapter 4 describes recommended and required postinstallation tasks.
Get started using Oracle Database: Chapter 5 describes how to check the contents of the installed Oracle Database, how to start various tools, and how to locate various files. Appendix D explains how to manage Oracle Database port numbers.
The following changes and enhancements are unique to this release of Oracle Database:
In earlier releases, when one of the background processes terminated abruptly with an access violation, no useful information was readily available regarding the cause for termination. For troubleshooting, certain actions needed to be taken, and the failure needed to be reproduced. Starting with this release, by default, an image dump is created when a background process terminates abruptly. If you do not want an Oracle background process to generate image dump files, then create an HP OpenVMS system logical for that background process as follows:
$ DEFINE/SYSTEM ORA_sid_bgprocess_DMP FALSE
In the preceding command, the value of
bgprocess can be PMON, SMON, DBW0, and so on. The value of
sid should be set to the required system Identifier or instance name.
Start the instance and open the database. For example:
Note:HP OpenVMS logicals must be defined before starting the instance.
$ DEFINE/SYSTEM ORA_PROD_LMD0_DMP FALSE $ SQLPLUS/NOLOG SQL> CONNECT SYS / AS SYSDBA Enter password: SQL> STARTUP
On-Disk Structure Level 5 (ODS-5) format enables HP OpenVMS to support Linux and Unix style file name formats. Longer file names, additional character support, and the ability to have lowercase and mixed-case file names are some of the features supported on ODS-5 disks.
Beginning with OpenVMS 11gR2 Oracle Database, it is required to use the ODS-5 format for all disks involved with the installation. This includes the login, download, install target, temporary install, database, and archive/redo logs devices.
Note:Oracle recommends that you read HP OpenVMS Guide to Extended File Specifications before changing the structure of any disk. This guide describes ODS-2 and ODS-5 formats in more detail and provides important information that you must follow.
The disks on which the Oracle code tree resides must be formatted in Files-11 ODS-5 format. This is the disk to which the HP OpenVMS logicals
ORACLE_HOME point. The directory that is referenced by these logicals is the parent directory for all Oracle Database software, such as Apache, CTX, INSTALL, NETCONFIG, RDBMS, and UTIL. With HP OpenVMS 11g Release 2 (11.2), the only format that will perform as expected is ODS-5.
See Also:Oracle Note 2012766.1 on My Oracle Support.
Alternatively, use the search function and search for ODS-5 for more information.
You must observe the following precautions:
Do not change the format of any HP OpenVMS disk without first making a backup of the disk.
Conversion from ODS-2 to ODS-5 does not require you to restore files.
Conversion from ODS-5 to ODS-2 requires you to restore files.
Note:Contact Hewlett-Packard for more information about reverting to ODS-2 format from ODS-5 format.
$ SHOW DEVICE/FULL device_name
Volume Status: line of the output displays the current ODS level. The default when initializing disks is ODS-2.
Create at least one HP OpenVMS backup of the disk.
Use the following command:
$ SET VOLUME/STRUCTURE_LEVEL=5 $2$DKC0:
INITIALIZE/STRUCTURE=5 $2$DKC100: TESTVOL
The installation directory structure of Oracle Database closely resembles that of the installation directory structure of Oracle Database on UNIX systems. By making the HP OpenVMS installation directory structure similar to that of other platforms, a more consistent and predictable layout is followed across platforms. This enables database administrators (DBAs) from other platforms to quickly become familiar with Oracle Database for this platform.
You can choose one of the following installation types when installing Oracle Database:
Enterprise Edition: Installs licensable Oracle Database options and database configuration and management tools. It also installs products most commonly used for data warehousing and transaction processing.
Standard Edition: Designed for department-level or workgroup-level applications and for small-sized or medium-sized enterprises. It provides core relational database options and management services.
Oracle Enterprise Manager Concepts and Oracle Enterprise Manager Grid Control Installation and Basic Configuration for more information about Oracle Enterprise Manager 11g Release 2 (11.2).
Oracle Database Licensing Information guide for more information about the features available with each Oracle Database edition and information about licensing.
Database Configuration Assistant (DBCA) enables you to copy a preconfigured Oracle Database, or to create a fully customized database to match the selected environment and database configuration. In order to run DBCA, type DBCA at the DCL prompt.
When installing Oracle Database software using any database configuration option other than Custom and Software Only, Oracle Universal Installer prompts for a global database name and system identifier (SID). After Oracle Database installation is complete, Database Configuration Assistant uses this information to create a database.
If you select this option with an Enterprise Edition installation, then Database Configuration Assistant creates a preconfigured, ready-to-use, multipurpose database with the following features:
If you select this option, then Database Configuration Assistant creates a preconfigured, ready-to-use OLTP database.
If you select this option, then Database Configuration Assistant creates a database that is fully enabled for data warehousing applications.
If you select this option, then Database Configuration Assistant guides you in creating a fully customized database.
Automatic or Manual
Automatic or manual configuration options, Oracle Text components, and advanced replication.
Select this option only if you are experienced with advanced database creation procedures. You must customize some or all of the following settings or parameters:
Data, control, and redo log file settings.
Tablespace and extent sizes.
Database memory parameters.
Archiving modes, formats, and destinations.
Trace file destinations.
Character set values.
For HP OpenVMS 11g Release 2 (11.2), "Software Only" is the method of install. Once the install is complete, DBCA can be run from the command line to create a database.
Section B.5, "Running Database Configuration Assistant in Noninteractive or Silent Mode" for more information about running Database Configuration Assistant from the command line.
Oracle Database Globalization Support Guide for more information about database character sets.
During the installation, you can choose whether you want to create an Oracle Database as part of the installation. The Select Configuration Option screen provides the following options:
Create a database
Install database Software only
Specify ASM SYS Password: [ ] Confirm ASM SYS Password: [ ]
Install database Software only
If you decide not to create an Oracle Database during the installation, then you can use the Database Configuration Assistant (DBCA) to create one after you have installed the software. Choose the third option from this screen as ASM is not supported on OpenVMS platforms.
See Also:Oracle Database 2 Day DBA for more information about using Database Configuration Assistant (DBCA) to create a database after installation
If you choose to create an Oracle Database, Oracle Universal Installer uses the Database Configuration Assistant to create it. You can choose to create one of the preconfigured database types, which are designed for different types of applications, modify one of the preconfigured database types, or create a customized database to suit your requirements.
This section describes the following database configuration options:
Oracle provides the following preconfigured database types that you can create or customize during the installation:
A starter database designed for general purpose usage. Users of this database type perform a variety of database tasks, ranging from simple transactions to complex queries. Select this database environment for general purpose use.
A starter database optimized for transaction-heavy applications. Users of this database type perform large numbers of concurrent transactions, in which each transaction is a relatively simple operation that is processing a small amount of data.
Billing databases, such as those commonly found on Internet commerce websites, are the most common example of this database configuration. These databases are also known as Online Transaction Processing (OLTP) databases.
A starter database optimized for data warehousing applications. Users of this database type typically perform reporting and data analysis tasks, often on data uploaded from operational systems and databases.
This option allows you to customize the configuration of your starter database. This option enables you to create a customized database configuration that meets specialized requirements. Select this option only if you are prepared to provide detailed product and database environment choices. Selecting this option requires a longer installation session than choosing a preconfigured database.
Oracle recommends that you install at least one preconfigured database to serve as a template for database configuration.
Oracle Universal Installer runs Database Configuration Assistant in one of two modes, depending on the choices that you make during the installation:
If you choose the Enterprise Edition installation type, then choose 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.
If you choose the Custom installation type, 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 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.
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.
See Also:Oracle Database 2 Day DBA for more information about using Database Configuration Assistant to create a database after installation
The current release of Oracle Database provides new options for simplifying database administration tasks. These include:
If you choose to create a database during the installation, then you can specify the File System option as the storage option for database files.
Oracle Automatic Storage Management (Oracle ASM) is not supported as a storage option for HP OpenVMS. If you choose the File System option, then Database Configuration Assistant creates the database files in a directory on a device mounted on the system. Oracle recommends that the device that you select be separate from the devices that the operating system or by Oracle products use. The device that you select can be any of the following:
A standalone device
A device on a logical volume manager (LVM) volume or RAID device
If you are using multiple disks in an logical volume manager (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 device for database storage.
See Also:Oracle Database Administrator's Guide
If you choose to use Oracle Enterprise Manager Grid Control during the installation, then you can enable automated database backups that use the default backup strategy recommended by Oracle.
Note:You do not have to enable automated backups during the installation. If you prefer, you can use Oracle Enterprise Manager Grid Control to configure automated backups after you install the software and create a database.
This section contains the following sections:
If you enable automated backups, then Oracle Enterprise Manager schedules a daily backup job that uses Oracle Recovery Manager (RMAN) to back up all the database files to a storage area on disk 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 have previously installed the Oracle Enterprise Manage Grid Control Agent. During database installation you must specify the following information:
The location of the flash recovery area.
You can choose a device directory or accept the default for the flash recovery area. The default disk quota configured for the flash recovery area is 2 GB.
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 have the appropriate privileges and rights required for database administrators.
See Also:Chapter 2 for information about choosing the location of the flash recovery area and determining the disk space requirements and about the requirements for the database administrator account
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, you can specify a start time for the backup job and a disk quota for the flash recovery area.
Oracle Database 2 Day DBA for information about using Oracle Enterprise Manager Grid Control to configure or customize automated backups or to recover a backed up database.
Oracle Database Backup and Recovery Basics manual or Oracle Database Backup and Recovery User's Guide for more information about defining a backup strategy and about backing up and recovering Oracle Databases.
This section contains information about the following considerations, which you must address before deciding how to install Oracle Database:
The hardware and software requirements included in this installation guide are current at the time of publishing this guide. However, because new platforms and operating system software versions may be certified after this guide is published, review the certification matrix on My Oracle Support for an updated list of certified hardware platforms and operating system versions. You can visit My Oracle Support at
This product supports multiple Oracle homes. You can install this release or earlier releases of the software more than once on the same system. For example, you may want to make an Enterprise Edition installation and a Standard Edition installation available on the same system.
You must install this product into a new Oracle home directory. You cannot install products from one release of Oracle Database into the 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, then 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.
Note:Before installing Oracle software, you must log out of any existing Oracle sessions. If you do not do this, then the new installation includes the logicals and symbols of the active Oracle sessions.
Ensure that the
LOGIN.COM file of the account that Oracle Database uses to install does not define any of the Oracle logicals or symbols, and does not run any command file that may define them. Ensure that none of the general Oracle specific logicals (typically beginning with
ORA_) are defined in the system table, except for some logicals related to mailbox devices and shared libraries. Oracle Database may not run correctly if these logicals are defined.
Note:If you install Oracle Database 11g Release 2 (11.2) on a node where other versions of Oracle Database are run, then ensure that you do not have Oracle symbols or logicals defined before installing Oracle Database 11g Release 2 (11.2). Do not run any
orauserscripts as part of the login sequence. Failure to heed this warning will result in numerous problems, including undefined symbols and overwriting of the previous code tree.
Take the following issues into consideration when installing 188.8.131.52 on a system with existing Oracle software:
Oracle Database 11g Release 2 (11.2) Enterprise Edition must be installed in a location separate from other previous Oracle Database installations.
Oracle products from earlier releases of Oracle Database, such as Release 10.2.0.x and Release 9.2.0.x, must not be linked with an Oracle Database 11g Release 2 (11.2) installation.
For more information about upgrading a previous release of Oracle Database to Oracle Database 11g Release 2 (11.2), see Oracle Database Upgrade Guide. The following sections includes additional upgrade information that you should review before upgrading an existing database.
To manually upgrade an existing database to Oracle Database 11g Release 2 (11.2) on HP OpenVMS, follow the steps in Oracle Database Upgrade Guide. In Chapter 3 of the guide, use the following steps for HP OpenVMS.
In the "Prepare the New Oracle Home" subsection of the "Upgrade the Database Manually" section, substitute
ORA_ROOT:[DBS]. Also substitute
In step 1 of the "Upgrade the Database" subsection, ignore the steps for the Windows operating system.
Set your default directory to the new Oracle home and execute the script
@ORAUSER.COM (without arguments). Then
ET DEF ORA_ROOT:[RDBMS] and execute the migrate script: To upgrade 10.2 to 11.2, enter
Enter the details prompted by the upgrade assistant.
Proceed to step 4 in the "Prepare the New Oracle Home" subsection, which involves changing to the ORA_ROOT:[RDBMS.ADMIN] directory.
If you want to use an existing non-VMS database on an HP OpenVMS Itanium system, you must upgrade the non-VMS database to 11g Release 2 (11.2) before migrating it to HP OpenVMS Itanium.
To upgrade an existing database that uses the
AL24UTFFSS character set, upgrade the database character set to
UTF8 before upgrading to Oracle Database 11g Release 2 (11.2). 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.
In this document, there are references to the term cluster file system. This term refers to the configuration in which all disks are equally accessible from all nodes on the cluster. This is the most commonly used configuration on an HP OpenVMS cluster. All references to this term should be considered as references to this configuration on an HP OpenVMS cluster.