Skip Headers

Oracle9i Database and Client Release Notes
Release 2 (9.2.0.2.1) for 64-Bit Windows

Part Number B10694-02

Oracle9i

Database and Client Release Notes

Release 2 (9.2.0.2.1) for 64-Bit Windows

April 2003

Part No. B10694-02

The information in these Release Notes is current as of the release date for Oracle9i Database release 2 (9.2.0.2.1) for 64-bit Windows. For the most current information, refer to the online Release Notes located on Oracle Technology Network (OTN) at http://otn.oracle.com/.

This document contains these topics:

1 System Requirements

Table 1 lists the system requirements.

Table 1 System Requirements  
Component Requirement

Processor

Itanium 2 or higher

Operating System

Oracle9i for Windows is supported on the following operating systems:

  • Windows Server 2003 Datacenter Edition for 64-bit Itanium 2 Systems

  • Windows Server 2003 Enterprise Edition for 64-bit Itanium 2 Systems

  • Windows XP 64-bit Edition Version 2003

Memory

1 GB RAM (minimum)

Virtual Memory

512 MB (minimum)

Video

VGA (minimum)

3-D graphics (recommended)

Hard Disk Space (NTFS)

3.2 GB

2 Known Limitations and Workarounds

This section contains these topics:

2.1 Components Not Supported on 64-Bit Windows

The following components do not ship with 64-bit Windows:

2.2 Active Directory Integration

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.

2.3 Advanced Security Option

To use Advanced Security Options (ASO):

  1. Add the JRE directory location to the system path. The default JRE location is:

    C:\Program Files\Oracle\jre\1.4.1\bin\server

  2. Restart the OracleServiceSID.

2.4 Enabling Automatic Mounting

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 DiskPart prompt.

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.

See Also:

Microsoft documentation for more information about DiskPart

2.5 Enabling Secure Socket Layer

When using JDK 1.4.1 or later Oracle Corporation recommends:

2.6 Globalization Support in Database Configuration Assistant

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.

2.7 INSO Filter

INSO Filter is not supported in this release. For a workaround see OTN at http://otn.oracle.com/products/text/htdocs/FilterServer.htm.

2.8 Large Page Support

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 ORA_SID_LPENABLE=1 or ORA_LPENABLE=1.

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.


Note:

Large page usage locks the entire SGA into physical memory. Physical memory is not released during a shrink operation.


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 GetLargePageMinumum function.

To set the size for ORA_SID_LPENABLE or ORA_LPENABLE:

  1. Start the Registry Editor at the command prompt:

    C:\> regedit
    
    
  2. Go to HKEY_LOCAL_MACHINE\value in oracle.key

    The value in ORACLE_HOME\bin\oracle.key is set by Oracle Universal Installer. The default value in oracle.key is SOFTWARE\ORACLE\Home0.

  3. Create the following keys based on your needs:

    Create ORA_LPENABLE to enable large page support on all the instances on the computer. Create ORA_SID_LPENABLE and to enable large page support on specific instances.

  4. Exit the Registry Editor.


    Caution:

    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.


2.9 Legato NetWorker

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.

2.10 Mandatory Upgrade to J2SE 1.4.2 SDK

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.

2.11 Oracle Counters for Windows Performance Monitor

Before using Oracle for Windows Performance Monitor to view Oracle-specific counters, you must specify the SYSTEM password using operfcfg.exe located in the ORACLE_HOME\bin directory.

To set the SYSTEM password, enter the following command:

C:\> operfcfg.exe -U SYSTEM -P PASSWORD [-D DATABASE_NAME]

2.12 Oracle Cluster File System

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.

2.13 Oracle Directory Manager

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.

See Also:

Oracle Enterprise Manager Concepts Guide for more information

2.14 Oracle Enterprise Login Assistant

Oracle Enterprise Login Assistant is not supported in this release. Use Oracle Wallet Manager to create a single sign-on wallet.

See Also:

"Using Auto Login" in Oracle Advanced Security Administrator's Guide for more information

2.15 Oracle Enterprise Manager

A 64-bit version of Oracle Enterprise Manager is not available in this release. Use Oracle Enterprise Manager from your 32-bit computer to manage the 64-bit computer nodes remotely.

See Also:

Oracle Enterprise Manager Configuration Guide for more information

2.16 Oracle Enterprise Security Manager

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.

See Also:

Oracle Enterprise Manager Concepts Guide for more information

2.17 Oracle HTTP Server

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.

2.18 Oracle interMedia and Oracle Spatial

Release 9.2.0.2.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_BASE\ORACLE_HOME\md\admin\sdopath.sql 
ORACLE_BASE\ORACLE_HOME\ord\im\admin\impatch.sql

2.19 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.2 or higher, to an Oracle9i database installed on a 64-bit computer.

2.20 Oracle Workflow Server

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.

2.21 Shared Pool Size

When creating a database with the AL32UTF8 character set, and the Oracle JVM and Oracle XML DB options, the minimum recommended shared_pool_size and java_pool_size is 200 MB. If these values are lower than 200 MB, then the Oracle Server may return an ORA-04031 error.

2.22 Stopping OracleDriveLetterService

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.

If the 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.

C:\> net stop OracleDriveLetterService

Check all nodes which were a part of the installation to verify that the OracleDriveLetterService has stopped.

2.23 Virtual Interface Architecture (VIA)

Virtual Interface Architecture (VIA) network interconnect technology is not supported with Real Application Clusters in this release.

3 Oracle Home Selector

Oracle Home Selector is no longer available from the Start Menu. Similar functionality is available through Oracle Universal Installer.

See Also:

"Database Tools for 64-Bit Windows" in Oracle9i Database Platform Guide for Windows

4 Oracle Universal Installer

Release 2.2.1.8.0 of Oracle Universal Installer is bundled with Oracle9i release 2 (9.2.0.2.1) for 64-bit Windows.

5 Migration

This section describes database and application migration from a 32-bit Windows computer:

5.1 Database Migration

This section contains these topics:

5.1.1 Backing up a 32-Bit Oracle Database

To back up the 32-bit Oracle home database:

  1. Start SQL*Plus:

    C:\> sqlplus / NOLOG
    
    
  2. Connect to the database instance AS SYSDBA:

    SQL> CONNECT / AS SYSDBA
    
    
  3. Create a .trc file to use as a template to re-create the control files on the 64-bit computer.

    SQL> Alter database backup controlfile to trace
    
    
  4. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE
    
    
  5. Perform a full offline backup of the database.

    .

    See Also:

    Oracle9i User-Managed Backup and Recovery Guide for more information


    Note:

    NCHAR columns in user tables are not changed during the migration. To change NCHAR columns in user tables, refer to "Upgrade User NCHAR Columns" of Oracle9i Database Migration.


5.1.2 Migrating an Oracle9i Database

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:

  1. Install Oracle9i Database release 2 (9.2.x) for 64-bit Windows.

    See Also:

    Oracle9i Database Installation Guide for Windows for more information

  1. 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
    
    

This syntax includes the following variables:

  1. Copy the 32-bit datafiles to the new 64-bit Oracle home.

  2. 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 that resides 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\pwdSID.ora. The SID is your Oracle instance ID.

  1. In the 64-bit Oracle home, add the _SYSTEM_TRIG_ENABLED = false parameter to the ORACLE_HOME\database\ORACLE_SID \init.ora file before changing the word size.

  2. Remove this parameter from the initialization file after the word size change is complete.

    See Also:

    Oracle9i Database Migration for more information on changing word size

  1. Go to the 64-bit ORACLE_HOME\rdbms\admin directory from the command prompt.

  2. Start SQL*Plus as follows:

    C:\> sqlplus / NOLOG 
    
    
  3. Connect to the database instance AS SYSDBA:

    SQL> CONNECT / AS SYSDBA
    
    
  4. Re-create the 64-bit control files using the CREATE CONTROLFILE command. 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 ORACLE_HOME\database.

Example:


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;

  1. Alter the init file from the 32-bit computer to include the new control file generated in step 10.

  2. Start the database in RESTRICT mode:

    SQL> STARTUP RESTRICT
    
    

You may need to use the PFILE option to specify the location of your initialization parameter file.

  1. Set the system to spool results to a log file for later verification of success. For example:

    SQL> SPOOL catoutw.log
    
    
  2. Enter the following command to view the output of the script on-screen:

    SQL> SET ECHO ON
    
    
  3. Recompile existing PL/SQL modules in the format required by the 64-bit Oracle9i database:

    SQL> @utlirp.sql;
    
    
  4. Turn off the spooling of script results to the log file:

    SQL> SPOOL OFF
    
    
  5. Check the spool file and verify that the packages and procedures compiled successfully. Correct any problems you find in this file.

  6. If you specified SET ECHO ON, then SET ECHO OFF now:

    SQL> SET ECHO OFF
    
    
  7. Exit the RESTRICT database mode:

    SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION;
    
    

The word size of the 64-bit Oracle9i database is changed. You can open the database for normal use.

5.1.3 Migrating a pre-Oracle9i Database

This section describes the migration of a pre-Oracle9i Database for 32-bit Windows to an Oracle9i Database for 64-bit Windows.

Perform steps 1 - 11 in, "Migrating an Oracle9i Database."

Then perform the following steps on the 64-bit computer:

  1. Shut down the database:

    SQL> SHUTDOWN IMMEDIATE
    
    
  2. Start the database migration:

    SQL> STARTUP MIGRATE
    
    
  3. Migrate the database as described in Chapter 3, "Upgrading a Database to the New Oracle9i Release" in Oracle9i Database Migration

  4. Shut down and start the database.

    SQL> SHUTDOWN IMMEDIATE
    SQL> STARTUP MOUNT
    

5.2 Application Migration

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 http://msdn.microsoft.com/default.asp.


Note:

NNCHAR columns in user tables are not changed during the migration. To change NCHAR columns in user tables, refer to "Upgrade User NCHAR Columns" of Oracle9i Database Migration.


6 Related Documentation

For more information, refer to your 32-bit Oracle9i Online Documentation at http://otn.oracle.com/documentation/.

7 Documentation Accessibility

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 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 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.


Oracle
Copyright © 2002, 2003 Oracle Corporation.

All Rights Reserved.