Oracle® Database Installation Guide
10g Release 1 (10.1) for hp OpenVMS Alpha
Part No. B13681-01
This chapter describes the different types of Oracle Database installations that you can perform, as well as issues that you should consider before installing the software.
The following topics are discussed in this chapter:
The Oracle Database installation process consists of five phases:
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.
Installing the software
Chapter 3 describes how to use Oracle Universal Installer to install the product.
Completing postinstallation tasks
Chapter 4 describes recommended and required postinstallation tasks.
Installing the client software
If you want to install client tools, applications, and client interfaces that are not included on the Oracle Database CD-ROM, then refer to the documentation for those products.
To make full use of the latest OpenVMS CPU and compiler optimizations in Oracle software products, Oracle Database 10g release 1 (10.1) and associated Oracle products that are based on Oracle Database 10g requires an OpenVMS system with an EV56 or later generation CPU.
Note:Oracle Database 10g Release 1 (10.1.0.3.0) is not certified on and is, therefore, not supported on Alpha chip sets earlier than EV56.
See Also:Note 181307.1 on OracleMetaLink for a list of affected models and for instructions about how to identify the CPU model number
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 OpenVMS system logical for that background process as follows:
$ define/system ORA_
bg process_DMP FALSE
In the preceding command, the value of
bg process can be pmon, lmd0, lms0, and so on. The value of
sid should be set to the required SID or instance name.
Start the instance, and open the database. For example:
Note:OpenVMS logicals must be defined prior to starting the instance.
$ define/system ORA_PROD_LMD0_DMP FALSE $ sqlplus/nolog SQL> connect / as sysdba SQL> startup
On-Disk Structure Level 5 (ODS-5) format enables OpenVMS to support Microsoft Windows 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.
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 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. The disks on which Oracle Database files reside can be formatted as either ODS-2 or ODS-5.
See Also:Oracle Note 286895.1 on OracleMetaLink
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 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.
Checking Disk 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.
Changing Disk Format
Create at least one OpenVMS backup of the disk.
Use the following command:
$ SET VOLUME/STRUCTURE_LEVEL=5 $2$DKC100:
Formatting a New Disk
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 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.
Support for the following Oracle Database initialization paramenters found in earlier releases has been removed starting with this release of Oracle Database.
You can select 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 that are commonly used for data warehousing and transaction processing.
During the installation, you can specify that you want to create an Oracle Database as part of the installation. If you choose to create an Oracle Database, Oracle Universal Installer uses the Database Configuration Assistant (DBCA) 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 contains the following topics:
Depending on your requirements, you may want to install a specific database type or install other Oracle products without installing a database. This section provides information about the following database options:
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.
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 Web sites, are the most common example of this database configuration. These databases are also known as Online Transaction Processing (OLTP) databases.
This option enables you to create a customized database configuration of Oracle products that meets specialized requirements. Select this option only if you are prepared to provide detailed product and database environment choices. Processing this option involves a longer installation session than choosing a preconfigured database.
Depending on the choices that you make during the installation, Oracle Universal Installer runs DBCA in one of two modes:
If you select 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 DBCA 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 select the Custom installation type, then Oracle Universal Installer does not prompt you for database information. Instead, it installs the software and then runs DBCA in interactive mode. By using the screens in DBCA, 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 select this method to create a database, then refer to the DBCA online Help 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 DBCA to create one after you have installed the software.
See Also:Oracle Database 2 Day DBA (B10742-03) for more information about using DBCA to create a database after installation
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. It starts automatically (unless you selected software only) after Oracle Database software has been installed during an installation session.
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, DBCA uses this information to create a database.
If you select this option with an Enterprise Edition installation, then DBCA creates a preconfigured, ready-to-use, multipurpose database with the following features:
If you select this option, then DBCA creates a preconfigured, ready-to-use OLTP database.
If you select this option, then DBCA creates a database that is fully enabled for data warehousing applications.
If you select this option, then DBCA 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 will need to 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
If you select this option, then Oracle Universal Installer only installs Oracle Database software. DBCA does not start after installation, and no preconfigured database is installed.
If a choice other than the Software Only option is selected for database configuration, then Oracle Universal Installer starts DBCA during the installation session. If a "Software Only" installation is performed, then DBCA can be run later from the command line.
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.
Automated Storage Management (ASM) is not supported as a storage option in this release. If you select the File System option, then DBCA 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 are used by the operating system or by Oracle products. 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 improve performance and reliability.
See Also:Oracle Database Administrator's Guide (B10739-01)
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.
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 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.
To enable automated backup jobs during installation, you must specify the following information:
The location of the flash recovery area
You can select 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
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 DBCA, 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.
Note:You must not upgrade an Oracle Database 7.3.2 for VAX VMS to an Oracle Database 10g (10.1.0.3.0) for OpenVMS. You must perform an export or import operation to carry out this type of upgradation.
To manually upgrade an existing database to Oracle Database 10g on OpenVMS, follow the steps in Oracle Database Upgrade Guide. In Chapter 3 of that guide, make the following modifications in the steps outlined for OpenVMS:
In the "Upgrade the Database" subsection of the "Upgrade the Database Manually" section, instead of Steps 4 and 5 (Setting the environment variables to point to the new release 10.1 directories), start the
mig*.com script under
ora_root:[rdbms] appropriate for the upgrade path:
For an upgrade from 8.1.7 or 9.0.1 to 10g, enter
For an upgrade from 9.2 to 10g, enter
After you complete this step, proceed with Step 7 in this subsection, which involves changing to the
For more information about upgrading a previous release of Oracle Database to Oracle Database 10g, refer to Oracle Database Upgrade Guide. The following section includes additional upgrade information that you should review before upgrading an existing database.
To upgrade an existing database that uses the AL24UTFFSS character set, upgrade the database character set to UTF8 before upgrading to Oracle Database. 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.
installing Oracle Database 10g on a node where other versions of Oracle Database are running, then ensure that you have no Oracle symbols and logicals defined prior to installing Oracle Database 10g. Do not run any
The follow are compatibility issues that you must address:
Oracle Database 10g Enterprise Edition must be installed in a location separate from other previous Oracle Database installations.
Oracle products released for earlier versions of Oracle Database (such as release 9.2.0.x and release 8.1.7.x) must not be linked with an Oracle Database 10g installation.
Note:To install Globalization Support, you must first build all Oracle products. The product directories must exist before Globalization Support message files can be copied into them.
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 the OracleMetaLink Web site for an updated list of certified hardware platforms and operating system versions. You can visit the OracleMetaLink Web site at
If you do not have a current Oracle Support Services contract, then you can access the same information from the Oracle Technology Network Web site at
This product supports multiple Oracle homes. This means that you can install this release or previous releases of the software more than once on the same system.
However, you must install this release of the 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 10g software into an existing Oracle9i Database 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.
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 is used to install Oracle Database does not define any of the Oracle logicals or symbols, or 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 of the logicals related to mailbox devices and shared libraries. Oracle Database may not run correctly if these logicals are defined.
For Oracle Real Application Clusters (RAC) installations, the Oracle Cluster Synchronization Services (CSS) daemon is installed with Oracle Cluster Ready Services (CRS) in a separate Oracle home directory.
See Also:Section 8.3, "Reconfiguring Oracle Cluster Synchronization Services" for more information about deleting and reconfiguring the Oracle CSS daemon
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 OpenVMS cluster. All references to this term should be considered as references to this configuration on an OpenVMS cluster.