Oracle® Database Release Notes
10g Release 1 (10.1.0.2.0) for 64-Bit Windows Part No. B13800-04 |
|
Copyright © 2005, Oracle. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Release Notes
10g Release 1 (10.1.0.2.0) for 64-Bit Windows
Part No. B13800-04
April 2005
The information in these Release Notes is current as of the release date for Oracle Database 10g release 1 (10.1.0.2.0) for 64-bit Windows. For the most current information, refer to the online Release Notes located on Oracle Technology Network (OTN) at
http://oracle.com/technology/documentation/
This is the main release notes document for the 64-bit Windows product. Oracle recommends you also review Oracle Database Readme and Oracle Database Release Notes for Windows (32-bit version) before installing Oracle Database.
See Also: Oracle Database Readme and the 32-bit version of Oracle Database Release Notes for Windows available on OTN |
This document is an update of Oracle Database Release Notes Release 10g Release 1 (10.1.0.2.0) for 64-Bit Windows, Part No. B13800-03, published October 2004. The information in this update is current as of April 2005. At the time of this publication, Oracle Database 10g release 1 (10.1.0.3) patch set 1 is available for download from OracleMetaLink. Oracle recommends installing the latest patch set release after successful installation of the Oracle Database.
http://metalink.oracle.com/
This document contains these topics:
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. 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 additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
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.
For more information, refer to the Oracle Database 10g release 1 (10.1.0.2.0) documentation available at
http://oracle.com/technology/documentation/
Additional component README files are accessible after installation. They are located in:
ORACLE_BASE
\
ORACLE_HOME
\doc
ORACLE_BASE
\
ORACLE_HOME
\relnotes
Product subdirectories in directory ORACLE_BASE
\
ORACLE_HOME
The following components are not supported with 64-bit Windows:
Business Components for Java (BC4J)
DCE and CyberSafe Adapter Support
Entrust PKI Support
Generic Connectivity
INSO filters are not supported on Windows XP 64-bit Edition Version 2003 for 64-bit Itanium 2 Systems.
Java Server Pages
nCipher Accelerator Support
Oracle Data Provider for .NET
Oracle Enterprise Integration Gateways, which include the following:
Oracle Procedural Gateway for APPC
Oracle Transparent Gateway for IBM DRDA
Oracle Enterprise Manager Grid Control CD
A 64-bit Windows version of Oracle Enterprise Manager Grid Control is not available in this release. Use the Linux version of Oracle Enterprise Manager Grid Control from your Linux system to manage the 64-bit Windows computer nodes remotely.
Oracle Enterprise Manager Java Console
Oracle Fail Safe
Oracle Fail Safe is not available with the initial 10g release 1 (10.1) version for 64-bit Windows. Oracle Fail Safe will be available the beginning of September 2004.
Oracle Messaging Gateway
Oracle Migration Workbench
Oracle Migration Workbench can be executed from a 32-bit Windows environment to migrate third party databases, as supported by release 9.2.0.1.7 or higher, to an Oracle Database 10g release 1 (10.1) database installed on a 64-bit computer.
Oracle Objects for OLE
Oracle Open Gateways, which include the following:
Oracle Transparent Gateway for Sybase
Oracle Transparent Gateway for Teradata
Oracle Transparent Gateway for Microsoft SQL Server
Oracle Workflow Builder
The Oracle Workflow Builder feature of Oracle Workflow Server is not available on the Oracle Database for 64-bit Windows Client CD. It is available only on the Oracle Database for 32-bit Windows Client CD. Using the Workflow Builder from a 32-bit computer to connect to a 64-bit computer is supported.
Pro*COBOL
To use raw partitions or logical drives on Windows Server 2003, you must enable disk automounting. Enable disk automounting for:
Raw Partitions for Oracle Real Application Clusters (RAC)
Cluster File System for Oracle Real Application Clusters
Oracle Clusterware
Raw partitions for a single-node database
Logical drives for Automatic Storage Management (ASM)
Follow these steps to enable automounting:
Enter the following commands at a command prompt:
C:\> diskpart DISKPART> automount enable DISKPART> exit
Restart your computer.
Note: All nodes in the cluster must have automatic mounting enabled in order to correctly install RAC and Oracle Clusterware. Oracle recommends that you enable the automatic mounting feature before creating any logical partitions for use by the database, ASM, or the Cluster File System.You must restart each node after enabling this feature. After it is enabled and the node restarted, automatic mounting remains active until it is disabled. |
See Also: Operating system documentation for more information aboutDiskPart
|
The following procedures describe how to upgrade an Oracle 7.3.4 database from 32-bit Windows to an Oracle Database 10g release 1 (10.1) for 64-bit Windows.
Direct upgrade is not supported. Complete the following steps to upgrade to the new Oracle Database 10g release:
See Also: Appendix G, "Oracle Database for 64-Bit Windows" in Oracle Database Platform Guide for Windows for more information about upgrading 32-bit Windows Oracle8i, Oracle9i, and Oracle Database 10g release 1 (10.1) databases to 64-bit Windows |
Follow these steps to upgrade an Oracle 7.3.4 database to Oracle9i release 2 (9.2). After completing these steps, you will have an Oracle9i release 2 (9.2) database on 64-bit Windows.
On the 32-bit windows computer:
Shut down the database and perform a full offline backup.
Install 9.2.0.2.1 32-bit software on the 32-bit computer which has the 7.3.4 database. Selecting the Software Only option is sufficient.
Run the migration utility (mig.exe
) from the 9.2.0.2.1 installation against the 7.3.4 instance.
See Also: Appendix D, "Upgrading an Oracle7 Database Using the MIG Utility" of Oracle9i Database Migration (part number A96530-02)This guide is available on OTN
|
Note: The migration utility creates a convert file that contains the information of the Oracle7 control file. Later in the upgrade process, the convert file is used byALTER DATABASE CONVERT to create a new control file in Oracle9i. The name and location of the convert file are operating system-specific. For example, on a UNIX operating system, the default location is ORACLE_HOME /dbs in the Oracle7 environment, and the default filename in this directory is conv sid .dbf , where sid is your Oracle7 instance ID. On Windows platforms, the default location is ORACLE_HOME \rdbms in the Oracle9i environment, and the default filename in this directory is convert.ora .
|
To migrate to the 64-bit Oracle9i Oracle home, complete the following steps on the 64-bit Windows computer:
Install Oracle9i Database release 2 (9.2.0.2.1) for 64-bit Windows.
See Also: Oracle9i Database Installation Guide for 64-Bit Windows (part number B10546-01) for more information |
Create the new Oracle9i database service at the command prompt:
C:\> ORADIM -NEW -SID SID [-INTPWD PASSWORD] -MAXUSERS USERS -STARTMODE AUTO -PFILE ORACLE_HOME\DATABASE\INITSID.ORA
where:
Variable | Description |
---|---|
SID
|
The SID of the database you are upgrading.
|
PASSWORD
|
The password for the new Oracle9i Database for 64-bit Windows. This is the password for the user connected with SYSDBA privileges. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and a password is not required.
|
USERS
|
The maximum number of users who can be granted SYSDBA and SYSOPER privileges.
|
ORACLE_HOME
|
The release 9.2 Oracle home directory. Ensure that you specify the full path name with the -PFILE option, including drive letter of the Oracle home directory.
|
Copy the 32-bit datafiles to the new 64-bit Oracle home.
Copy the convert.ora
file generated by the migration utility to ORACLE_BASE
\
ORACLE_HOME
\rdbms
directory on the 64-bit computer.
Copy the 32-bit configuration files to the 64-bit Oracle home.
If your 32-bit initialization parameter file has an IFILE (include file) entry, then copy the file specified by the IFILE entry to the 64-bit Oracle home and edit the IFILE entry in the initialization parameter file to point to its new location.
If you have a password file in the 32-bit Oracle home, then copy the password file to the 64-bit Oracle home. The default 32-bit password file is located in ORACLE_BASE
\
ORACLE_HOME
\database\pwd
sid
.ora
. The sid
is your Oracle instance ID.
In the 64-bit Oracle home, add the _SYSTEM_TRIG_ENABLED = false
parameter to the initialization parameter file before changing the word size.
Follow the upgrade steps documented in the "Upgrade the Database" section in Chapter 3 of Oracle9i Database Migration (part number A96530-02).
Run utlirp.sql
at the end to complete the word size change.
Remove the _SYSTEM_TRIG_ENABLED = false
parameter from the initialization parameter file.
If you upgrade an Oracle9i database to Oracle Database 10g release 1, Oracle Flashback features using a timestamp may fail. To work around this problem, enter the following SQL commands from the Oracle Database 10g database:
SQL> DELETE FROM smon_scn_time WHERE orig_thread <> 0; SQL> COMMIT;
This issue is tracked with Oracle bug 3994270.
Under certain conditions, two packages owned by the OLAP Catalog schema, OLAPSYS
, will be listed as INVALID
in your upgraded database. These packages are:
CWM2_OLAP_AW_CREATE
CWM2_OLAP_VALIDATE_MAPPING
These packages are obsolete with this release and should be dropped from the database.
DROP PACKAGE OLAPSYS.CWM2_OLAP_AW_CREATE DROP PACKAGE OLAPSYS.CWM2_OLAP_VALIDATE_MAPPING
Note: This bug has been fixed in the Oracle Database 10g release 1 (10.1.0.3) patch set. |
Bug 3636652 affects the creation of services with Database Configuration Assistant (DBCA). If you use DBCA to configure high availability services, then the process fails during the start phase. The failure occurs at approximately when the progress bar indicates that it is 50% complete. At this time, DBCA displays an error message indicating that DBCA could not start the service called service_name
.
In addition, the use of SRVCTL commands to start the services that you created with DBCA or SRVCTL also fail with the following errors:
PRKP-1030: Failed to start the service service_name
CRS-1006: No more members to consider
CRS-0215: Could not start resource resource_name
As a workaround, download and install the patched file, racgchsn.exe
using the following procedure:
Download the patch into a local subdirectory.
Rename your original version of the racgchsn.exe
file by running the following command:
renameORACLE_BASE
\ORACLE_HOME
\bin\racgchsn.exeORACLE_BASE
\ORACLE_HOME
\bin\racgchsn.bk1
Copy the downloaded version of racgchsn.exe
into the ORACLE_BASE
\
ORACLE_HOME
\bin
directory by running the following command:
copydownload_location
\racgchsn.exeORACLE_BASE
\ORACLE_HOME
\bin
If your Oracle home is on a shared cluster file system partition, then you only need to perform this procedure once and you can perform this procedure on any node in your cluster.
If your Oracle home is on a non-shared file system, that is, if your Oracle home is on a file system in which each node has a local copy of the binaries, then perform this procedure on each node in your cluster. After you install the updated racgchsn.exe
file, you can use DBCA and SRVCTL to configure and start services.
Bug 3602534
Users installing Oracle HTML DB on Windows Server 2003 should download the env.exe
patch and place it in the PATH
on the system before proceeding with the installation. The link to the env.exe
patch is provided in bug 3602534.
Remove this binary from the system once the Oracle HTML DB installation is complete.
To find and download patches:
Go to the OracleMetaLink Web site
http://metalink.oracle.com/
Log in to OracleMetaLink.
Note: If you are not an OracleMetaLink registered user, then click Register for MetaLink! and follow the registration instructions. |
Select Patches on the main OracleMetaLink page.
Select Simple Search.
Specify the following information, then click Go:
In the Search By field, choose Patch Number(s), and enter 3602534.
In the Platform or Language field, select Microsoft Windows (64-bit).
Review the installation instructions by clicking View README.
Return to the patch download page and click Download. Save the patch to a location in the PATH
. For example, ORACLE_BASE
\
ORACLE_HOME
\bin
.
If you choose to perform a software only install in a RAC environment no configurations tools will be executed by Oracle Universal Installer, this includes Virtual IP Configuration Assistant (VIPCA), Network Configuration Assistant and Database Configuration Assistant.
If you decide to run Network Configuration Assistant and or Database Configuration Assistant after the installation, you must first configure and start the VIPs, GSD and ONS applications by running VIPCA. You run VIPCA only once for the cluster.
To start VIPCA execute vipca.bat
from the ORACLE_BASE
\
ORACLE_HOME
\bin
directory.