|Oracle® Database Release Notes
10g Release 2 (10.2) for HP OpenVMS
|PDF · Mobi · ePub|
10g Release 2 (10.2) for HP OpenVMS
This document contains important information that was not included in the platform-specific or product-specific documentation. Except where noted in the text, the information in these notes applies to Oracle Database 10g Release 2 for HP OpenVMS Alpha and HP OpenVMS Itanium.
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, see the Documentation section on the Oracle Technology Network (OTN) website:
These Release Notes are part of the following documentation set for the Oracle Database 10g for HP OpenVMS:
This document contains the following topics:
Oracle Database 10g Release 2 ships with the following new features:
Oracle Database Configuration Assistant
Oracle Data Mining
Oracle Label Security
Oracle Wallet Manager
The following products are not available in this release:
Agent control utility (
Automatic Storage Management
Oracle Database 10g supports only the file system as a storage option for both the Oracle Database files as well as the Oracle Database recovery files.
Cursor size utility (
Database file size utility (
This release does not support Enterprise JavaBeans (EJB) on the server.
File Map Utility (
File Map Utility Helper (
The Hewlett-Packard Fortran compiler (formerly the DIGITAL Fortran 90) is not supported.
To check which FORTRAN compiler is on your system, run the following command:
$ HELP FORTRAN
If the following message is displayed:
"Invokes the Hewlett-Packard Fortran (formerly the DIGITAL Fortran 90) compiler."
then the FORTRAN command should be qualified with
/OLD_F77, as follows:
$ FORT/OLD_F77 foo.FOR
HS Distributed External Procedure agent (
HS OTS agent (
INSO filters for Oracle Text
iFS (Oracle Files) and Oracle Ultra Search
Oracle Files and Ultra Search are not supported due to the lack of third-party software called INSO filter.
Java API for ODM
The Java API for Oracle Data Mining is currently not supported on HP OpenVMS. However, the PL/SQL Data Mining interface is supported.
KGMGR utility (
KGPMON utility (
Max memory test utility (
Non-uniform memory access (NUMA)
OCI Instant Client (
Oracle Database Upgrade Assistant
Oracle Enterprise Manager Database Control
Note:You can access Oracle Enterprise Manager from an Oracle Client installation on Windows.
Optimal Flexible Architecture (OFA)
Oracle HTML DB
Oracle HTTP Server
This release does not support Oracle HTTP Server, although the Companion CD offers an installation option for Apache Server.
Oracle Notification Server (ONS)
Oracle Policy Manager
Oracle Real Application Clusters Guard (formerly OPFS)
Oracle Real Application Clusters Management Pack
Oracle Standard Edition
Oracle Standard Edition Real Application Clusters
This feature is not supported due to the lack of the Automatic Storage Management feature.
Oracle Workflow Server
osh utility (
OSM Discovery utility (
PSP Loader utility (
Real Application Clusters Interconnect Failover
SBTTEST utility (
SGA Dump utility (
SGA Lock/Unlock utility (
SGA Map utility (
Shared memory test utility (
SQL*Module for Ada
Support for audit information to files
Support for the
System Resource Verifier utility (
TDS compiler (
Oracle Transparent Gateway for Informix agent
Oracle Transparent Gateway for Ingres II agent
Oracle Transparent Gateway for Sybase agent
Oracle Transparent Gateway for Teradata agent
Ultra Search/Context search
Oracle XA functionality is supported only within the Oracle Database acting in the role of Transaction Manager as well as Resource Manager.
Oracle XA is the Oracle implementation of the X/Open Distributed Transaction Processing (DTP) XA interface. The XA standard specifies a bidirectional interface between resource managers (for example, Oracle) that provide access to shared resources within transactions, and between a transaction service that monitors and resolves transactions.
Oracle Call Interface has XA functionality. When building a TP-monitor XA application, ensure that the TP-monitor libraries (that define the symbols
ax_unreg) are placed in the link line before the Oracle client shared library. This link restriction is required only when using the XA dynamic registration (Oracle XA switch
Oracle Database XA calls are defined in both the client shared library (
libclntsh.so) and the client static library (
libclntst.olb). These libraries are located in the
XDK for C++
XML SQL Utility
Support for the following Oracle Database initialization parameters found in earlier releases has been removed starting with this release of Oracle Database:
The following initialization parameters are deprecated starting with this release of Oracle Database:
The following section contains information about issues related to Oracle Database 10g Release 2 and associated products such as Oracle Database installation, configuration, and upgrade:
Oracle Database Upgrade Assistant is not supported in this release of Oracle Database 10g on HP OpenVMS. To upgrade a database, follow the steps outlined in
During normal installation, when using the Oracle Database Configuration Assistant to create a database, the Oracle Database Configuration Assistant automatically starts the Oracle Enterprise Manager Configuration Assistant to create the necessary configuration files for the Oracle home and database.
If you upgrade from a previous release, then the configuration assistants do not start automatically. After the upgrade is complete, ensure the following:
The database is up and running in the Oracle Database 10g Oracle home
Set up your Oracle environment by running the following command from the Oracle home directory:
$ @orauser sid
Manually run Oracle Enterprise Manager Configuration Assistant (emca)
Oracle Enterprise Manager Configuration Assistant prompts for various parameters that you need to respond to. Enter appropriate values for these parameters. After entering the parameter values, type
Yes at the prompt asking whether to continue or not, and then press Enter. Oracle Enterprise Manager Configuration Assistant runs through the tasks and completes the configuration. If any errors are reported when running Oracle Enterprise Manager Configuration Assistant, then refer to the
ora_root:[cfgtoollogs]emca.log file for more information about errors or failures.
After Oracle Enterprise Manager Configuration Assistant runs successfully, follow the steps in the "Installing, Configuring, and Running Enterprise Manager Agent" appendix of Oracle Database Installation Guide for HP OpenVMS to complete the remaining steps.
If you plan to run Oracle Universal Installer on an existing installation, then ensure that all Oracle processes running out of that installation are completely shutdown, including Oracle instances, listeners, agent, and so on. After shutting down all Oracle processes, run the following command to stop the Bequeath listener and remove the known binaries:
There are cases where
remoracle may be optional, such as installing the Companion CD software into the same Oracle home as the Oracle Database software. If you are installing Client Administration on the same Oracle home as a Database installation, or deploying certain patches, then you must shutdown all Oracle processes. Failure to shutdown and perform
remoracle is likely to result in errors.
While installing Oracle Database, the Specify Backup and Recovery Options screen may appear truncated if the system does not have the required fonts installed. If the system has only fixed-width fonts, you may not be able to fully specify the required information in the Backup Job Credentials area of the screen. To work around this issue, do not select Enable Automated Backups on this screen. After the installation is complete, use Oracle Enterprise Manager Grid Control to enable automated backups.
A known issue exists with Oracle Multimedia on Oracle Database 10g. The problem may arise when making calls to
ordibody.sql, yielding errors such as the following:
ERROR at line 1: ORA-29400: data cartridge error IMG-00714: internal error ORA-28579: network error during callback from external procedure agent ORA-06512: at "ORDSYS.ORDIMGEXTCODEC_PKG", line 164 ORA-06512: at "ORDSYS.ORDIMGEXTCODEC_PKG", line 160 ORA-06512: at line 1 ORA-06512: at "ORDSYS.ORDIMG_PKG", line 525 ORA-06512: at "ORDSYS.ORDIMAGE", line 59 ORA-06512: at "TKIDIUSER.IMG_PROCESSCOPY", line 12 ORA-06512: at "TKIDIUSER.TKIDIPCU_MAIN", line 57 ORA-06512: at line 1
The problem is being tracked internally with Oracle bug number 4203210.
You must use UNIX-based syntax when you specify file and path names. For example, the HP OpenVMS file specification
]control1.ctl is expressed as the UNIX path
The following are known Oracle Clusterware issues in the current release:
An Oracle Clusterware installation creates the following system level logicals:
ORA_OCRCONFIG_LOC ORA_SCLS_SCR_PATH ORA_VAR_OPT
If you plan to delete an Oracle Clusterware installation and create a non-Oracle Clusterware installation on the same node, ensure that you first deassign these logicals. Failure to do so will result in unintended errors or failures on assistants such as Oracle Net Configuration Assistant and Oracle Database Configuration Assistant.
In an Oracle Clusterware installation, if Private Interconnect is selected in the Private Interconnect Configuration screen, then the Private Interconnect Configuration Assistant displays a failure message even though the actual operation completes successfully. Check the
oifcfg.log file in the installation directory, and verify that the operation is completed successfully. If a failure is recorded in the log file, then you must run the
oifcfg manually as indicated by Oracle Universal Installer. You can ignore the Private Interconnect Assistant failure if the operation completed successfully.
While installing Oracle Clusterware, the device on which an installation is created is visible and accessible across all nodes of a cluster installation. For example, for an Oracle Clusterware installation created on disk A to run on nodes B and C, disk A is accessible on both nodes. For this reason, it is not necessary to copy a device across nodes. You may see error messages similar to the following in the
.err files created under the log directory of your orainventory:
Error in copying file : rootadd.com oracle.ops.mgmt.cluster.ClusterException: PRKC-1004 : Problem in copying file to node
These errors can be safely ignored.
During a Custom installation of Oracle Real Application Clusters (Oracle RAC), Oracle Network Configuration Assistant is displayed at the end of the installation procedure even though the Database Creation option is not selected. You must run Virtual IP Configuration Assistant before running Oracle Net Configuration Assistant for Oracle RAC. To do so, perform one of the following tasks:
Cancel the Oracle Network Configuration Assistant, and then run Virtual IP Configuration Assistant, Oracle Net Configuration Assistant, and Oracle Database Configuration Assistant in that order.
Run Virtual IP Configuration Assistant from a separate window, then continue with Oracle Network Configuration Assistant that is displayed during custom installation, and then run Oracle Database Configuration Assistant.
In the Oracle RAC database alert log files, messages similar to the following are displayed:
SSKGXP_IP: Primary interface down operation location error error 0
These messages are displayed if a private interconnect is not selected for Oracle RAC cluster communication, and the public IP address of the nodes are used for cluster communication. These messages can be ignored.
crs_* commands, you must specify the arguments to these commands. For example:
srvctl start database "-d" "orcl" crs_stat "-p" "ora.ORCL.ORCL1.inst"
The command line for HP OpenVMS is case-sensitive. Therefore, all parameters to
srvctl must be passed with proper quoting to maintain the case. Moreover, the resource name you enter for
crs_* commands should match the name it is registered in the Oracle Cluster Registry (OCR).
While running Virtual IP Configuration Assistant, tracing information is displayed on the terminal from where Virtual IP Configuration Assistant is run. You can ignore this information. To suppress the tracing information, you must define the following logical before running Virtual IP Configuration Assistant.
define X$SRVM_TRACE X
Automonitoring of DB/Listener resources is not supported in this release due to OS restriction.
C++ links in the installation linking phase will generate the following error, which can be safely ignored:
%CXXLNK-I-NODEMANGLER, No demangler database was found; unresolved symbols will not be demangled.
Install the Oracle image as an HP OpenVMS resident image to increase the performance of Oracle database. To install the
ORACLE.EXE image resident, refer to document 282965.1, OpenVMS: Installing the Oracle Image /Resident on the My Oracle Support (formerly OracleMetaLink) website:
To locate document 282965.1:
Log on to My Oracle Support (formerly OracleMetaLink).
Set Article ID as the search source.
Enter 282965.1 in the search field, then click Search.
Note:Make valid backups of all HP OpenVMS and Oracle software before any changes are implemented.
Oracle recommends that you to do initial testing in a non-production environment whenever possible. For queries, contact your local support organization.
The following system changes are recommended for improved Oracle performance:
Increase the current size of the
GH_RSRVPGCNT. The size of the parameters
GH_RSRVPGCNT need to be increased by 8192, and
GH_RES_DATA to its current maximum value of 2048. This increase needs to accommodate the size of the image being installed resident. For 9.2.0.x
ORACLE.EXE, this size should be of maximum 90 MB, and for 10.1.0.x
ORACLE.EXE it should be approximately 98 MB depending on what options you have selected for
ORACLE.EXE during installation.
Oracle recommends using
AUTOGEN and the
modparams.dat file for making these changes. These values should be changed by making use of the
ADD_parameter feature of
HP OpenVMS System Services Reference Manual for information about
HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems for information about using
AUTOGEN to adjust system parameters
Note:These parameters are not dynamic. You must restart your system for the new values to take effect.
You must also install the HP OpenVMS image
SYS$LIBRARY:DSMTSHR.EXE with shared address space before the Oracle image is installed resident. HP OpenVMS installs this image by default, but not with shared address space.
There are two ways to implement this:
install replace command as shown:
$ install replace sys$library:dismntshr.exe/shared=address
This command would need to be rerun after any system restart and before the Oracle image is installed (which typically occurs during execution of Oracle startup procedures).
Edit the file
sys$manager:vms$images_master.dat, which contains the list of installed images for HP OpenVMS, and add the
/shared=address qualifier for the
DISMNTSHR.EXE entry in the file. This is done before running
AUTOGEN to ensure that
DISMNTSHR.EXE is installed with the
/share=address option after a system restart or after running
AUTOGEN. You may re-edit this file if it is included in a system patch or upgrade. Caution should be taken when editing this file, so that this is the only change made.
To make the Oracle image an installed resident, make the following changes to the command procedure that links the
ORACLE.EXE image and the procedure that installs this image:
installl create ora_root:[bin]oracle.exe/open/header_res/share
installl create ora_root:[bin]oracle.exe/open/header_res/share=address/resident
The following are known problems in the current release:
Bug 3107086: RMAN backup files not truncated when finished
Bug 1835885: DBV fails with DBV-00102 on data files exceeding 2047 MB
SQL*LOADER fails with
ORA-01426: Numeric Overflow
ORA-00600 [KCCSBCK FIRST]   IN TKMSTU9E.DIF
The effect of this bug will include: an Exclusive Mount attempt when another Instance is already Mounted fails with Split Brain
ORA-00600 [KCCSBC FIRST] instead of a file lock conflict.
(4L1) TKAMX384.DIF - ORA-16107: ALL LOG DATA FROM PRIMARY HAS BEEN PROCESSED
The effects of this bug include:
When Initialization parameter
MANUAL and the DBA forgets to manually copy a new data file to the Standby database after adding a data file to the Primary, the Apply server will not detect the omission and terminate.
ORA-27086 or ORA-27089 may not be detected.
TRLE2BX.DIF AND TRLE2VX.DIF FROM LRG3CU ON LINUX
The effect of this bug will include: if a data file contains binary data which may be interpreted as a record terminator, SQL*Loader may miss a record terminator.
Temporary files PERLPIPE*.COM created in login directory
This has no impact on the functioning of Enterprise Manager Agent. The temporary files can be manually deleted. Refer to the bug for more details and latest updates.
Delays in Listener Start/Stop from Console
This problem has not been observed in an Oracle installation, but has only been observed within the internal test QA area, which was set up with additional spooling of debugging information. However, the latency may reproduce in a customer environment, although very unlikely. To correct this, repeat the operation or perform the operation directly on the Server box where the listener is running. The modified status is automatically picked up by Enterprise Manager Database Control within a few minutes of the direct operation.
deadlock detection error during Oracle RAC instances startup by Oracle Database Configuration Assistant
Refer to the bug for the solution and latest updates.
Inconsistent ora-0600 errors during Oracle RAC stress test
If you select 'Generate Database Create Scripts' when running the Oracle Database Configuration Assistant, then error messages similar to the following are displayed:
P2-0310: unable to open file "DISK:[INSTALL_TEST.Home15]/sysman/admin/emdrep/sql/core/latest/admin/admin_check_repos_user.sql" SP2-0310: unable to open file "DISK:[INSTALL_TEST.Home15]/sysman/admin/emdrep/sql/core/latest/admin/admin_create_repos_user.sql"
These errors can be safely ignored. It is not required to create a repository on HP OpenVMS, since Database Control is not supported.
When performing an Oracle Database Custom installation, the following message may appear in the
1 :ORA-06512: at "SYS.DBMS_JAVA", line 236 1 :ORA-06512: at line 2 1 :ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions.
This message can be safely ignored as the JAccelerator component is not supported.
During an Oracle Clusterware installation from the Oracle Clusterware release media, the following error message is displayed when you click Next on the Cluster Configuration screen:
Each node must have both private and public node name
This error message is displayed even if you enter valid public and private node names. Click Ok, and then click Next to proceed.
During a Database Enterprise installation, the installation log and
orainstall error file displays the following errors:
Performing fastcopy operations based on the information in the file 'oracle.server_EE_1.xml'.
Performing fastcopy operations based on the information in the file 'setperms1.sh'.
Exception occurred during spawning:Child creation error: no such file or directory.
These errors are can be safely ignored.
While installing Oracle Database Client, do not select individual products in the Custom installation option. Instead, select all the products from the menu.
During an Oracle Database installation, the following messages may be displayed after the relinking phase.
Redefining LNM$FILE_DEV... %RMS-E-FNF, file not found %RMS-F-ISI, invalid internal stream identifier (ISI) value
These messages can be safely ignored.
OUI: unable to find any user group
During installation, the following error is reported by the Oracle Universal Installer at 84% in the Processing Oracle Database 10g 10.1.0.3.0 window:
Unable to find any user group
installActions log file contains the following:
Calling Query unixQueries10.1.0.3.0 getGroups Query Exception: NoGroupsException Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException
The error occurs when the installation is carried out from an HP OpenVMS account, which is a member of an unnamed UIC group. Before attempting to install Oracle Database 10g Release 1 products, run the following commands:
$ grp = 'f$getjpi("","GRP")' * %X10000 $ grp = grp + %X0FFFF $ grpname = f$identifier(grp,"NUMBER_TO_NAME") $ show sym grpname
If the symbol
grpname in the preceding commands is a null string, then run the following command:
$ write sys$output f$fao("!%U",grp)
This command displays a group UIC in a format similar to the following:
Use the HP OpenVMS
authorize utility to add a group name to the VMS rights database.
For example, the following commands use the UIC
[50,*] and the group name DBA:
$ set default sys$system $ run authorize UAF> add/identifier/value=uic:[50,*] DBA %UAF-I-RDBADDMSGU, identifier DBA value [000050,177777] added to rights database UAF> exit
The following sections provide information about issues that affect other Oracle products:
In the Oracle Net Configuration Assistant help, the link to the Select Oracle Context help topic is broken. The text for this topic is as follows:
Directory Usage Configuration, Select Oracle Context
Oracle administrative content has been found in multiple locations in the directory. Oracle administrative content is stored in Oracle Context, a subtree in the directory that stores Oracle entries.
From the list, select or enter the location you want to use as the default Oracle Context location from which this computer will access Oracle entries, such as connect identifiers.
If you select the use of the IPC protocol for the network layer, Oracle Net Configuration Assistant cannot reliably determine whether the key value specified in the protocol is in use. To let the user specify whether the key is actually available, Oracle Net Configuration Assistant displays the following message:
The information provided for this listener is currently in use by other software on this computer. You can proceed with this configuration as it is, but it will not be possible to start this listener until the conflict is resolved. Would you like to continue with the configuration anyway?
When this message is displayed, you should check if there are other listener processes on the system. In addition, you should ensure that the key value you have specified is not in use. If it is not in use, then proceed with the configuration session. If it is in use, then shut down the listener using the key. Alternatively, you can use the Oracle Net Configuration Assistant screen to specify that you do not want to continue with the installation and then select a key value that is not in use on the system.
If a user starts the Flashback Table or Flashback Analysis operation, and that user has
FLASHBACK ANY TABLE privileges but does not have DBA privileges and specific flashback privileges on the objects that flashback is started on, then the following errors may occur:
ORA-02002: error while writing to audit trail ORA-00600: internal error code, arguments: [kzasps1], , , ,,
To fix this problem, as
SYSDBA, grant the user
FLASHBACK privilege on the objects that are referred to in the
FLASHBACK TABLE statement and then start the flashback operation. For example:
SQL> GRANT FLASHBACK ON SCOTT.EMP_1 TO user1;
This issue is tracked with Oracle bug 3403666.
Viewing the execution plan of Period SQL in Korean causes an internal server error. This problem is unique to Korean, and does not reproduce in Japanese or Chinese. The only workaround currently available is to run the product in a language other than Korean when you need to view this page.
Grid features, Resonance and Transparent Session Migration that are listed in Oracle Database New Features Guide, 10g Release 1 (10.1) are not available in this release.
To install Enterprise Security Manager, install Oracle Client and choose the Administrator installation type.
For full-text searching with Oracle Text, you must create XML tables manually.
If you will need to use Oracle Text indexes for text-based
ora:contains searches over a collection of XML elements, then do not use the XML schema annotation
storeVarrayAsTable="true". This annotation causes element collections to be persisted as rows in an Index Organized Table (IOT). Oracle Text does not support IOTs.
To be able to use Oracle Text to search the contents of element collections, set parameter
genTables="false" during schema registration. Then create the necessary tables manually, without using the
ORGANIZATION INDEX OVERFLOW clause. The tables will then be heap-organized instead of index-organized (IOT), as shown in the following example:
CREATE TABLE PurchaseOrder of XMLTYPE XMLSCHEMA http://localhost:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd ELEMENT "PurchaseOrder" VARRAY "XMLDATA"."ACTIONS"."ACTION" STORE AS TABLE ACTION_TABLE ((PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX))) VARRAY "XMLDATA"."LINEITEMS"."LINEITEM" STORE AS TABLE LINEITEM_TABLE ((PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX)));
In this release, the
AES_256 cipher suites do not work with Transport Layer Security (TLS). This issue is tracked with Oracle bug 3753967.
Files such as
SQLNET.ORA, if configured manually, or copied and edited from earlier releases of Oracle Database may have record attributes that are incompatible with Oracle Database 10g Release 2. The software cannot read such files.
This may result in:
Inability to start the listener
Services not registered with the listener
Inability to connect to other databases
ORA-12154: TNS:could not resolve service name
Run the following command on each file affected:
$ DIR/FULL filename;0
An output similar to the following may be displayed:
Record format: Variable length, maximum 255 bytes Record attributes: Carriage return carriage control
If the output includes the preceding entries, then run the following command:
$ CONVERT/FDL=SYS$INPUT filename filename RECORD CARRIAGE_CONTROL carriage_return FORMAT stream_LF ^Z
The following sections lists current restrictions for using Oracle Database 10g.
HP OpenVMS always performs its I/O asynchronously. Several
init.ora parameters that mimic asynchronous behavior are not needed on HP OpenVMS. Refer to Section 3, for the list of parameters that are not supported on HP OpenVMS.
With some limitations, Oracle Database 10g with Oracle Application Server middle tier (with HP OpenVMS back end database configuration) is supported. For information about iAS support, contact your Oracle representative.
Moving executables from one HP OpenVMS system to another is not recommended due to the usage of shared libraries and to the difficulty of ensuring valid referencing. Oracle recommends that you relink on the node where the executable will run.
The Hewlett-Packard Fortran compiler (formerly the DIGITAL Fortran 90) is not supported by Oracle Database 10g. To check which FORTRAN compiler is on your system, refer to "Hewlett-Packard Fortran Compiler (F90)".
Due to an inherent characteristic of the Perl language, wherein it attempts to translate any string with the '$' character in it as a Perl variable, it is strongly recommended that the paths used for Oracle targets, such as
listener_ora_dir do not contain the '$' (dollar) character in them. This issue is tracked through Oracle bug 4299411.
When running the Oracle Universal Installer, the Installer may take about five minutes to move from one screen to the other. This is normal and expected and the Installer is not hanging. An installation will run between 3-4 hours depending on the products being installed.
During installation, when you click Next on the Installation Details screen, Oracle Universal Installer processes the information that you provided up to that point. This may take 10 minutes. During this time, it may appear that Oracle Universal Installer is not responding. There may be similar delays on other installer screens.
When running the Oracle Database Configuration Assistant, the assistant performs background operations such as running databases. As a result, some of the assistant screens do not change for 10 minutes or more, depending on the system performance.
If the Password Management button on the last Oracle Database Configuration Assistant screen is not visible, then expand the Oracle Database Configuration Assistant window to use the Password Management feature.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Database Release Notes, 10g Release 2 (10.2) for HP OpenVMS
Copyright © 1996, 2012, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.