Changing the Word Size of Your Current Release

The instructions in this section guide you through the process of changing the word size of your current release (switching from 32-bit software to 64-bit software or switching from 64-bit software to 32-bit software).


Complete the following steps to change the word size of your current release:

1. Start SQL*Plus.

2. Connect to the database instance as a user with SYSDBA privileges.

3. Run SHUTDOWN IMMEDIATE on the database:

SQL> SHUTDOWN IMMEDIATE

Note:

For Oracle9i Real Application Clusters, issue this statement for all instances. Also, set the CLUSTER_DATABASE initialization parameter to false. You can change it back to true after the change in word size is complete.

4. Perform a complete backup of the database.

See Also:

Oracle9i User-Managed Backup and Recovery Guide for more information

5. If you are using the same Oracle home for your current release and the release to which you are switching, then deinstall your current release using the Oracle Universal Installer. You do not need to deinstall your current release if you are using separate Oracle home directories.

6. If you currently have a 32-bit installation, then install the 64-bit release. Or, if you currently have a 64-bit installation, then install the 32-bit release.

Note:

Installation and deinstallation are operating system-specific. For installation and deinstallation instructions, see your Oracle9i operating system-specific installation documentation and the Oracle9i README for your operating system.

7. Copy configuration files to a location outside of the old Oracle home:
- If your parameter file resides within the old environment's Oracle home, then copy it to a location outside of the old environment's Oracle home. The parameter file can reside anywhere you wish, but it should not reside in the old environment's Oracle home after you switch to the new release.
- If your parameter file has an IFILE (include file) entry and the file specified in the IFILE entry resides within the old environment's Oracle home, then copy the file specified by the IFILE entry to a location outside of the old environment's Oracle home. The file specified in the IFILE entry has additional initialization parameters. After you copy this file, edit the IFILE entry in the parameter file to point to its new location.
- If you have a password file that resides within the old Oracle home, then move or copy the password file to the new Oracle9i Oracle home. The name and location of the password file are operating system-specific; for example, on UNIX platforms, the default password file is ORACLE_HOME/dbs/orapwsid, but on Windows operating systems, the default password file is ORACLE_HOME\database\pwdsid.ora. In both cases, sid is your Oracle instance ID.

Note:

For Oracle9i Real Application Clusters, perform this step on all nodes. Also, if your initdb_name.ora file resides within the old environment's Oracle home, then move or copy the initdb_name.ora file to a location outside of the old environment's Oracle home.

8. At a system prompt, change to the ORACLE_HOME/rdbms/admin directory.

9. Start SQL*Plus.

10. Connect to the database instance as a user with SYSDBA privileges.

11. Run STARTUP MIGRATE:

SQL> STARTUP MIGRATE

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

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

SQL> SPOOL wordsize.log

13. Run utlirp.sql:

SQL> @utlirp.sql

The utlirp.sql script recompiles existing PL/SQL modules in the format required by the new database. This script first alters certain dictionary tables. Then, it reloads the STANDARD and DBMS_STANDARD packages, which are necessary for using PL/SQL. Finally, it triggers a recompile of all PL/SQL modules, such as packages, procedures, types, and so on.


14. Turn off the spooling of script results to the log file:

SQL> SPOOL OFF

Then, check the spool file and verify that the packages and procedures compiled successfully. You named the spool file in Step 12; the suggested name was wordsize.log. Correct any problems you find in this file.

15. Run ALTER SYSTEM DISABLE RESTRICTED SESSION:

SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION;

The word size of your database is now changed. You can open the database for normal use.