1 Installation Overview

1.2.1 Turning Off the Image Dump

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_sid_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 system Identifier or instance name.

Start the instance, and open the database. For example:

$ DEFINE/SYSTEM ORA_PROD_LMD0_DMP FALSE
$ SQLPLUS/NOLOG
SQL> connect / as sysdba
SQL> startup

This change has no effect on the usual daily production activities. Oracle recommends that you do not define the dump logical.

1.2.2 Oracle Database Dependency on ODS-5 Disk Structure

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 ORA_ROOT, ORA_ROOTDIR, and 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.

If you downloaded Oracle 10g R2 from OTN or copy the kit from the DVD to disk, make sure that the location of the software kit is in ODS-5 format.

Precautions

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

To check the current disk format, run the following DCL command:

$ SHOW DEVICE/FULL device_name

The Volume Status: line of the output displays the current ODS level. The default when initializing disks is ODS-2.

Changing Disk Format

If you plan to reformat an existing (in use) disk from ODS-2 to ODS-5 format, then:

1. Create at least one OpenVMS backup of the disk.

2. Use the following command:

   $ SET VOLUME /STRUCTURE_LEVEL=5 device_name
   
   

   Example:

   $ SET VOLUME/STRUCTURE_LEVEL=5  $2$DKC100:
   

Formatting a New Disk

If you plan to use a new (empty) disk, then use the following command to format the new disk to ODS-5 format:

$ INITIALIZE/STRUCTURE=5 device_name:volume_label

Example:

INITIALIZE/STRUCTURE=5 $2$DKC100: TESTVOL

1.2.3 Oracle Database Installation Directory Structure

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.

1.2.4 Unsupported Initialization Parameters

Support for the following Oracle Database initialization parameters found in earlier releases has been removed starting with this release of Oracle Database.

• ALWAYS_ANTI_JOIN

• ALWAYS_SEMI_JOIN

• JOB_QUEUE_INTERVAL

• OPTIMIZER_PERCENT_PARALLEL

• HASH_MULTIBLOCK_IO_COUNT

• DB_BLOCK_LRU_LATCHES

• DB_BLOCK_MAX_DIRTY_TARGET

• SORT_MULTIBLOCK_READ_COUNT

• DB_FILE_DIRECT_IO_COUNT

• GC_DEFER_TIME

• GC_RELEASABLE_LOCKS

• GC_ROLLBACK_LOCKS

• LM_LOCKS

• LM_RESS

• USE_INDIRECT_DATA_BUFFERS

1.2.5 Deprecated Initialization Parameters

The following initialization parameters are deprecated starting with this release of Oracle Database.

• ROLLBACK_SEGMENTS

• FAST_START_IO_TARGET

• TRANSACTIONS_PER_ROLLBACK_SEGMENT

• LOG_CHECKPOINT_INTERVAL

• DB_BLOCK_BUFFERS

• BUFFER_POOL_KEEP

• BUFFER_POOL_RECYCLE

1.5.1 Database Options

Oracle provides the following preconfigured database types that you can create or customize during the installation:

• General Purpose

• OLTP

• Customized

• Software Only

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

• Interactive mode

  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.

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

1.6.1 Database Storage Options

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.

File System

Automated Storage Management (ASM) is not supported as a storage option in this release. 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 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 increase performance and reliability. Using this methodology, you do not need to specify more than one device for database storage.

1.6.2 Database Backup and Recovery Options

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.

This section contains the following sections:

• Enabling Automated Backups

• Backup Job Default Settings

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

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, you can specify a start time for the backup job and a disk quota for the flash recovery area.

1.8.1 Hardware and Software Certification

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

https://metalink.oracle.com

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

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

1.8.2 Multiple Oracle Homes

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.

Installing the Software on a System with an Existing Oracle Installation

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 10g 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.

1.8.3 Logical Names and Symbols

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, 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 of the logicals related to mailbox devices and shared libraries. Oracle Database may not run correctly if these logicals are defined.

1.8.4 Oracle Cluster Synchronization Services Daemon

For Oracle RAC installations, the Oracle Cluster Synchronization Services (CSS) daemon is installed with Oracle Clusterware in a separate Oracle home directory. For single-node installations, the CSS daemon is installed in and runs from the same Oracle home as Oracle Database.

1.9.1 Manually Upgrade a Database

To manually upgrade an existing database to Oracle Database 10gR2 on OpenVMS, follow the steps in the Oracle Database Upgrade Guide. In Chapter 3 of the guide, use the following steps for OpenVMS.

In the "Prepare the New Oracle Home" subsection of the "Upgrade the Database Manually" section, substitute ORACLE_HOME/dbs with ORA_ROOT:[DBS]. Also substitute ORACLE_HOME/dbs/orapwsid with ORA_ROOT:[DBS]orapwsid.

• In the "Upgrade the Database" subsection, ignore step 1 (for Windows operating system).

• Set your default directory to the new Oracle home and execute the script @ORAUSER.COM (without arguments). Then SET DEF ORA_ROOT:[RDBMS] and execute the migrate script:

  • To upgrade 8.1.7 or 9.0.1 to 10gR2, enter @MIGRATE89.COM

  • To upgrade from 9.2 to 10gR2, enter @MIGRATE92.COM

  • To upgrade from 10gR1 to 10gR2, enter @MIGRATE101.COM

Enter the details prompted by the upgrade assistant.

After you complete this step, proceed with Step 4 in this subsection, which involves changing to the ORA_ROOT:[RDBMS.ADMIN] directory.

If you want to use an existing OpenVMS Alpha database on an OpenVMS Itanium system (Integrity Server), you must upgrade the database to 10.2 on Alpha before transferring it to Itanium.

1.9.2 AL24UTFFSS Character Set

To upgrade an existing database that uses the AL24UTFFSS character set, upgrade the database character set to UTF8 before upgrading to Oracle Database10g. 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.

1.9.3 CRS/RAC upgrade

Please refer to file readme_vms_10grac.txt that is shipped in CRS shiphome for complete details about CRS/RAC upgrade from 10gR1 to 10gR2.

The file location in the CRS software distribution will be at:

DISK$MOUNT[CLUSTERWARE]README_VMS_10GRAC.TXT