| Oracle® Database Platform Guide 10g Release 1 (10.1) for Windows Part Number B10113-02 |
|
|
View PDF |
| Oracle® Database Platform Guide 10g Release 1 (10.1) for Windows Part Number B10113-02 |
|
|
View PDF |
Oracle Database 10g Release 1 (10.1) for 64-bit Windows supports 64-bit processing in the following operating systems:
Windows XP 64-bit Edition Version 2003
Windows Server 2003 for 64-bit Itanium 2 Systems
This appendix contains:
The following features of Oracle Database, documented elsewhere in this guide, are not currently supported in the 64-bit version:
Oracle Enterprise Manager Grid Control CD
Oracle Enterprise Manager Console (Java-based)
Oracle Migration Workbench
Oracle Objects for OLE
Oracle Data Provider for .NET (ODP.NET)
Oracle Open Gateways
Oracle Transparent Gateways
|
Note: A 64-bit version of Oracle Enterprise Manager Grid Control is not available in this release. Use Oracle Enterprise Manager Grid Control from your 64-bit Solaris system to manage the 64-bit computer nodes remotely. |
|
See Also: Oracle Database Release Notes for Windows for a complete list of unsupported features in Oracle Database for 64-bit Windows |
Oracle Database for 64-bit Windows does not support Very Large Memory (VLM) configurations. VLM enables the address space for 32-bit computers to expand beyond its default value of 2 to the power 32 bytes. But the default address space for 64-bit computers is already 2 to the power 64 bytes. So a 64-bit computer does not need VLM.
Neither Windows XP 64-bit Edition Version 2003 nor Windows Server 2003 for 64-bit Itanium 2 Systems support 4 GB RAM Tuning, so it is not available in Oracle Database for 64-bit Windows.
Pro*COBOL, Oracle Portal, and Oracle Migration Workbench are not supported in Oracle Database for 64-bit Windows.
Legato Networker is supported in this release of Oracle Database for 64-bit Windows.
Oracle Database for 64-bit Windows supports enterprise users and roles stored in Oracle Internet Directory, but administration tools must be run from a 32-bit computer.
To enable large page support, the system administrator must grant the "Lock pages in memory" privilege to the oracle user. This privilege is not enabled by default when Windows is installed. To grant this privilege:
Choose Start > Settings > Control Panel.
The Control Panel window opens.
Double-click Administrative Tools.
The Administrative Tools window opens.
Double-click Local Security Policy.
The Local Security Settings window opens.
In the left pane of the Local Security Settings window, expand Local Policies and select User Rights Assignment.
In the right pane of the Local Security Settings window, select Lock pages in memory and choose Action > Security...
The Local Security Policy Setting dialog opens.
Click Add...
The Select Users or Groups dialog opens.
Select the oracle user from the Name list.
Click Add.
Click OK to close the Select Users or Groups dialog.
Click OK to close the Local Security Policy Setting dialog.
To take advantage of large pages on Windows Server 2003, the amount of physical memory must be greater than the amount of System Global Area (SGA) specified in the parameter file.
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. |
|
See Also: Your operating system documentation for restrictions on allocating large pages. |
To enable large page support:
Go to ORACLE_BASE\ORACLE_HOME\bin\oracle.key.
Open oracle.key in a text editor and record the value found. It is set by Oracle Universal Installer. The default is:
SOFTWARE\ORACLE\KEY_HOME_NAME
Start Registry Editor at the command prompt:
C:\> regedit
|
Note: Although Registry Editor lets you view and modify registry keys and parameter values, you normally are not required to do so. In fact, you can render your system useless if you make incorrect changes. Therefore, only advanced users should edit the registry! Back up your system before making any changes in the registry. |
Go to HKEY_LOCAL_MACHINE.
Find the key corresponding to the value found in oracle.key. In the default case, for example, you would look for:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_HOME_NAME
Create one of the following, depending on where you want to enable large page support:
ORA_LPENABLE=1 to enable large page support on all instances
ORA_SID_LPENABLE=1 to enable large page support on a specific instance
Exit Registry Editor.
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.
|
Caution: Do not set initialization parameterlock_sga when large pages are enabled. Large page usage locks the entire SGA into physical memory. When used with parameter lock_sga, 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. |
This section contains these topics:
|
See Also: Oracle Database Upgrade Guide |
To back up a 32-bit Oracle home database:
Start SQL*Plus:
C:\> sqlplus /NOLOG
Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;
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;
Shut down the database:
SQL> SHUTDOWN IMMEDIATE;
Perform a full offline backup of the database.
To migrate an Oracle Database 10g Release 1 (10.1) database for 32-bit Windows to an Oracle Database 10g Release 1 (10.1) database for 64-bit Windows:
Install Oracle Database 10g Release 1 (10.1) for 64-bit Windows.
Create the new Oracle Database 10g Release 1 (10.1) service at the command prompt:
C:\> ORADIM -NEW -SID SID [-INTPWD PASSWORD ]-MAXUSERS USERS -STARTMODE AUTO -PFILE ORACLE_HOME\DATABASE\INITSID.ORA
The following table provides more information on the values you must supply.
| Parameter | Description |
|---|---|
SID |
SID of the database you are upgrading |
PASSWORD |
Password for the new Oracle Database 10g Release 1 (10.1) for 64-bit Windows database. 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 no password is required. |
USERS |
Maximum number of users who can be granted SYSDBA and SYSOPER privileges |
ORACLE_HOME |
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 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., where SID is your Oracle instance ID.
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.
Remove this parameter from the initialization file after the word size change is complete.
|
See Also: Oracle Database Upgrade Guide for more information on changing word size |
Go to the 64-bit ORACLE_HOME\rdbms\admin directory from the command prompt.
Start SQL*Plus:
C:\> sqlplus /NOLOG
Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;
Re-create the 64-bit control files using the CREATE CONTROLFILE command. Edit the trace file created in "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.
Here is an example of a database named "orcl32" on a 32-bit computer migrating to "orcl64" on a 64-bit computer:
CREATE CONTROLFILE REUSE DATABASE "T1" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 32
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 'C:\oracle\product\10.1.0\oradata\orcl64\REDO03.LOG' SIZE 1M,
# was 'C:\oracle\product\10.1.0\oradata\orcl32\...LOG'
# on the 32-bit computer
GROUP 2 'C:\oracle\product\10.1.0\oradata\orcl64\REDO02.LOG' SIZE 1M,
GROUP 3 'C:\oracle\product\10.1.0\oradata\orcl64\REDO01.LOG' SIZE 1M
DATAFILE
'C:\oracle\product\10.1.0\oradata\orcl64\SYSTEM01.DBF',
# was 'C:\oracle\product\10.1.0\oradata\orcl32\...DBF'
# on the 32-bit computer
'C:\oracle\product\10.1.0\oradata\orcl64\RBS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\USERS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\TEMP01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\TOOLS01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\INDX01.DBF',
'C:\oracle\product\10.1.0\oradata\orcl64\DR01.DBF'
CHARACTER SET WE8ISO8859P1;
Alter the init file from the 32-bit computer to include the new control file generated in the preceding step.
Start the database in RESTRICT mode:
SQL> STARTUP RESTRICT;
You might need to use the PFILE option to specify the location of your initialization parameter file.
Set the system to spool results to a log file for later verification of success. For example:
SQL> SPOOL catoutw.log
Enter the following command to view the output of the script on-screen:
SQL> SET ECHO ON;
Recompile existing PL/SQL modules in the format required by the 64-bit Oracle9i database:
SQL> @utlirp.sql;
Turn off the spooling of script results to the log file:
SQL> SPOOL OFF;
Check the spool file and verify that the packages and procedures compiled successfully. Correct any problems you find in this file.
If you were viewing the output of catoutw.log on-screen, disable viewing now:
SQL> SET ECHO OFF;
Exit the RESTRICT database mode:
SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION;
The word size of the 64-bit Oracle Database 10g Release 1 (10.1) database is changed. You can open the database for normal use.
To migrate an Oracle9i or older database to an Oracle Database 10g Release 1 (10.1) database for 64-bit Windows:
Perform steps 1 - 11 in "Migrating an Oracle Database 10g Release 1 (10.1) Database".
Shut down the database on the 64-bit computer:
SQL> SHUTDOWN IMMEDIATE;
Start the database migration:
SQL> STARTUP MIGRATE;
Migrate the database as described in Chapter 3, "Upgrading a Database to the New Oracle Database 10g Release" in Oracle Database Upgrade Guide.
Shut down the database:
SQL> SHUTDOWN IMMEDIATE;
Restart the database:
SQL> STARTUP MOUNT;
Use Oracle 64-bit components to create your applications. 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: NCHAR columns in user tables are not changed during the migration. To change NCHAR columns in user tables, refer to "Upgrade User NCHAR Columns" in Oracle Database Upgrade Guide. |
The Oracle Database Online Documentation Library CD-ROM for Windows is not shipped with Oracle Database for 64-bit Windows. Everything in the library is available for download from the Oracle Technology Network (OTN) at http://otn.oracle.com/documentation/
You must register online before using OTN; registration is free and can be done at http://otn.oracle.com/membership/.
