You might need to use the PFILE option to specify the location of your initialization parameter file. Start the database in RESTRICT mode: SQL> STARTUP RESTRICT 'C:\oracle\product\10.1.0\oradata\orcl64\DR01.DBF'Īlter the init file from the 32-bit computer to include the new control file generated in the preceding step. 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 This creates the new control file in ORACLE_HOME \database. 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. Re-create the 64-bit control files using the CREATE CONTROLFILE command. Go to the 64-bit ORACLE_HOME \rdbms\admin directory from the command prompt.Ĭonnect to the database instance as SYSDBA: SQL> CONNECT / AS SYSDBA
See Also: Oracle Database Upgrade Guide for more information on changing word size Remove this parameter from the initialization file after the word size change is complete. 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. ora., where SID is your Oracle instance ID.
The default 32-bit password file is located in ORACLE_BASE \ ORACLE_HOME \database\pwd SID. 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. 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.
Ensure that you specify the full path name with the -PFILE option, including drive letter of the Oracle home directory.Ĭopy the 32-bit datafiles to the new 64-bit Oracle home.Ĭopy the 32-bit configuration files to the 64-bit Oracle home. Maximum number of users who can be granted SYSDBA and SYSOPER privileges If you do not specify it, then operating system authentication is used, and no password is required. This is the password for the user connected with SYSDBA privileges.
Password for the new Oracle Database 10 g Release 1 (10.1) for 64-bit Windows database. 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. 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. Select the oracle user from the Name list.Ĭlick OK to close the Select Users or Groups dialog.Ĭlick OK to close the Local Security Policy Setting dialog.
The Local Security Policy Setting dialog opens. In the right pane of the Local Security Settings window, select Lock pages in memory and choose Action > Security.
In the left pane of the Local Security Settings window, expand Local Policies and select User Rights Assignment. The Local Security Settings window opens. This privilege is not enabled by default when Windows is installed. To enable large page support, the system administrator must grant the "Lock pages in memory" privilege to the oracle user. G.6 Large Page Support for 64-bit Windows