Oracle8i Migration
Release 3 (8.1.7)
Part Number A86632-01

Library
Product
Contents
Index

Go to previous page Go to next page

7
Upgrading from a Previous Version 8 Release to the New Oracle8i Release

This chapter contains information about upgrading your current release of Oracle to the new Oracle8i release. The information in this chapter only applies to release 8.0 and higher installations of Oracle. If your current release is version 7 or version 6 and you want to migrate to Oracle8i, then follow the instructions at the beginning of this book, starting with Chapter 2, "Overview of Migration".

This chapter covers the following topics:

Upgrade Paths

The path that you must take to upgrade your database to the new release depends on the release you are currently using. Table 7-1 contains the upgrade path required for each old release of Oracle. Use the upgrade path and the documentation specified for the release you are running currently.

Table 7-1 Upgrade Paths
Old Release  Upgrade Path 

8.0.1 beta 

Direct upgrade is not supported. Complete the following steps to upgrade to the new release:

  1. Upgrade to release 8.0.2 using the instructions in the release 8.0.2 README.doc file.

  2. Upgrade the release 8.0.2 database to release 8.0.5 using the instructions in the release 8.0.5 README.doc file.

  3. Upgrade the release 8.0.5 database to the new release using the instructions in "Upgrading the Database to the New Oracle8i Release".

 

8.0.2 beta

8.0.4S 

Direct upgrade is not supported. Complete the following steps to upgrade to the new release:

  1. Upgrade the release 8.0.2 database to release 8.0.5 using the instructions in the release 8.0.5 README.doc file.

  2. Upgrade the release 8.0.5 database to the new release using the instructions in "Upgrading the Database to the New Oracle8i Release".

 

8.0.3

8.0.4

8.0.5

8.0.6

8.1.5

8.1.6 

Direct upgrade is supported. Upgrade to the new release using the instructions in "Upgrading the Database to the New Oracle8i Release". 

8.1.1 beta

8.1.2 beta 

Upgrading to the new release is not supported. 

8.1.3 beta

8.1.4 beta 

Direct upgrade is not supported. Complete the following steps to upgrade to the new release:

  1. Upgrade to release 8.1.5 using the instructions in the release 8.1.5 Oracle8i Migration book, Oracle part number A67774-01.

  2. Upgrade the release 8.1.5 database to the new release using the instructions in "Upgrading the Database to the New Oracle8i Release".

 

Upgrading the Database to the New Oracle8i Release

This section guides you through the process of upgrading your database to the new Oracle8i release.

Upgrading Oracle Parallel Server:

If you are upgrading a system with Oracle Parallel Server installed on a UNIX operating system, then most of the actions described in this chapter should be performed on only one node of the system. So, perform the actions described in this chapter on only one node unless instructed otherwise in a particular step.

If you are upgrading an Oracle Parallel Server on a Windows platform, do not follow the instructions in this chapter. Instead, follow the instructions for upgrading in the Oracle Parallel Server Administrator's Guide for Windows NT. 

Prepare to Upgrade

Complete the following steps to begin the upgrade process:

  1. Review upgrade issues relating to SQL*Net and Net8.

    See Also:

    Appendix F, "SQL*Net and Net8 Considerations for Migrations and Upgrades" for information. 

  2. Make sure your DB_DOMAIN initialization parameter is set properly.

    See Also:

    "The DB_DOMAIN Parameter" for more information about setting this initialization parameter. 

  3. Make sure the _SYSTEM_TRIG_ENABLED initialization parameter is set to FALSE in the initialization parameter file. If this initialization parameter is not currently set, then explicitly set it to FALSE: 

    _SYSTEM_TRIG_ENABLED = FALSE
  4. Start Server Manager.

  5. Connect to the database instance as INTERNAL user.

  6. If you are upgrading from an 8.0 release, then make sure no user or role has the name OUTLN, because this schema is created automatically when you install Oracle8i. If you have a user or role named OUTLN, then you must drop the user or role and recreate it with a different name.

    Note:

    If you are upgrading from an 8.1 release, then you do not need to perform this check because the OUTLN user should have been created when you installed the previous 8.1 release. Therefore, if you are upgrading from an 8.1 release, then go to Step 7 now. Do not drop the OUTLN user if you are upgrading from a previous 8.1 release. 

    To check for a user with the name OUTLN, enter the following SQL statement: 

    SELECT username FROM dba_users WHERE username = 'OUTLN';

    If you do not have a user named OUTLN, then zero rows are selected.

    To check for a role with the name OUTLN, enter the following SQL statement: 

    SELECT role FROM dba_roles WHERE role = 'OUTLN';

    If you do not have a role named OUTLN, then zero rows are selected.

  7. Add space to your SYSTEM tablespace and to the tablespaces where you store rollback segments, if necessary.

    Upgrading to a new release requires more space in your SYSTEM tablespace and in the tablespaces where you store rollback segments. If you have enough space on your system, then consider adding more space to these tablespaces. In general, you need at least 20 MB of free space in your SYSTEM tablespace to upgrade. If you run out of space during the upgrade, then you will need to perform the upgrade again.

    The following SQL statement illustrates how to add more space to a tablespace: 

    ALTER TABLESPACE system
   ADD DATAFILE '/home/user1/mountpoint/oradata/db1/system02.dbf'
   SIZE 20M;
  8. Determine the files that you will back up in Step 11 by issuing the following SQL statements: 

    SPOOL v8files.log;
SELECT member FROM v$logfile;
    
SELECT name FROM v$datafile;
    
SELECT value FROM v$parameter WHERE name = 'control_files';
    SPOOL OFF;

    The v8files.log spool file lists all of the files that you must back up in Step 11.

  9. Run SHUTDOWN IMMEDIATE on the database: 

    SVRMGR> SHUTDOWN IMMEDIATE

    If you are using Oracle Parallel Server, then shutdown all instances.

  10. If your operating system is Windows, then ensure all Oracle services are stopped.

    See Also:

    Your Administrator's Guide for Windows for information about stopping services. 

  11. Perform a full offline backup of the database. Make sure you back up the files listed in the v8files.log spool file that you generated in Step 8.

    Caution:

    If you encounter any problems with the UPGRADE, then you will need to restore the database from this backup. Therefore, make sure you back up your database now as a precaution. 

    See Also:

    Oracle8i Backup and Recovery Guide for more information about backing up a release 8.1 database, or see Oracle8 Backup and Recovery Guide for information about backing up a release 8.0 database. 

  12. Exit Server Manager.

  13. Deinstall your current release of Oracle if both of the following conditions are true:

    • You are upgrading from a previous 8.1 release.

    • You plan to use the same Oracle home for your current release and the new release to which you are upgrading.

    If you plan to use separate Oracle home directories for your current release and the new release to which you are upgrading, then you do not need to deinstall your current release.

    Note:

    If you are upgrading from an 8.0 release, then you must install the new 8.1 release in an Oracle home separate from the 8.0 release. However, if you are upgrading from a previous 8.1 release, then this restriction does not apply, and you can install the new release into the same Oracle home as the previous release if you wish. 

Upgrade the Database

Choose an upgrade method and then follow the instructions for upgrading using the method you have chosen.

See Also:

Some aspects of upgrading are operating system-specific. See your operating system-specific Oracle documentation for additional information about migrating. 

Choose an Upgrade Method

There are two ways to upgrade your database to release 8.1. You can either use the Oracle Data Migration Assistant to complete the upgrade, or you can perform the upgrade manually.

The Oracle Data Migration Assistant provides a completely automated upgrade of your database. You use a graphical user interface (GUI), which guides you through each step of the process. In addition, the Oracle Data Migration Assistant includes extensive online help. The Oracle Data Migration Assistant runs the appropriate upgrade script for your current release, deletes any obsolete initialization parameters from your initialization parameter file, and optionally configures your listener.ora file. See Appendix B, "Changes to Initialization Parameters" for lists of obsolete initialization parameters.

On the other hand, you lose some flexibility and control by using the Oracle Data Migration Assistant. If you want complete control over the upgrade process, especially with regard to setting initialization parameters, then you may want to perform the upgrade manually.

Caution:

The Oracle Data Migration Assistant cannot upgrade systems with Oracle Parallel Server installed. If you have Oracle Parallel Server installed, then you must upgrade the database manually. 

Decide which method you want to use to upgrade your database, and then complete the steps in one of the following sections accordingly:

Upgrade the Database Using the Oracle Data Migration Assistant

Complete the following steps to upgrade the database using the Oracle Data Migration Assistant:

  1. If you are using a UNIX operating system, then make sure you are logged in as a user with write permission to the ORACLE_HOME directory and all of its subdirectories.

  2. Follow the instructions in your operating system-specific Oracle documentation to prepare for installation and start the Oracle Universal Installer.

    If you need help at any screen or want to consult more documentation about the Oracle Universal Installer, then click the Help button to open the online help.

  3. At the Welcome screen of the Oracle Universal Installer, click Next. The File Locations screen appears.

  4. At the File Locations screen, complete the following steps:

    1. Do not change the text in the Source field. This is the location of files for installation

    2. If there is a Destination Name field, enter the name of a new Oracle home in this field.

    3. Enter the complete path of the Oracle home directory where you want to install the new release in the Destination Path field. Click the Browse button to navigate to the directory.

    4. Click Next.

    The Available Products screen appears.

  5. At the Available Products screen, select the Oracle8i server. The Oracle8i server is either Oracle8i Enterprise Edition or Oracle8i, depending on your installation medium. Then, click Next.

  6. At the Installation Types screen, choose an installation type. Then, click Next.

    If you chose Custom, the Available Product Components screen appears. Complete the following steps:

    1. Choose the product components you want to install. Then, click Next.

      Make sure you install all of the options you installed with the previous database, assuming you do not want to discontinue use of a particular option. For example, if you installed Oracle replication in the previous database, then you should install it in the new Oracle8i database.

    2. Respond to the remaining screens that enable you to specify your custom installation settings, until you reach the Upgrading or Migrating an Existing Database screen.

  7. At the Upgrading or Migrating an Existing Database screen, complete the following steps:

    1. Select the Upgrade or Migrate an Existing Database check box.

    2. Choose the database to upgrade.

    3. Click Next.

  8. At the Create Database screen, select the No option, indicating that you do not want to create a database because you are upgrading an existing database. Then, click Next.

  9. At the Summary screen, make sure all of the settings and choices are correct for your installation. Then, click Install. The Oracle Universal Installer performs the installation, which may take some time.

    When installation is complete, one or more assistants may be started. When the Oracle Data Migration Assistant is started, you are ready to proceed with the upgrade.

  10. At the Before You Migrate or Upgrade screen of the Oracle Data Migration Assistant (shown in Figure 7-1), make sure the database that you are upgrading meets the conditions specified. Then, click Next

    Figure 7-1 Before You Migrate or Upgrade Screen


    If you need help at any screen or want to consult more documentation about the Oracle Data Migration Assistant, then click the Help button to open the online help.

  11. At the Select a Database Instance screen, select the database instance of the database you are upgrading. Then, click Next.

    Note:

    The database you choose must be release 8.0 or higher. If the database is an Oracle7 or lower database, then you must complete a migration of the database, not an upgrade. If the database is an Oracle7 database, then exit the Oracle Data Migration Assistant, and see Chapter 2 to start the migration process. 

  12. At the Database Password and INIT.ORA File screen, complete the following steps:

    1. Make sure the specified new Oracle home is correct.

    2. Make sure the location of the initialization parameter file specified is the complete path to the initialization parameter file of the database that you are upgrading. If the location is incorrect, click the Browse button to navigate to the correct directory.

    3. Make sure the old Oracle home specified is the complete path to the Oracle home of the database you are upgrading.

    4. Click Next. The Choose Migration or Upgrade Type screen appears.

  13. Choose a upgrade type. Then, click Next.

    If you chose Custom, then respond to the screens that enable you to specify your custom migration settings until you reach the Backup Your Database screen. If you need help with any of the custom screens, click the Help button

  14. At the Backup Your Database screen, you have two options:

    • Choose "I have already backed up my database" if you completed a backup before running the Oracle Data Migration Assistant.

    • Choose "I would like this tool to back up the database" if you did not complete a backup. If you choose this option, then you can select the backup directory by clicking the Browse button.

    After you have made your choice, click Next.

  15. At the Start the Migration or Upgrade screen, make sure all of the specifications are correct. If anything is incorrect, then click Back until you can correct the specification. If everything is correct, then click Next.

    The Oracle Data Migration Assistant performs the upgrade. If the COMPATIBLE initialization parameter was not set prior to upgrading, then the assistant sets COMPATIBLE to 8.0.5. However, if COMPATIBLE was set prior to upgrading, then the original setting is retained after the migration. See Chapter 9, "Compatibility and Interoperability" for information about resetting the COMPATIBLE initialization parameter.

    You may encounter the following error message: 

    An error occured while upgrading your Oracle database. Check the log files 
to determine if the upgrade was successful.

    If you encounter this message, then complete the following steps:

    1. Click the OK button.

    2. Click the View Summary in the subsequent box that appears. If the errors are similar to the following, then you can ignore the messages: 

      ORA-00604: error occurred at eecursive SQL level 1
ORA-00001: unique constraint (SYSTEM.AQ$_QUEUES_CHECK) violated
ORA-06512: at "SYS.DBMS_AQADM", line 2023
ORA-06512: at line 2

    If other errors appear, then you must address these them accordingly.

    Caution:

    If you retain the old Oracle software, then never start the upgraded database with the old software. Only start the database with the executables in the new release 8.1 installation directory. 

  16. At the Listener.ora Migration Confirmation screen, click the Yes button if you want the assistant to modify your listener.ora file automatically, or click the No button if you do not want the assistant to modify the listener.ora file.

    Certain modifications are required to the listener.ora file for your database to work properly with Oracle Enterprise Manager. If you plan to use Oracle Enterprise Manager, then you should click the Yes button to automatically modify the listener.ora file. However, if you do not plan to use Oracle Enterprise Manager, then click the No button.

    If you click the Yes button, then the Oracle Data Migration Assistant modifies the listener.ora file in the following way:

    1. The assistant shuts down the old listener and the new Oracle8i listener.

    2. The assistant modifies the SID_DESC entry for the migrated database in the Oracle8i listener.ora file in one of the following ways:

      A simple case: Suppose the old listener.ora has the following SID_DESC entry: 

      ... 
   (SID_DESC = 
      (SID_NAME = ORCL) 
   ) 
...

      If the database name is SAL, the domain name is COM, and the Oracle home is /oracle/product/8.1, then the assistant adds the following entry: 

      ... 
   (SID_DESC = 
       (GLOBAL_DBNAME = sal.com) 
          (ORACLE_HOME = /oracle/product/8.1) 
          (SID_NAME = SAL) 
    ) 
...

      A more complicated case: Suppose the old listener.ora has the following SID_DESC entry: 

      ... 
   (SID_DESC = 
       (GLOBAL_DBNAME = an_entry) 
       (SID_NAME = ORCL) 
    ) 
...

      If an_entry does not match the GLOBAL_DBNAME of the migrated database, and if the database name is SAL, the domain name is COM, and the Oracle home is \oracle\product\8.1 on the D drive, then the assistant adds the following entry: 

      ... 
   (SID_DESC = 
       (GLOBAL_DBNAME = sal.com) 
          (ORACLE_HOME = d:\oracle\product\8.1) 
          (SID_NAME = SAL) 
    ) 
...

      This entry is the same as the entry in the simple case, but the assistant also adds the entry an_entry to the SERVICE_NAMES parameter in the listener.ora file. Therefore, the assistant changes the SERVICE_NAMES parameter to the following: 

      SERVICE_NAMES = sal.com, an_entry
    3. On Windows platforms, the assistant removes the entry of the migrated database from the old listener.ora file. The assistant does not perform this action on UNIX operating systems.

    4. The assistant starts up the Oracle8i listener.

  17. Complete the procedures described in "Upgrading Specific Components" and in Chapter 8, "After Migrating or Upgrading the Database".

    Caution:

    If you retain the old Oracle software, then never start the upgraded database with the old Oracle software. Only start the database with the executables in the new Oracle8i installation. Also, before you remove the old Oracle environment, make sure you relocate any datafiles in that environment to the new Oracle8i environment. See the Oracle8i Administrator's Guide for information about relocating datafiles. 

Running the Oracle Data Migration Assistant Independently

If you installed Oracle8i without specifying that you are migrating or upgrading an existing database, then you can run the Oracle Data Migration Assistant independently after the Oracle8i installation is complete.

Complete the following steps to run the Oracle Data Migration Assistant independently:

  1. Start the Oracle Data Migration Assistant.

    On UNIX, enter the following command at a system prompt: 

    odma

    On Windows platforms, choose: 

    Start > Programs > Oracle - HOME_NAME > Migration Utilities > 
Oracle Data Migration Assistant

    When you start the Oracle Data Migration Assistant, its Welcome screen appears (see Figure 7-1).

  2. Respond to questions in each Oracle Data Migration Assistant window, and click Next when you are ready to continue to the next window.

    See Also:

    Step 10 to Step 17 in "Upgrade the Database Using the Oracle Data Migration Assistant" for more information. 

Upgrade the Database Manually

Complete the following steps to upgrade the database manually using SQL scripts:

  1. Follow the instructions in your operating system-specific Oracle documentation to prepare for installation and start the Oracle Universal Installer.

    If you are upgrading a system with Oracle Parallel Server installed, then see the Oracle8i Parallel Server Setup and Configuration Guide for additional installation instructions.

  2. At the Welcome screen of the Oracle Universal Installer, click Next. The File Locations screen appears.

  3. At the File Locations screen, complete the following steps:

    1. Do not change the text in the Source field. This is the location of files for installation

    2. If there is a Destination Name field, enter the name of a new Oracle home in this field.

    3. Enter the complete path of the Oracle home directory where you want to install the new release in the Destination Path field. Click the Browse button to navigate to the directory.

    4. Click Next.

    The Available Products screen appears.

  4. At the Available Products screen, select the Oracle8i server. The Oracle8i server is either Oracle8i Enterprise Edition or Oracle8i, depending on your installation medium. Then, click Next.

  5. At the Installation Types screen, choose either Custom or Minimal. Do not choose Typical unless you want to install a starter database along with your Oracle software. You can avoid installing a starter database if you select Custom or Minimal. Normally, you should not install a starter database if you are upgrading an existing database.

    Note:

    Minimal is not supported for Oracle Parallel Server installations. 

    After you make your selection, click Next.

    If you chose Custom, the Available Product Components screen appears. Complete the following steps:

    1. Choose the product components you want to install. Then, click Next.

      Make sure you install all of the options you installed with the previous database, assuming you do not want to discontinue use of a particular option. For example, if you installed Oracle replication in the previous database, then you should install it in the new Oracle8i database.

    2. If you are installing Oracle Parallel Server, then, at the Cluster Node Selection screen, select the nodes onto which you want the software installed. Then, click Next.

    3. Respond to the remaining screens that enable you to specify your custom installation settings, until you reach the Upgrading or Migrating an Existing Database screen.

  6. At the Upgrading or Migrating an Existing Database screen, leave the Upgrade or Migrate an Existing Database checkbox unselected. Then, click Next.

    If you select the Upgrade or Migrate an Existing Database checkbox, then the Oracle Data Migration Assistant is started automatically after installation. Because you are following the instructions for upgrading the database manually, you should not start the Oracle Data Migration Assistant.

    Note:

    The Oracle Data Migration Assistant does not support Oracle Parallel Server migrations. 

  7. At the Summary screen, make sure all of the settings and choices are correct for your installation. Then, click Install. The Oracle Universal Installer performs the installation, which may take some time.

    When installation is completed successfully, click the Exit button to close the Universal Installer.

  8. If your operating system is Windows, then complete the following steps:

    1. Shut down and restart your computer.

    2. Stop the Oracle service OracleServiceSID of the database you are upgrading, where SID is the instance name. For example, if your SID is ORCL, then enter the following at an MS-DOS prompt: 

      C:\> NET STOP OracleServiceORCL
    3. Delete the Oracle service at the MS-DOS command prompt using ORADIM. The following table lists the MS-DOS command to run for each Oracle7 release:

      Oracle Release...  Enter at the MS-DOS Command Prompt... 

      8.0 

      C:\> ORADIM80 -DELETE -SID SID 

      8.1 

      C:\> ORADIM -DELETE -SID SID 

      For example, if your Oracle release is release 8.0.6 and your SID is ORCL, then enter the following MS-DOS command: 

      C:\> ORADIM80 -DELETE -SID ORCL

      If your Oracle release is release 8.1.5 and your SID is ORCL, then enter the following MS-DOS command: 

      C:\> ORADIM -DELETE -SID ORCL
    4. If your operating system is Windows, then create the Oracle8i database service at the MS-DOS 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:

      SID 

      is the same SID name as the SID of the database you are upgrading. 

      PASSWORD 

      is the password for the new release 8.1 database instance. This is the password for the INTERNAL user. The -INTPWD option is not required. If you do not specify it, then operating system authentication is used, and no password is required.  

      USERS 

      is the maximum number of users who can be granted SYSDBA and SYSOPER privileges. 

      ORACLE_HOME 

      is the release 8.1 Oracle home directory. Ensure that you specify the full pathname with the -PFILE option, including drive letter of the Oracle home directory. 

      For example, if your SID is ORCL, your PASSWORD is TWxy579, the maximum number of USERS is 10, and the ORACLE_HOME directory is C:\ORA81, then enter the following command: 

      C:\> ORADIM -NEW -SID ORCL -INTPWD TWxy579 -MAXUSERS 10 
     -STARTMODE AUTO -PFILE C:\ORA81\DATABASE\INITORCL.ORA
  9. Copy configuration files to a location outside of the old Oracle home:

    1. If your initialization parameter file resides within the old environment's Oracle home, then copy it to a location outside of the old environment's Oracle home. By default Oracle looks for the initialization parameter file in ORACLE_HOME/dbs on UNIX and ORACLE_HOME\database on Windows platforms. The initialization parameter file can reside anywhere you wish, but it should not reside in the old environment's Oracle home after you upgrade to the new release.

    2. If your initialization 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, make the same edits to it as you do to the initialization parameter file, as specified in the next step.

    3. If you have a password file that resides within the old Oracle home, then move or copy the password file to the Oracle8i Oracle home. The name and location of the password file is operating system-specific. On most UNIX operating systems, the default password file is ORACLE_HOME/dbs/orapwsid. On Windows platforms, the default password file is ORACLE_HOME\database\pwdsid.ora. On both UNIX and Windows platforms, sid is your Oracle instance ID.

  10. Adjust the initialization parameter file for use with the new release.

    1. Remove obsolete parameters and adjust changed parameters. Certain initialization parameters are obsolete in the new 8.1 release. Remove all obsolete parameters from any initialization parameter file that will start a new release 8.1 instance. Obsolete parameters may cause errors. Also, alter any parameter whose syntax has changed in the new 8.1 release; refer to Appendix B, "Changes to Initialization Parameters" for lists of new, renamed, and obsolete parameters.

      Also, if you are using Oracle Parallel Server, then see Oracle8i Parallel Server Documentation Set: Oracle8i Parallel Server Concepts; Oracle8i Parallel Server Setup and Configuration Guide; Oracle8i Parallel Server Administration, Deployment, and Performance for more information about obsolete Oracle Parallel Server initialization parameters.

    2. If you are updating snapshots automatically by using the JOB_QUEUE_PROCESSES initialization parameter, then set this parameter to 0 (zero) in the initialization parameter file. Also, if you are using Advanced Queuing and have propagation schedules, then set both the JOB_QUEUE_PROCESSES and AQ_TM_PROCESSES initialization parameters to 0 (zero).

    3. Make sure the OPTIMIZER_MODE initialization parameter is set to CHOOSE. After upgrading your database, you can change the settings for these parameters back to their normal settings.

    4. If the initialization parameter file contains an IFILE entry, then change the IFILE entry in the initialization parameter file to point to the new location you copied it to in Step 9. b. Make sure you edit this file in the same way that you edited the initialization parameter file in sub-steps a to c.

    5. If you are using Oracle Parallel Server, then modify the initdb_name.ora file in the same way that you modified the initialization parameter file.

    Make sure you save all of the files you modified after making these adjustments.

    Note:

    For Oracle Parallel Server, perform this step on all nodes. Also, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

  11. If your operating system is UNIX, then make sure that the following environment variables point to the new release 8.1 directories:

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

  13. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  14. Connect to the database instance as INTERNAL user.

  15. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

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

    You may see error messages listing obsolete initialization parameters. If so, then make a note of the obsolete initialization parameters and continue with the upgrade normally. Then, remove the obsolete initialization parameters the next time you shut down the database (Step 19).

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

    SVRMGR> SPOOL catoutu.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  17. Run uold_release.sql where old_release refers to the release you had installed prior to upgrading. See Table 7-2 to choose the correct script. Each script provides a direct upgrade from the release specified in the "Old Release" column. The "Old Release" is the release from which you are upgrading.

    To run a script, enter the following: 

    SVRMGR> @uold_release.sql
    Table 7-2 Upgrade Scripts
    Old Release  Run Script 

    8.0.1 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.2 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.3 

    u0800030.sql 

    8.0.4 

    u0800040.sql 

    8.0.4S 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.5 

    u0800050.sql 

    8.0.6 

    u0800060.sql 

    8.1.1 

    Upgrading to the new release is not supported. 

    8.1.2 

    Upgrading to the new release is not supported. 

    8.1.3 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.1.4 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.1.5 

    u0801050.sql 

    8.1.6 

    u0801060.sql 

    Note:

    If the old release you had installed prior to upgrading is not listed in Table 7-2, then see the readme files in the new installation for the correct upgrade script to run. 

    Make sure you follow these guidelines when you run the script:

    • You must use the version of the script supplied with new release 8.1 installation.

    • You must run the script in the new release 8.1 environment.

    • You only need to run ONE script, even if your upgrade spans several releases. For example, if your old release was 8.0.4, then you need to run only u0800040.sql.

    The script you run creates and alters certain dictionary tables. It also runs the catalog.sql and catproc.sql scripts that come with the release to which you are upgrading, which create the system catalog views and all the necessary packages for using PL/SQL.

    If you encounter any problems when you run the script, or any of the scripts in the remaining steps, then correct the causes of the problems and rerun the script. You can rerun any of the scripts described in this chapter as many times as necessary.

    See Also:

    "Running Scripts" for information about the types of errors to look for when you run a script. 

    You may encounter a series of messages similar to the following during the upgrade: 

    ORA-00604: error occurred at eecursive SQL level 1
ORA-00001: unique constraint (SYSTEM.AQ$_QUEUES_CHECK) violated
ORA-06512: at "SYS.DBMS_AQADM", line 2023
ORA-06512: at line 2

    You can ignore these messages.

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

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  19. Run SHUTDOWN on the Oracle8i database: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Caution:

    Use SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE. Do not use SHUTDOWN ABORT. 

    Executing this clean shutdown flushes all caches, clears buffers, and performs other DBMS housekeeping activities. These measures are an important final step to ensure the integrity and consistency of the newly upgraded Oracle8i database.

    Also, if you encountered a message listing obsolete initialization parameters when you started the database in Step 15, then remove the obsolete initialization parameters from the initialization parameter file now.

    Your database is now upgraded to the new 8.1 release.

    Caution:

    If you retain the old Oracle software, then never start the upgraded database with the old software. Only start the database with the executables in the new release 8.1 installation directory. Also, before you remove the old Oracle environment, make sure you relocate any datafiles in that environment to the new Oracle8i environment. See the Oracle8i Administrator's Guide for information about relocating datafiles. 

  20. Complete the procedures described in "Upgrading Specific Components" and in Chapter 8, "After Migrating or Upgrading the Database".

Upgrading Specific Components

Some components of the Oracle database server require an upgrade operation separate from the general database upgrade operation. This section contains information about upgrading specific components. You should perform the actions described in these sections only after you have upgraded the database by following the instructions in "Upgrading the Database to the New Oracle8i Release".

Some of the upgrading procedures below involve Export/Import. See Oracle8i Utilities for Export/Import instructions.

Upgrading interMedia Text From a Previous 8.1 Release

The interMedia Text new features for this release are described in Chapter 1 of the Oracle8i Documentation Addendum, release 8.1.7. Make sure no other database administrators are modifying the database when you perform the steps in this section, and make sure no one is querying the database.

Note:

If you used the Oracle Data Migration Assistant to upgrade your database and you had interMedia Text release 8.1 installed, then the assistant displays a message at the end of the upgrade stating that interMedia Text must be upgraded manually. In this case, the database is already upgraded, and you must perform the following steps to manually upgrade interMedia Text.  

Complete the following steps to upgrade interMedia Text to release 8.1.7 from either release 8.1.5 or release 8.1.6:

  1. Shut down the database if it is running: 

    SQL> SHUTDOWN IMMEDIATE
  2. At a system prompt, change to the ORACLE_HOME directory.

  3. Start SQL*Plus: 

    sqlplus /nolog

    Caution:

    You must use SQL*Plus. Do not use Server Manager. 

  4. Connect to the database instance as a user with SYSDBA privilege. 

    SQL> connect sys/change_on_install as sysdba
  5. Run STARTUP RESTRICT: 

    SQL> STARTUP RESTRICT

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

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

    SQL> SPOOL catoutint.log

    If you want to see the output of the scripts you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SQL> SET ECHO ON
  7. If you are upgrading from release 8.1.5, then complete the following steps. Skip to Step 8 if you are upgrading from release 8.1.6.

    1. Run the s0801060.sql script in ORACLE_HOME/ctx/admin/upgrade: 

      SQL> @ctx/admin/upgrade/s0801060.sql
    2. Connect to the database instance as CTXSYS user.

    3. Run the u0801060.sql script in ORACLE_HOME/ctx/admin/upgrade: 

      SQL> @ctx/admin/upgrade/u0801060.sql
    4. Connect to the database instance as a user with SYSDBA privilege: 

      SQL> connect sys/change_on_install as sysdba
  8. Run the s0801070.sql script in the ORACLE_HOME/ctx/admin/upgrade directory 

    SQL> @ctx/admin/upgrade/s0801070.sql

    This script grants new, required database privileges to CTXSYS user.

  9. Connect to the database instance as CTXSYS user.

  10. Run the u0801070.sql script in the ORACLE_HOME/ctx/admin/upgrade directory: 

    SQL> @ctx/admin/upgrade/u0801070.sql

    This script upgrades the CTXSYS schema to release 8.1.7.

  11. Run the dr0typec.pkh script in the ORACLE_HOME/ctx/admin directory: 

    SQL> @ctx/admin/dr0typec.pkh

    This script creates the CTXCAT index type, which is new for release 8.1.7.

  12. Run the dr0pkh.sql script in the ORACLE_HOME/ctx/admin directory: 

    SQL> @ctx/admin/dr0pkh.sql

    This script recreates all public and private package headers.

  13. Run the dr0plb.sql script in the ORACLE_HOME/ctx/admin directory: 

    SQL> @ctx/admin/dr0plb.sql

    This script recreates all public and private package bodies.

  14. Run the dr0type.plb script in the ORACLE_HOME/ctx/admin directory: 

     SQL> @ctx/admin/dr0type.plb

    This script recreates the CONTEXT index type body.

  15. Run the dr0typec.plb script in the ORACLE_HOME/ctx/admin directory: 

    SQL> @ctx/admin/dr0typec.plb

    This script creates the CTXCAT index type body, which is new for release 8.1.7.

  16. Run the dr0itypc.sql script in the ORACLE_HOME/ctx/admin directory: 

    SQL> @ctx/admin/dr0itypc.sql

    This script creates the bindings and index type for CTXCAT, which is new for release 8.1.7.

  17. Check for any invalid CTXSYS objects and alter compile as needed.

  18. 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 6; the suggested name was catoutint.log. Correct any problems you find in this file.

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SQL> SET ECHO OFF
  19. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION

The interMedia Text feature is upgraded to the new release.

Upgrading Oracle Replication

If the Oracle system has Oracle replication installed, then complete the following steps:

  1. Shut down the database if it is running: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

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

  3. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  4. Connect to the database instance as INTERNAL user.

  5. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

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

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

    SVRMGR> SPOOL catoutrep.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  7. Run catrep.sql: 

    SVRMGR> @catrep.sql
  8. Run the rold_release.sql script where old_release refers to the release you had installed prior to upgrading. See Table 7-3 to choose the correct script. Each script provides a direct upgrade for Oracle replication from the release specified in the "Old Release" column. The "Old Release" is the release from which you are upgrading

    To run a script enter the following: 

    SVRMGR> @rold_release.sql
    Table 7-3 Upgrade Scripts for Oracle Replication
    Old Release  Run Script 

    8.0.1 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.2 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.3 

    r0800030.sql 

    8.0.4 

    r0800040.sql 

    8.0.4S 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.0.5 

    r0800050.sql 

    8.0.6 

    r0800050.sql (Same as 8.0.5) 

    8.1.1 

    Upgrading to the new release is not supported. 

    8.1.2 

    Upgrading to the new release is not supported. 

    8.1.3 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.1.4 

    Direct upgrade is not supported. See "Upgrade Paths" for more information. 

    8.1.5 

    No upgrade script is required. Oracle replication will work with the new release 8.1 database. 

    8.1.6 

    No upgrade script is required. Oracle replication will work with the new release 8.1 database. 

    Note:

    If the old release you had installed prior to upgrading is not listed in Table 7-3, then see the readme files in the new installation for the correct upgrade script to run for Oracle replication. 

    Make sure you follow these guidelines when you run the script:

    • You must use the version of the script supplied with new release 8.1 installation.

    • You must run the script in the new release 8.1 environment.

    • You only need to run ONE script, even if your upgrade spans several releases. For example, if your old release was 8.0.4, then you need to run only r0800040.sql.

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

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  10. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION

Oracle replication is upgraded to the new release.

Upgrading JServer

If the Oracle system has JServer installed, then complete the following steps:

  1. Make sure the _SYSTEM_TRIG_ENABLED initialization parameter is set to TRUE in the initialization parameter file. If this initialization parameter is not currently set, then explicitly set it to TRUE: 

    _SYSTEM_TRIG_ENABLED = TRUE
  2. Shut down all instances using SHUTDOWN IMMEDIATE: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

  3. At a system prompt, change to the ORACLE_HOME/javavm/install directory.

  4. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  5. Connect to the database instance as INTERNAL user.

  6. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

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

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

    SVRMGR> SPOOL catoutjava.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  8. Run the appropriate script depending on the release from which you are upgrading.

    If you are upgrading from release 8.1.6, run jvmu816.sql: 

    SVRMGR> @jvmu816.sql

    If you are upgrading from release 8.1.5, run jvmu815.sql: 

    SVRMGR> @jvmu815.sql

    After you run either one on these scripts, user classes that were present before the upgrade are left in place but are typically invalid. These classes are implicitly revalidated when they are used. You can explicitly revalidate any class by issuing an ALTER ANY CLASS statement. For example, to revalidate a class named MyClass, issue the following statement: 

    ALTER JAVA CLASS MyClass RESOLVE;
  9. Run catxsu.sql in the ORACLE_HOME/rdbms/admin directory: 

    SVRMGR> @ORACLE_HOME/rdbms/admin/catxsu.sql

    For ORACLE_HOME, substitute the complete path to your Oracle home directory.

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

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  11. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION
  12. Shut down all instances using SHUTDOWN IMMEDIATE: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

  13. Exit Server Manager.

  14. To ensure that the Oracle Servlet Engine (OSE) is configured correctly, make the following changes to your initialization parameter file:

    1. If the MTS_SERVICE initialization parameter exists in the file, then comment it out. You can comment out an initialization parameter by placing a # symbol at the beginning of the line. You can remove the comment symbol after the upgrade is complete.

    2. Make sure the following initialization parameters are set to the values shown: 

      MTS_DISPATCHERS="(PROTOCOL=tcp)"
MTS_DISPATCHERS="(PROTOCOL=tcps)"
MTS_SERVERS=5 
LOCAL_LISTENER=inst1

      MST_SERVERS can be set to a value higher than 5, but not lower.

      See Also:

      The readme.txt file in the ORACLE_HOME/javavm directory for more information about configuring the OSE 

  15. To ensure that the OSE is configured correctly, make sure your tnsnames.ora file contains the correct information. For example, suppose your environment includes the following:

    • A host server named hq_server

    • A database instance with the service name rdbms_hq.mycompany.com

    In this case, your tnsnames.ora file must contain the following entries: 

    inst1_http = (DESCRIPTION=
  (ADDRESS=(PROTOCOL=tcp)(HOST=hq_server)(PORT=5521))
    (CONNECT_DATA=
      (SERVICE_NAME=rdbms_hq.mycompany.com)
      (SERVER=shared)
      (PRESENTATION=http://admin)))

inst1_https = (DESCRIPTION=
  (ADDRESS=(PROTOCOL=tcps)(HOST=hq_server)(PORT=5524))
    (CONNECT_DATA=
      (SERVICE_NAME=rdbms_hq.mycompany.com)
      (SERVER=shared)
      (PRESENTATION=http://admin)))

    See Also:

    The readme.txt file in the ORACLE_HOME/javavm directory for more information about configuring the OSE 

  16. To ensure that the OSE is configured correctly, make sure your listener.ora file contains the correct information. For example, suppose that in your environment the wallet directory is /home/wallet. In this case, your listener.ora file must contain the following entry: 

    oss.source.my_wallet=
  (SOURCE=
    (METHOD=FILE)
    (METHOD_DATA=
      (DIRECTORY=/home/wallet)))

    See Also:

    The readme.txt file in the ORACLE_HOME/javavm directory for more information about configuring the OSE 

  17. At a system prompt, change to the ORACLE_HOME/javavm/install directory, if you are not already there.

  18. Start SQL*Plus: 

    sqlplus /nolog

    Caution:

    You must use SQL*Plus. Do not use Server Manager. 

  19. Connect to the database instance as a user with SYSDBA privilege. 

    SQL> connect sys/change_on_install as sysdba
  20. Run STARTUP: 

    SQL> STARTUP

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

  21. Start the administration OSE by running the jisaep script: 

    SQL> @jisaep admin http_port https_port -register

    Use 8080 for http_port and 9090 for https_port if these ports are available.

  22. To start Java Accelerator, complete the following steps:

    1. Make sure you have at least 100 megabytes of free rollback segment space.

    2. Grant JAVA_DEPLOY privilege to SYS: 

      SQL> GRANT JAVA_DEPLOY TO SYS;
    3. Run the jisja.sql script 

      SQL> @jisja.sql
    4. Run the jspja.sql script: 

      SQL> @jspja.sql

The JServer component is upgraded to the new release.

The XML Parser for PL/SQL and the XML Class Generator for Java are not loaded during an upgrade.

To use the XML Parser for PL/SQL, load the following file: 

ORACLE_HOME/lib/xmlplsql.jar

Then, run the following script: 

ORACLE_HOME/xdk/plsql/parser/bin/load.sql

To use XML Class Generator for Java, load the following file: 

ORACLE_HOME/lib/classgen.jar

See Also:

Oracle8i Application Developer's Guide - XML for more information about the XML Parser for PL/SQL and the XML Class Generator for Java 

Note:

Upgrade of Enterprise JavaBeans is not supported. If you deployed Enterprise JavaBeans in a past release, then you need to redeploy it for release 8.1.7. See the Oracle8i Enterprise JavaBeans Developer's Guide and Reference for information. 

Upgrading Oracle Parallel Server

If the Oracle system has Oracle Parallel Server installed, then complete the following steps:

  1. Shut down all instances using SHUTDOWN IMMEDIATE: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

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

  3. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  4. Connect to the database instance as INTERNAL user.

  5. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

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

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

    SVRMGR> SPOOL catoutpar.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  7. Run catparr.sql: 

    SVRMGR> @catparr.sql
  8. Turn off the spooling of script results to the log file: 

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  9. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION

Oracle Parallel Server is upgraded to the new release.

Upgrading Snapshots

Note:

The word "snapshot" is synonymous with the word "materialized view". 

Snapshots upgraded from release 8.0 or imported from a release 8.0 database cannot use the new summary management features available in release 8.1. If you want to use these new features, then complete the following steps for each snapshot and for each snapshot imported from release 8.0:

  1. GRANT QUERY REWRITE privileges to the owner of the snapshot. Only local snapshots are available for query rewrite.

    If the snapshot references any schema objects outside its owner's schema, then you must issue a GRANT GLOBAL QUERY REWRITE statement.

  2. Issue the ALTER SNAPSHOT ... ENABLE QUERY REWRITE statement on the snapshots you want to upgrade.

    For example, on a snapshot named SSORDERS, issue the following statement: 

    ALTER SNAPSHOT ssorders ENABLE QUERY REWRITE;

In addition, if you do not ENABLE QUERY REWRITE on a snapshot, then the ATOMIC=FALSE option of the DBMS_SNAPSHOT.REFRESH procedure may not work unless you issue an ALTER SNAPSHOT ... COMPILE statement on the snapshot. For example, for a snapshot named SSCUST, issue the following statement: 

ALTER SNAPSHOT sscust COMPILE;

You do not need to issue this statement if you have issued any other ALTER SNAPSHOT statement on the snapshot, such as the ALTER SNAPSHOT ... ENABLE QUERY REWRITE statement.

Upgrading the Advanced Queuing Option

The following sections describe the actions required to upgrade the Advanced Queuing (AQ) option.

Use the Extended Address Field

Note:

This section only applies to systems that were upgraded from release 8.0.3 of Oracle. If you never ran release 8.0.3 of Oracle on your current system, then you do not need to perform the procedure in this section, and you can move on to "Upgrade Your Queue Tables". 

Release 8.0.4 introduced an extended address field in the AQ$_AGENT datatype; the address field was extended to 1024 bytes. If you installed release 8.0.3, then you must perform the procedure in this section to use the extended address field.

Also, if you installed release 8.0.3 but performed the steps described in this section to extend the address field when you upgraded to a prior release, such as release 8.0.4, then you need not perform the steps below. Or, if you do not plan to use the AQ, then you need not perform these steps.

However, if you installed release 8.0.3, then you have not performed these steps in a prior release, and you want to use the extended address field, you should perform this procedure now. Oracle Corporation recommends using the extended address field.

To use the extended address field, complete the following steps:

  1. Shut down the database: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

  2. In the initialization parameter file, set the JOB_QUEUE_PROCESSES and AQ_TM_PROCESSES initialization parameters to 0 (zero). You can change the settings these for parameters back to their normal values after this procedure is complete.

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

  4. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  5. Connect to the database instance as INTERNAL user.

  6. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

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

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

    SVRMGR> SPOOL catoutaq.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  8. Issue the following SQL statement to determine the existing queue tables in the database: 

    SELECT owner, queue_table FROM dba_queue_tables;
  9. Open the Export utility in a new command window.

  10. Export the contents of all existing queue tables using the Export utility.

    You also must export the SYSTEM.DEF$_AQCALL and SYSTEM.DEF$_AQERROR queue tables and then import them in Step 15. These default queue tables are used by Oracle replication.

    See Also:

    Oracle8i Application Developer's Guide - Advanced Queuing for more information about the required procedure for exporting queue tables, and see Oracle8i Utilities for detailed information about using the Export utility. 

  11. Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop all of your queue tables. Make sure you drop the SYSTEM.DEF$_AQCALL and SYSTEM.DEF$_AQERROR queue tables.

    See Also:

    Oracle8i Application Developer's Guide - Advanced Queuing for information about the DBMS_AQADM.DROP_QUEUE_TABLE procedure. 

  12. Run catnoque.sql to drop the existing AQ dictionary tables: 

    @catnoque.sql
  13. Run catqueue.sql to redefine the new types and dictionary tables: 

    @catqueue.sql
  14. In the command window where you ran the Export utility, close the Export utility and open the Import utility.

  15. Import the queue tables you exported in Step 10 using the Import utility.

    See Also:

    Oracle8i Utilities for detailed information about using the Import utility. 

  16. Check that all queue tables exported in Step 10, including the SYSTEM.DEF$_AQCALL and SYSTEM.DEF$_AQERROR queue tables, were properly imported in Step 15 by issuing the following SQL statement: 

    SELECT owner, queue_table FROM dba_queue_tables;

    The following is an example of the output you should see when you issue this SQL statement: 

    OWNER                          QUEUE_TABLE
------------------------------ ------------------------------ 
SYSTEM                         DEF$_AQCALL
SYSTEM                         DEF$_AQERROR
AQUSER1                        QUEUE_TABLE1
AQUSER2                        QUEUE_TABLE2
  17. Turn off the spooling of script results to the log file: 

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  18. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION;

You can now use the extended address field.

Upgrade Your Queue Tables

The following release 8.1 AQ enhancements are available only if you upgrade your existing queue tables:

To upgrade an existing queue table, run the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, specifying 8.1 for the option. For example, for a queue table named TB_QUEUE owned by SCOTT user, run the following procedure: 

EXECUTE dbms_aqadm.migrate_queue_table (
    queue_table => 'scott.tb_queue',       
    compatible => '8.1');

To create a new queue table that is release 8.1 compatible, connect as the owner of the queue table and run the DBMS_AQADM.CREATE_QUEUE_TABLE procedure, specifying 8.1 for the COMPATIBLE option, as in the following example: 

EXECUTE dbms_aqadm.create_queue_table(
    queue_table => 'scott.tkaqqtpeqt', 
    queue_payload_type =>'message', 
    sort_list => 'priority,enq_time', 
    multiple_consumers => true, 
    comment => 'Creating queue with priority and enq_time sort order', 
    compatible => '8.1');

Note:

The COMPATIBLE initialization parameter must be set to 8.1.0 or higher to upgrade your queue tables and to create new release 8.1 compatible queue tables. 

Upgrading User-Defined Datatypes

When you upgrade your database from release 8.0 to release 8.1, the existing user-defined datatypes (such as object types, nested tables, and varrays) retain the release 8.0 representation format. The representation format is changed in release 8.1 to optimize disk space utilization for better performance.

You can continue to use the release 8.0 format in release 8.1, but then you will not benefit from the improved representation format. Therefore, upgrading your existing user-defined datatypes is not required, but it is recommended.

To use the new format for existing user-defined datatypes, complete the following steps:

  1. Export all of the tables (including queue tables) containing release 8.0 user-defined object types, nested tables, and varrays using the Export utility.

  2. Drop the tables you exported.

  3. Make sure the compatibility level of your database is at 8.1.0 or higher by setting the COMPATIBLE initialization parameter.

  4. Import the tables you exported in Step 1 using the Import utility.

Upgrading the Recovery Catalog

Your recovery catalog schema for the upgraded database may reside in a database that is separate from the database you upgraded. If you upgraded the Recovery Manager executable to release 8.1, then you must upgrade the recovery catalog to release 8.1 as well.

Also, if you have multiple databases of different releases managed by a single recovery catalog, then you need to consider compatibility issues between a particular Recovery Manager release and the recovery catalog release. For example, release 8.1.3 and 8.1.4 of Recovery Manager cannot access a release 8.1.5 or higher recovery catalog. Therefore, in this case, you must upgrade all of the databases managed by the recovery catalog to release 8.1.5 or higher. For more information about recovery catalog compatibility with Recovery Manager, see "Recovery Manager".

Complete the following steps to upgrade the recovery catalog:

  1. Log in to Recovery Manager and connect to the recovery catalog.

    For example, if RCAT/RCAT is the user name and password for the recovery catalog owner, and RECDB is the network service name, then enter the following: 

    rman rcvcat rcat/rcat@recdb

    The first time you connect to an older recovery catalog with the 8.1 release of Recovery Manager, you will see message RMAN-06186, indicating that the recovery catalog must be upgraded.

  2. Use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current release. Recovery Manager prompts you to enter the command twice to confirm the catalog upgrade. If any errors are encountered while upgrading, then they are displayed in the Recovery Manager log.

    Here is the log from a session that upgrades the recovery catalog from release 8.0.4: 

    Recovery Manager: Release 8.1.5.0.0 

RMAN-06008: connected to recovery catalog database 
RMAN-06186: PL/SQL package rcat.DBMS_RCVCAT version 08.00.04 in RCVCAT 
database is too old 

RMAN> upgrade catalog 

RMAN-06435: recovery catalog owner is rcat 
RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade 

RMAN> upgrade catalog 

RMAN-06408: recovery catalog upgraded to version 08.01.05

Upgrading Statistics Tables Created by the DBMS_STATS Package

If you created statistics tables using the DBMS_STATS.CREATE_STAT_TABLE procedure, then upgrade these tables by executing the following procedure: 

EXECUTE DBMS_STATS.UPGRADE_STAT_TABLE('scott', 'stat_table');

where SCOTT is the owner of the statistics table and STAT_TABLE is the name of the statistics table. Execute this procedure for each statistics table.

Recompiling Invalid PL/SQL Modules

The utlrp.sql script recompiles all existing PL/SQL modules that were previously in an INVALID state, such as packages, procedures, types, etc. These actions are optional; however, they ensure that the cost of recompilation is incurred during installation rather than in the future.

To run the utlrp.sql script, complete the following steps:

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

  2. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  3. Connect to the database instance as INTERNAL user.

  4. Run utlrp.sql: 

    SVRMGR> @utlrp.sql

Oracle Corporation highly recommends running utlrp.sql.

Changing the Word-Size of Your Current Release

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

See Also:

"Changing Word-Size" for more information about changing word-size. 

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

  1. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  2. Connect to the database instance as INTERNAL user.

  3. Run SHUTDOWN IMMEDIATE on the database: 

    SVRMGR> SHUTDOWN IMMEDIATE

    Note:

    For Oracle Parallel Server, issue this statement for all instances. Also, set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after the upgrade operation is complete. 

  4. Perform a full offline backup of the database.

    See Also:

    Oracle8i 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 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 version of the same release. Or, if you currently have a 64-bit installation, then install the 32-bit version of the same release.

    Note:

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

  7. Copy configuration files to a location outside of the old Oracle home:

    1. If your initialization 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 initialization 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.

    2. If your initialization 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 initialization parameter file to point to its new location.

    3. If you have a password file that resides within the old Oracle home, then move or copy the password file to the Oracle8i Oracle home. The name and location of the password file is operating system-specific; for example, on UNIX operating systems, the default password file is ORACLE_HOME/dbs/orapwsid, but on Windows platforms, the default password file is ORACLE_HOME\database\pwdsid.ora. In both cases, sid is your Oracle instance ID.

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

  9. Start Server Manager. On most operating systems, enter svrmgrl at a command prompt to start Server Manager in Oracle8i.

  10. Connect to the database instance as INTERNAL user.

  11. Run STARTUP RESTRICT: 

    SVRMGR> STARTUP RESTRICT

    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: 

    SVRMGR> SPOOL catoutw.log

    If you want to see the output of the script you will run on your screen, then you also can issue a SET ECHO ON statement: 

    SVRMGR> SET ECHO ON
  13. Run utlirp.sql: 

    SVRMGR> @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 package STANDARD and DBMS_STANDARD, which are necessary for using PL/SQL. Finally, it triggers a recompile of all PL/SQL modules, such as packages, procedures, types, etc.

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

    SVRMGR> SPOOL OFF

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

    If you specified SET ECHO ON, then you may want to SET ECHO OFF now: 

    SVRMGR> SET ECHO OFF
  15. Run ALTER SYSTEM DISABLE RESTRICTED SESSION: 

    SVRMGR> ALTER SYSTEM DISABLE RESTRICTED SESSION

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

Go to previous page Go to next page
Oracle
Copyright © 1996-2000, Oracle Corporation.
All Rights Reserved.

Library
Product
Contents
Index