|Oracle9i Installation Guide
Release 2 (188.8.131.52) for hp OpenVMS Alpha
Part Number B10508-01
This chapter provides information specific to this release of Oracle9i for HP OpenVMS. The following sections are included:
The following components are included on the product CD-ROM:
In order to take full advantage of the latest OpenVMS CPU and compiler optimizations in Oracle software products, Oracle9i Release 2 (184.108.40.206) and associated Oracle9i Release 2-based products will require HP OpenVMS AlphaServers with EV56 or later generation CPUs. AlphaServers with earlier generation CPUs will see a performance degradation. Refer to Note 181307.1 on MetaLink for a list of affected models and for instructions on how to identify the CPU model number.
The following changes and enhancements are unique to this release of Oracle9i for HP OpenVMS:
In releases prior to Oracle9i Release 2 (220.127.116.11), 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 crash needed to be reproduced. Starting with this release, by default, an image dump will be created when a background process aborts. If you do not want this feature enabled, you can turn it off using the following commands:
Please note that this change has no effect on normal daily production behavior. Oracle Corporation recommends that you do not define the dump logical.
In general, ODS-5 format allows VMS to support Microsoft Windows file naming 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 On-Disk Structure Level 5 (ODS-5) format. This is the disk to which the VMS logicals
ora_root, ora_rootdir, and
oracle_home will point. The directory that is referenced by these logicals is the parent directory for all Oracle RDBMS software, such as APACHE, CTX, INSTALL, NETCONFIG, RDBMS, UTIL, and so forth. The disks on which Oracle database files reside can be formatted as either ODS-2 or ODS-5.
Oracle Note 205630.1 can be viewed at Oracle MetaLink. Alternatively, use the search function and search for "ODS-5" for more information.
To check the current disk format, use the following DCL command:
Volume Status: will display the current ODS level. The default when initializing disks is ODS-2.
If you plan to reformat an existing (in use) disk from ODS-2 to ODS-5 format, then do the following:
If you plan to use a new (empty) disk, then use the Initialize command to format the new disk to ODS-5 format, as follows:
Beginning with this release, the directory structure of Oracle9i for HP OpenVMS closely resembles that of Oracle9i on UNIX systems. Database Administrators will more quickly become familiar with Oracle9i as the platform by being able to make file locations more consistent and predictable.
The connection to both the catalog and the database must be a TCP/IP connection.
OpenVMS always performs its I/O asynchronously. Several
init.ora parameters that mimic asynchronous behavior are not needed on OpenVMS. Refer to the Oracle9i Administrator's Guide, section 1.5.3 for the list of parameters that are not supported on OpenVMS.
With some limitations, Oracle9i for HP OpenVMS with iAS mid tier (with VMS back end database configuration) is supported. For information about iAS support, contact:
RAC Guard and RAC High Availability Extensions are not supported in this release due to the lack of cluster failover in the Operating System.
RAC Management Pack is not supported in this release.
LDAP (OID) is currently not supported. This feature is a candidate for support in future releases.
iFS and Ultra Search are not supported due to the lack of third party software called INSO filter.
Oracle9i for HP OpenVMS does not support EJB on the server. If customers have iAS in mid tier, however, they can still use the database on OpenVMS in order to use EJB.