Release Notes
Release 2 (9.2.0.5.0) for hp OpenVMS Alpha
B15894-02
August 2006
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 Oracle9i release 2 (9.2.0.5 and earlier).
It contains the following topics:
The following sections contain information about issues related to Oracle9i and associated products:
The following products are not available in the current release. They may be available in future releases.
Apache modules mod-JServ, mod-perl, and mod-ssl
Connection Manager
iFS
Kerberos
OLAP
Oracle Data Mining
Oracle Data Guard Broker
Oracle Database Upgrade Assistant
Oracle Enterprise Manager
Note: You can access Oracle Enterprise Manager from an Oracle Client installation on Windows. |
Oracle interMedia, except for interMedia Image
Oracle Internet Directory
Oracle Label Security
Oracle Policy Manager
Oracle Real Application Cluster Management
Oracle RAC Guard (formerly OPFS)
Oracle Wallet Manager
Oracle Workflow Server
PGA Aggregate Target
Personalization
RAC Interconnect Failover
SQL*Module for Ada
SNMP
SSL
Ultra Search/Context search
Workspace Manager
XA
XDK for C++
XML SQL Utility
If you use XML DB, you must use the Oracle9i release 9.2.0.3 or a later version. The earlier versions of Oracle9i are no longer supported.
You must install this product into a new Oracle home directory. You cannot install products from one release of Oracle9i into an Oracle home directory of a different release. For example, you cannot install release 9.2.0.5 software into an existing release 9.0.1 Oracle home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation fails.
You can install this release more than once on the same system provided that each installation is installed in a separate Oracle home directory.
Before installing Oracle software, log out of any existing Oracle sessions. If you do not do this, the new installation will include the logicals and symbols of the active Oracle sessions.
Ensure that the LOGIN.COM
file of the account that will be used to install Oracle9i does not define any of the Oracle logicals or symbols, or does not run any command file that might define these. 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. Oracle9i may not run correctly if these logicals are defined.
The following error message may occur during installation. In this example, oraclehome_path
is the path of the Oracle home directory:
s_touchFileFunction_ux:ERROR src oraclehome_path/lib/ldflags
A list of recommended OpenVMS tuning parameters for new Oracle9i installations is available on OracleMetalink, from document 156484.1, VMS: System Tuning Recommendations for New 8i/9i RDBMS Installations at:
http://metalink.oracle.com
To locate document 156484.1:
Click Advanced at the top of the OracleMetalink page.
Enter 156484.1 in the Document ID field, then click Submit.
Oracle recommends that you review this document before installing Oracle9i.
The Oracle9i Installation Guide for hp OpenVMS Alpha incorrectly lists the BYTLM account quota value as 150,000. The required minimum value is 750,000.
Database Configuration Assistant (DBCA) cannot start from the Installer. To work around this problem, after installation exit from the Installer to DCL level then enter the following commands:
$ set default oracle_home_location
$ @orauser
$ dbca
The following error may appear in the DBCA log files:
-- wrong OS/platform: Solaris sparc
Ignore this error. It occurs during an attempt to load JAccelerator DLLs. JAccelerator is not supported on Oracle9i release 2 (9.2) for hp OpenVMS Alpha.
The following DBCA options are not supported with this release:
Data Mining
OLAP
UltraSearch
Sales History Demonstration
This demonstration requires OLAP. OLAP is not currently supported on hp OpenVMS Alpha.
Review the following known issues before using DBCA:
If you select the "Manage templates"/"From existing database (structure as well as data)" option, DBCA might hang when it attempts to verify existing databases in the SYS$LOGIN:oratab
file. To workaround this issue, do not use this drop down list. If you have multiple instances listed in the ORATAB
file, make sure that the instance that you want to configure is either the first or the only instance listed in the ORATAB file. If you do this, it will not be necessary to use the drop down list.
When you run the DBCA, some error messages may appear twice.
You must use UNIX style syntax when you specify file and pathnames. For example, the VMS file specification dka100:[oracle92.oradata.my_db]control1.ctl
is expressed as the UNIX path dka100/oracle92/oradata/my_db/control1.ctl
.
If you create a new database with DBCA or use a set of database create scripts produced by DBCA, the CREATEDBCATALOG.sql
script is executed. This script references the owminst.plb
file. This file is not included because Oracle Workspace Manager is not included in this release.
As a result, the following error message appears:
SP2-0310: unable to open file "ora_root:[rdbms.admin]owminst.plb
You can ignore this error message.
If you attempt to create a database with DBCA, you will receive the ORA-12535 error message. To workaround this problem, see Tip 2 in OracleMetalink document 226184.1, DBCA tips for Oracle RDBMS 9.2.X on OpenVMS at:
http://metalink.oracle.com
To locate document 226184.1:
Click Advanced at the top of the OracleMetalink page.
Enter 226184.1 in the Document ID field, then click Submit.
This issue is tracked with Oracle bug 2671551.
Oracle9i release 2 has two separate logicals that specify the top-level directory of the installation: ORA_ROOT which is a concealed logical used in earlier releases, and ORACLE_HOME which is a non-concealed logical. You can use both logicals with the following restrictions.If the top-level directory is DISK$DISK1:[ORACLE92]
, then the following commands both return DISK$DISK1:[ORACLE92]
:
$ show logical ORA_ROOT $ show logical ORACLE_HOME
Therefore, the following command is invalid:
$ set default ORA_ROOT
The following commands are valid:
$ set default ORA_ROOT:[000000] $ set default ORACLE_HOME
The ORAUSER.COM
script must be located in the top-level Oracle home directory. Do not move this script. The definitions of Oracle logicals are created from the top-level Oracle home directory. If you run the ORAUSER.COM
script from a location other than the Oracle home directory, Oracle9i does not work correctly.
If you intend to use data files exceeding 4095 MB, you must install patch 2673723, available on OracleMetalink:
http://metalink.oracle.com
To locate patch 2673723:
Click Patches at the side of the OracleMetalink page.
Select Simple Search.
Enter 2673723 in the Search By Patch Numbers field.
Enter HP OpenVMS Alpha in the Platform or Language field, then click Submit.
Select the correct patch for your release.
The JDBC demonstrations are shipped as a backup saveset DBJAVA_DEMO.BCK
, which is located in the ORA_ROOT:[jdbc.demo]
directory. To install the demonstrations, enter the following commands:
$ set default ORA_ROOT:[jdbc.demo] $ backup/log dbjava_demo.bck/save_set [...]
Starting with Oracle9i release 2 (9.2.0.2), support for shared libraries in RMAN is available. If you want to change the specified MML, you no longer need to perform a relink. You can explicitly override the specified MML using the ALLOCATE CHANNEL command as follows:
RUN
{
ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=mymml';
}
In this example, mymml
is a logical that specifies the shared library that is provided by the third-party vendor. You should add the definition of the logical to the ORA_ROOT:[dbs]
sid_
SID
.
properties
file.
Alternatively, you can define the LIBOBK logical. By default, RMAN looks for the LIBOBK logical first. If it does not find either the LIBOBK or mymml
logical, then the RMAN logical defaults to the SBT disk implementation (which is statically linked). Note that because the shared library is called into by the server, third-party vendors who are supplying their own MML must ensure that their library is compiled 64-bit. The Oracle9i code was compiled using the qualifier /NAMES=AS_IS
, and the symbol vector must match exactly the entry point names as indicated in the SBT API specification.
The default port for Oracle HTTP Server is 7777. If this port is already in use by another application, or if you would like to use a different port, then modify the HTTPD.CONF
file located in the ORA_ROOT:[Apache.Apache.SPECIFIC...CONF]
to specify a different port number.
If you shut down the database with the SHUTDOWN ABORT command and then start up the database with the same utility, for example RMAN or SQL*Plus, you will receive error ORA-3113. To work around this problem, do one of the following:
Shut down the database with the SHUTDOWN IMMEDIATE or SHUTDOWN NORMAL command
Shut down the database with the SHUTDOWN ABORT command, then exit RMAN or SQL*Plus, return to the operating system level, and restart RMAN or SQL*Plus
This issue is tracked with Oracle bugs 2672239 and 2712369.
When you create a custom database using Database Configuration Assistant, the following message is displayed:
ORA-29807: specified operator does not exist
Workaround: Click Ignore and continue the database creation process.
This issue is tracked with Oracle bug 5095934.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/
.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle 9i Release Notes, Release 2 (9.2.0.5.0) for hp OpenVMS Alpha
B15894-02
Copyright © 1996, 2006, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.