|Oracle9i Database and Client Release Notes
Release 2 (184.108.40.206.1) for 64-Bit Windows
Part Number B10694-02
Part No. B10694-02
The information in these Release Notes is current as of the release date for Oracle9i Database release 2 (220.127.116.11.1) for 64-bit Windows. For the most current information, refer to the online Release Notes located on Oracle Technology Network (OTN) at
This document contains these topics:
Table 1 lists the system requirements.
Itanium 2 or higher
Oracle9i for Windows is supported on the following operating systems:
1 GB RAM (minimum)
512 MB (minimum)
3-D graphics (recommended)
Hard Disk Space (NTFS)
This section contains these topics:
The following components do not ship with 64-bit Windows:
Oracle9i provides two features which make use of a directory server:
Directory Naming with Active Directory is not supported at the time of this release, but will be supported in a future patch set. Enterprise User Security with Active Directory is not supported in this release.
To use Advanced Security Options (ASO):
At the time of this release Microsoft documentation states that automatic mounting is enabled by default, however this feature is disabled by default.
Automatic mounting should be enabled for:
Check the current setting of automatic mounting by executing the
DiskPart command from the MS-DOS prompt and issuing the
automount command at the
Oracle Corporation recommends setting of the automatic mounting feature before creating any logical partitions for use by the database or the Cluster File system. If you have already created logical partitions you must restart all nodes after enabling this feature.
When using JDK 1.4.1 or later Oracle Corporation recommends:
jre\libdirectory and the
When running Oracle Database Configuration Assistant in Korean or Traditional Chinese locales, the right pane of the Database Storage screen shows square boxes instead of Korean or Traditional Chinese characters. Select an item from the left pane in order to change and view information about control files, tablespaces, datafiles, rollback segments, or redo log groups. Click Next to continue or click Finish to create the database.
INSO Filter is not supported in this release. For a workaround see OTN at
To enable large page support, the system administrator must use Local Security Policy editor to grant the "Lock pages in memory" privilege. This privilege is not enabled by default when Windows is installed.
To grant this privilege go to Start > Settings > Control Panel > Administrative Tools > Local Security Policy.
Expand Local policies and select User Rights Assignment.
To take advantage of large pages on Windows Server 2003 the amount of physical memory should be greater than the amount of System Global Area (SGA) specified in the parameter file. Check the restrictions on allocating large pages in the Windows documentation.
To enable large pages for SGA on an Oracle instance, set instance-specific registry parameter
Large pages may not be allocated at all times during instance startup; either all of the SGA is allocated using large pages or all of SGA is allocated using regular pages.
By default Oracle allocates the minimum available large page size when using large pages. The minimum available large page size, 16 MB, is obtained by using the
To set the size for
The value in
\bin\oracle.key is set by Oracle Universal Installer. The default value in
ORA_LPENABLE to enable large page support on all the instances on the computer. Create
_LPENABLE and to enable large page support on specific instances.
Do not set initialization parameter
lock_sga when large pages are enabled. Large page usage locks the entire SGA into physical memory. When used with parameter
lock_sga, the database startup fails with an error because the operating system automatically locks. That is, it prevents memory from being paged to disk when large pages are requested. Physical memory is not released during a shrink operation.
Do not set initialization parameter
Legato NetWorker is not bundled with this release. The latest information on Legato NetWorker certifications, and the documentation can be found at
http://www.legato.com/lssv. This site also contains any product updates for the NetWorker.
J2SE 1.4.1 SDK (interpreted mode) is bundled with this release. When J2SE 1.4.2 SDK is available from Sun, customers using this release of Oracle9i Database for 64-bit Windows are required to perform a mandatory upgrade.
Before using Oracle for Windows Performance Monitor to view Oracle-specific counters, you must specify the
SYSTEM password using
operfcfg.exe located in the
To set the
SYSTEM password, enter the following command:
Oracle Cluster File System is not supported at the time of this release. A production version of Oracle Cluster File System will be available as a patch update for this product.
A 64-bit version of Oracle Directory Manager is not available in this release. Use Oracle Directory Manager from your 32-bit computer to create and manage enterprise users and their roles on the 64-bit computer remotely.
Oracle Enterprise Login Assistant is not supported in this release. Use Oracle Wallet Manager to create a single sign-on wallet.
A 64-bit version of Oracle Enterprise Security Manager is not available in this release. Use Oracle Enterprise Security Manager from your 32-bit computer to create and manage enterprise users and their roles on the 64-bit computer remotely.
Oracle Corporation does not support the use of Oracle HTTP Server, bundled with this release, as a general purpose Web server. Oracle Corporation recommends the use of Oracle HTTP Server included in this release to support browser-based functionality for Oracle components such as iSQL*Plus, Oracle Ultra Search, and Oracle Workflow.
Release 18.104.22.168.0 specific patches for Oracle interMedia and Oracle Spatial are not applied in the seed databases or with any database created with Database Configuration Assistant. To apply these patches, connect as
SYS and run the following SQL scripts:
Oracle Migration Workbench can be executed from a 32-bit Windows environment to migrate third party databases, as supported by release 22.214.171.124.2 or higher, to an Oracle9i database installed on a 64-bit computer.
The Oracle Workflow Builder and Notification Mailer features of Oracle Workflow Server are not available in this release. However, using Oracle Workflow Builder from a 32-bit computer to connect to a 64-bit computer is supported.
When creating a database with the AL32UTF8 character set, and the Oracle JVM and Oracle XML DB options, the minimum recommended
java_pool_size is 200 MB. If these values are lower than 200 MB, then the Oracle Server may return an ORA-04031 error.
OracleDriveLetterService is a temporary service used by Oracle Cluster Setup Wizard,
clustersetup.exe, when installing Oracle Cluster File System.
OracleDriveLetterService could be left in a running state after executing Oracle Cluster Setup Wizard. Although the service has been marked for deletion, the service is not removed by the system until it is stopped.
OracleDriveLetterService is listed as running after Cluster Setup Wizard has completed, execute the following command at the MS-DOS prompt to stop the service and allow the system to delete it.
Check all nodes which were a part of the installation to verify that the
OracleDriveLetterService has stopped.
Virtual Interface Architecture (VIA) network interconnect technology is not supported with Real Application Clusters in this release.
Oracle Home Selector is no longer available from the Start Menu. Similar functionality is available through Oracle Universal Installer.
Release 126.96.36.199.0 of Oracle Universal Installer is bundled with Oracle9i release 2 (188.8.131.52.1) for 64-bit Windows.
This section describes database and application migration from a 32-bit Windows computer:
This section contains these topics:
To back up the 32-bit Oracle home database:
.trcfile to use as a template to re-create the control files on the 64-bit computer.
This section describes the migration of an Oracle9i database for 32-bit Windows to an Oracle9i database for 64-bit Windows.
To migrate into the 64-bit Oracle9i home:
This syntax includes the following variables:
SIDis the same
SIDname as the
SIDof the database you are upgrading.
PASSWORDis the password for the new Oracle9i Database for 64-bit Windows. This is the password for the user connected with
-INTPWDoption is not required. If you do not specify it, then operating system authentication is used, and no password is required.
USERSis the maximum number of users who can be granted
ORACLE_HOMEis the release 9.2 Oracle home directory. Ensure that you specify the full path name with the
-PFILEoption, including drive letter of the Oracle home directory.
IFILE(include file) entry, then copy the file specified by the
IFILEentry to the 64-bit Oracle home and edit the
IFILEentry in the initialization parameter file to point to its new location.
SIDis your Oracle instance ID.
falseparameter to the
\init.orafile before changing the word size.
\rdbms\admindirectory from the command prompt.
CONTROLFILEcommand. Edit the trace file created in step 3 of "Backing up a 32-bit Oracle Database" to change the paths to the datafiles, log files and control files to point to the Oracle home on the 64-bit computer. This creates the new control file in
CREATE CONTROLFILE REUSE DATABASE "T1" NORESETLOGS NOARCHIVELOG MAXLOGFILES 32 MAXLOGMEMBERS 2 MAXDATAFILES 32 MAXINSTANCES 16 MAXLOGHISTORY 1815 LOGFILE GROUP 1 'C:\ORACLE\DATABASE\T1\REDO03.LOG' SIZE 1M, # was 'C:\ORACLE_817\...LOG' on the 32-bit machine GROUP 2 'C:\ORACLE\DATABASE\T1\REDO02.LOG' SIZE 1M, GROUP 3 'C:\ORACLE\DATABASE\T1\REDO01.LOG' SIZE 1M DATAFILE 'C:\ORACLE\DATABASE\T1\SYSTEM01.DBF', # was 'C:\ORACLE_ 817\...DBF' on the 32-bit machine 'C:\ORACLE\DATABASE\T1\RBS01.DBF', 'C:\ORACLE\DATABASE\T1\USERS01.DBF', 'C:\ORACLE\DATABASE\T1\TEMP01.DBF', 'C:\ORACLE\DATABASE\T1\TOOLS01.DBF', 'C:\ORACLE\DATABASE\T1\INDX01.DBF', 'C:\ORACLE\DATABASE\T1\DR01.DBF' CHARACTER SET WE8ISO8859P1;
initfile from the 32-bit computer to include the new control file generated in step 10.
You may need to use the
PFILE option to specify the location of your initialization parameter file.
The word size of the 64-bit Oracle9i database is changed. You can open the database for normal use.
This section describes the migration of a pre-Oracle9i Database for 32-bit Windows to an Oracle9i Database for 64-bit Windows.
Then perform the following steps on the 64-bit computer:
To create your applications, use Oracle 64-bit components. To migrate your business logic, refer to Migration Tips on the Microsoft Developer Network (MSDN) Web site at
For more information, refer to your 32-bit Oracle9i Online Documentation at
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 Corporation 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
This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Oracle is a registered trademark, and iSQL*Plus, Oracle9i, Oracle Names, Oracle Open Gateways, Oracle Procedural Gateway, PL/SQL, Pro*COBOL and SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved.
Copyright © 2002, 2003 Oracle Corporation.
All Rights Reserved.