4
Migrating from Oracle7 Using the Migration Utility

$ORACLE_HOME/migrate/nls/admin/data

Perform Migration Steps in the Oracle7 Environment

Complete the following migration steps in the Oracle7 environment. These steps apply to both UNIX systems and Windows platforms.

1. Start Server Manager.

2. Connect to the Oracle7 database as INTERNAL user.

3. Startup your Oracle7 database:

   STARTUP
   
   

4. Make sure the NLS_LANG environment variable is set to the character set you are using for your database.

   To check your character set, issue the following SQL statement:

   SELECT * FROM v$nls_parameters 
      WHERE parameter = 'NLS_LANGUAGE'   
         OR parameter = 'NLS_TERRITORY'
         OR parameter = 'NLS_CHARACTERSET';
   
   

   You use all three values returned by this query to set NLS_LANG. For example, suppose your output for the query above is the following:

   PARAMETER                   VALUE                                                           
   ---------------------  --------------------------- 
   NLS_LANGUAGE               AMERICAN                                                        
   NLS_TERRITORY              AMERICA                                                         
   NLS_CHARACTERSET          US7ASCII                                                        
   
   

   In this case, set NLS_LANG to the following at a command prompt:

   AMERICAN_AMERICA.US7ASCII
   
   

   See Also: Oracle8i National Language Support Guide for information about setting NLS_LANG.

5. Make sure you have DBA privileges, which are required to run the Oracle8i Migration utility.

   To check if you have DBA privileges, query the DBA_ROLE_PRIVS static data dictionary view. For example, if you are connected as user SYSTEM, then enter the following SQL statement:

   SELECT * FROM dba_role_privs WHERE grantee = 'SYSTEM';
   
   

   You have DBA privileges if 'DBA' is listed in the GRANTED_ROLE column for the user. If you do not have DBA privileges, then connect as a user who does.

6. Make sure no other DBA with RESTRICTED SESSION privilege connects to the database while the Migration utility is running. Also, "Normal" users should not connect to the database during migration.

7. Determine the files that you will back up in Step 9 by issuing the following SQL statements:

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

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

8. Shutdown the Oracle7 database cleanly using the SHUTDOWN NORMAL or SHUTDOWN IMMEDIATE statement; do not use SHUTDOWN ABORT. The Oracle7 source database must be shut down cleanly; therefore, no redo information or uncommitted transactions can remain.

   SHUTDOWN IMMEDIATE
   
   

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

   Note: If you do not shut down the Oracle7 database before migration starts, then the Migration utility will stop and display an error message.

9. Make a complete backup of your Oracle7 database. Make sure you back up the files listed in the v7files.log spool file that you generated in Step 7.

   Caution: If you encounter any problems with the migration, 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: The Oracle7 Server Administrator's Guide for information about backing up your Oracle7 database.

Run the Migration Utility

The steps required to run the Migration utility on UNIX are different than the steps required to run the Migration utility on a Windows platform. Complete the steps in the appropriate section:

• Run the Migration Utility on UNIX

• Run the Migration Utility on a Windows Platform

Run the Migration Utility on UNIX

Complete the following steps to run the Migration utility on a UNIX operating system:

1. Make sure your environment variables are still pointing to the Oracle7 directories.

   See Also: Step 3 in the "Prepare the Oracle7 Environment for Migration on UNIX Operating Systems" for detailed information about the environment variables to check.

2. Make sure you have enough space in the SYSTEM tablespace (optional).

   A common migration problem is running out of space in the SYSTEM tablespace during migration. The Migration utility will not complete the migration unless sufficient space is allocated in the SYSTEM tablespace. To determine disk space requirements for a successful migration, run the Oracle8i Migration utility with the CHECK_ONLY command-line option set to TRUE by entering the following at a system prompt:

   mig CHECK_ONLY=TRUE
   
   

   The CHECK_ONLY command-line option causes the Migration utility to assess the amount of disk space required for migration, check the amount of space available, and issue an informational message about the disk space requirements. When the CHECK_ONLY command-line option is set to TRUE, the Migration utility does not build the Oracle8i data dictionary or perform any other migration processing.

   If the CHECK_ONLY command-line option shows that you need to add more space to the SYSTEM tablespace, then you should add the amount specified by the CHECK_ONLY option plus an additional 25 megabytes. The additional 25 megabytes approximates the amount of space required by the migration scripts that you will run later in the migration process.

   To add space to the SYSTEM tablespace, issue a statement similar to the following, substituting the appropriate directory path and name for the new datafile and the amount of space you need to add:

   ALTER TABLESPACE system
      ADD DATAFILE '/home/user1/mountpoint/oradata/db1/system02.dbf'
      SIZE 50M;
   
   

   If you add space to the SYSTEM tablespace, then remember to shut down the database when you are finished.

3. Run the Migration utility by entering the Migration utility command at the system prompt:

   mig
   
   

   The command is mig unless stated otherwise in your operating system-specific Oracle documentation. Enter mig alone to run the Migration utility with a default set of options, or enter mig followed by one or more selected options.

   See Also: "Review Migration Utility Command-Line Options" for information about command-line options. Oracle Corporation recommends using the SPOOL option, because it makes it easier to check your migration results when the migration is complete.

4. When the Migration utility has completed successfully, change the following environment variables to point to the Oracle8i executables:
   • ORACLE_HOME

   • PATH

   • LD_LIBRARY_PATH

   • ORA_NLS

   If ORACLE_HOME points to the Oracle7 executables, then an ORA-223 error is displayed when you run the ALTER DATABASE CONVERT statement later in the migration process, stating "conversion data file is invalid or incorrect version".

   Note: For Oracle Parallel Server, perform this step on all nodes.

   See Also: Your operating system-specific Oracle8i installation documents for information about setting other important environment variables on your operating system.

Run the Migration Utility on a Windows Platform

Complete the following steps to run the Migration utility on a Windows platform:

1. In the new Oracle8i Oracle home, run the Migration utility by entering the Migration utility command at the MS-DOS prompt with the PFILE option included:

   C:\> mig PFILE=ORACLE7_HOME\DATABASE\INIT_PARAM_FILE
   
   

   Replace the ORACLE7_HOME variable with the complete path to the Oracle7 Oracle home directory. Also, replace the INIT_PARAM_FILE variable with the full name of the initialization parameter file for the Oracle7 database.

   For example, if the ORALCE7_HOME is C:\ORANT and the INIT_PARAM_FILE is INITORCL.ORA, then enter the following:

   C:\> mig PFILE=C:\ORANT\DATABASE\INITORCL.ORA
   
   

   You can enter mig with the PFILE option only to run the Migration utility with a default set of options, or you can enter mig followed by more selected options.

   See Also: "Review Migration Utility Command-Line Options" for information about command-line options. Oracle Corporation recommends using the SPOOL option, because it makes it easier to check your migration results when the migration is complete.

2. If the Oracle7 Password appears when you run the Migration utility, then enter the password for the INTERNAL user on the Oracle7 database. This prompt appears because the DBA_AUTHORIZATION registry parameter is set improperly or is not set at all.

3. Stop the Oracle7 service OracleServiceSID, 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
   
   

4. After the Migration utility has run successfully, delete the Oracle7 service at the MS-DOS command prompt using ORADIM7x. The following table lists the MS-DOS command to run for each Oracle7 release:

   Oracle7 Release...	Enter at the MS-DOS Command Prompt...
   7.1	C:\> ORADIM71 -DELETE -SID SID
   7.2	C:\> ORADIM72 -DELETE -SID SID
   7.3	C:\> ORADIM73 -DELETE -SID SID

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

   C:\> ORADIM73 -DELETE -SID ORCL
   
   

5. Restart your computer.

6. 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 version 7 database you migrated.
   PASSWORD	is the password for the new release 8.1 database instance. This is the password for 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 
   

Check the Migration Results

Check the results after running the Migration utility. The Migration utility generates informational messages and echoes its progress as it runs the migrate.bsq script. If the Migration utility exits with an ORA- error, then check Appendix A, "Troubleshooting Migration Problems" for information about the error and the actions to perform to resolve the problem.

The Migration utility creates a convert file that contains the information of the Oracle7 control file. Later in the migration process, the convert file is used by ALTER DATABASE CONVERT to create a new control file in Oracle8i.

The name and location of the convert file are operating system-specific. For example, on a UNIX operating system, the default location is ORACLE_HOME/dbs in the Oracle7 environment, and the default filename in this directory is convsid.dbf, where sid is your Oracle7 instance ID. On Windows NT, the default location is ORACLE_HOME\rdbms in the Oracle8i environment, and the default filename in this directory is convert.ora.

Preserve the Oracle7 Source Database

After you successfully run the Migration utility, perform a cold backup of the Oracle7 database. This backup serves the following purposes:

• If you wish to return to the Oracle7 database after executing the ALTER DATABASE CONVERT statement on Oracle8i, then you can restore the backup, start the Oracle7 database, and complete procedure in "Abandoning the Migration".

• It can be used as the first Oracle8i backup for an Oracle8i recovery.

• If an error occurs at Oracle8i database convert time (ALTER DATABASE CONVERT or ALTER DATABASE OPEN RESETLOGS), then you can restore this backup, fix the problem(s), and continue the conversion process. However, if you restore a backup that was performed before you ran the Migration utility, then you must rerun the Migration utility.

  See Also: The Oracle7 Server Administrator's Guide for information about performing backup and restore operations on your Oracle7 database.

In addition, perform a backup of the entire Oracle7 software distribution, including the Oracle7 home directory. Make sure the backup includes the following:

• all of the subdirectories

• control files

• datafiles and online redo log files (in case any datafiles in the Oracle7 database are lost or unreadable), although these files should not contain any outstanding redo information.

• parameter files

• convert file

• scripts that create objects in the Oracle7 database

• scripts that could restore the original database, if necessary

Perform Migration Steps in the Oracle8i Environment

Complete the following migration steps in the Oracle8i environment:

1. Either remove or rename the database's control files, or use the CONTROL_FILES initialization parameter to specify new control file names. The CONTROL_FILES initialization parameter typically is set in the initialization parameter file, but, if you are using Oracle Parallel Server, then it may be set in the initdb_name.ora file instead.

   You will issue the ALTER DATABASE CONVERT statement in Step 10. This statement automatically creates new control files. If you do not use the CONTROL_FILES parameter, then this statement uses the control file names of your pre-migration database (derived from the CONVERT file) and returns an error if the control files already exist. Therefore, in this case, you must remove or rename the control files.

   However, if you use the CONTROL_FILES initialization parameter to specify new control file names, then the ALTER DATABASE CONVERT statement creates the new control files with the names you specify, and you do not need to remove the old control files. For a complete list of your existing control files, check the v7files.log spool file you created in Step 9.

   Control files are considerably larger in Oracle8i than in Oracle7. For example, Oracle7 control files in the hundreds of kilobytes may expand into tens of megabytes in Oracle8i. The larger size in Oracle8i results from the storage of more information in the control file, such as backup and tablespace records. This size increase could be important if a control file is on a raw device or if its available disk space is restricted.

   Note: The CONTROL_FILES initialization parameter specifies one or more names of control files, separated by commas. Oracle Corporation recommends using multiple files on different devices or mirroring the file at the operating system level. See the Oracle8i Administrator's Guide for more information.

   Note: For Oracle Parallel Server, perform this step on all nodes.

2. Copy files that are important for migration to a location outside of the Oracle7 Oracle home:
   1. If your operating system is UNIX, then move or copy the convert file from the Oracle7 Oracle home directory to the Oracle8i Oracle home directory. On most UNIX operating systems, the convert file, convsid.dbf (where sid is the Oracle8i database name), should reside in ORACLE_HOME/dbs in both the Oracle7 and the Oracle8i environment.

      On Windows platforms, the convert file, convert.ora, should reside in ORACLE_HOME\rdbms in the Oracle8i environment. It is placed in this directory automatically by the Migration utility, and you do not need to move it.

   2. If you have a password file that resides within the Oracle7 Oracle home, then move or copy the password file to the Oracle8i Oracle home directory.

      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.

   3. If your initialization parameter file resides within the Oracle7 Oracle home, then move or copy it to a location outside of the Oracle7 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 Oracle7 Oracle home after you migrate to Oracle8i.

   4. If the initialization parameter file contains an IFILE (include file) entry that resides within the Oracle7 Oracle home, then move or copy the file specified in the IFILE entry to a location outside of the Oracle7 Oracle home.

   5. If you are using Oracle Parallel Server and your initdb_name.ora file resides within the Oracle7 Oracle home, then move or copy the initdb_name.ora file to a location outside of the Oracle7 Oracle home.

      Note: For Oracle Parallel Server, perform this step on all nodes.

3. Adjust the initialization parameter file in the Oracle8i environment for use with Oracle8i. Specifically, complete the following steps:
   1. Set the COMPATIBLE initialization parameter in your initialization parameter file to a valid version 8 setting, such as 8.0.6 or 8.1.7. Make sure the COMPATIBLE parameter is not set to any Oracle7 release, because if it is, then you will not be able to start the Oracle8i database. See "Setting the COMPATIBLE Initialization Parameter" for information.

   2. Remove obsolete parameters and adjust changed parameters. Certain Oracle7 initialization parameters are obsolete in version 8. Remove all obsolete initialization parameters from any initialization parameter file that will start an Oracle8i instance; obsolete parameters may cause errors in Oracle8i. Also, alter any parameter whose syntax has changed in version 8; 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.

   3. 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. After migrating your database, you can change the setting for this parameter back to its normal setting.

   4. Make sure the OPTIMIZER_MODE initialization parameter is set to CHOOSE. After migrating your database, you can change the setting for this parameter back to its normal setting.

   5. If you are using Oracle Parallel Server, then set the PARALLEL_SERVER initialization parameter to FALSE. You can change it back to TRUE after migration is complete.

   6. If you are using a Distributed Lock Manager (DLM) on a UNIX operating system, then make sure you set the LM_LOCKS, LM_RESS, and LM_PROCS initialization parameters equal to the lock, resource, and process parameters for the DLM used in Oracle7.

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

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

   8. On Windows platforms, change the BACKGROUND_DUMP_DEST and USER_DUMP_DEST initialization parameters that point to RDBMS71, RDBMS72, or RDBMS73 to point to the following directories instead (optional):

      Initialization Parameter	Change Setting To
      BACKGROUND_DUMP_DEST	ORACLE_BASE\oradata\DB_NAME
      USER_DUMP_DEST	ORACLE_BASE\oradata\DB_NAME\archive

      In the settings, substitute the complete ORACLE_BASE path for ORACLE_BASE and substitute the database name for DB_NAME.

   9. Make sure all path names in the initialization parameter file are fully specified. You should not have relative path names in the initialization parameter file.

   10. 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 2. Then, edit the file specified in the IFILE entry in the same way that you edited the initialization parameter file in sub-steps a to i.

   11. 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 in steps a to h.

   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.

4. If the Oracle8i DB_NAME is different from the Oracle7 DB_NAME, then complete the following steps. Otherwise, skip to Step 5.
   1. On UNIX operating systems, rename the convsid.dbf file to match the Oracle8i DB_NAME. For example, if the Oracle7 DB_NAME is DBMS7 and the Oracle8i DB_NAME is DBMS8, then rename the convert file from convDBMS7.dbs to convDBMS8.dbs. This action is not necessary on Windows platforms.

   2. Set the DB_NAME initialization parameter in the initialization parameter file to the Oracle8i database name.

5. Make sure all online data files are accessible and in the correct directories. If you are using a raw disk, then log files also must be accessible.

6. Change to the ORACLE_HOME/rdbms/admin directory. You should be in the Oracle8i Oracle home.

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

8. Connect to the database instance as user INTERNAL.

9. Start an Oracle8i database instance without mounting the new Oracle8i database:

   SVRMGR> STARTUP NOMOUNT 
   
   

   Caution: Starting the database instance in any other mode might corrupt the database.

   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 migration normally. Then, remove the obsolete initialization parameters the next time you shut down the database (Step 18).

10. Create a new Oracle8i database control file and convert the file headers of all online tablespaces to Oracle8i format by issuing the following statement:

    SVRMGR> ALTER DATABASE CONVERT;
    
    

    Successful execution of this statement is the "point of no return" to Oracle7 for this database. However, if necessary, you can restore the Oracle7 database from backups.

    If errors occur during this step, then correct the conditions that caused the errors and rerun the Migration utility. Restart at Step . Otherwise restore the backup you performed after you ran the Migration utility.

    See Also: "Problems at the ALTER DATABASE CONVERT Statement" for information about common errors encountered at this step and the actions required to resolve them.

11. Open the Oracle8i database with the following statement:

    SVRMGR> ALTER DATABASE OPEN RESETLOGS; 
    
    

    When the Oracle8i database is opened, all rollback segments that are online are converted to the new Oracle8i format.

    If you encounter errors when you issue this statement, then start the migration process over from the beginning, ensuring the database is not opened in the Oracle7 environment after the Migration utility completes. Start from the beginning of this chapter, Chapter 4, but make sure you completed all of the pre-migration steps described in Chapter 3.

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

    SVRMGR> SPOOL catoutm.log
    
    

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

    SVRMGR> SET ECHO ON
    
    

13. Run the Oracle8i database conversion script u0703040.sql:

    SVRMGR> @u0703040.sql
    
    

    The u0703040.sql script is the database conversion script for all 7.1, 7.2, and 7.3 releases supported by the Migration utility on your operating system. The u0703040.sql script creates and alters certain system tables and drops the MIGRATE user. It also runs the catalog.sql and catproc.sql scripts, which create the system catalog views and all the necessary packages for using PL/SQL.

    If you encounter any problems when you run this script, or any of the scripts in the remaining steps, then correct the cause(s) 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.

14. If the Oracle system has Oracle replication installed, then complete the following steps:
    1. Run catrep.sql:

       SVRMGR> @catrep.sql
       
       

    2. Run r0703040.sql:

       SVRMGR> @r0703040.sql
       
       

       This r0703040.sql script performs a post-catrep.sql Oracle replication related upgrade.

15. If the Oracle system has Oracle Parallel Server installed, then run catparr.sql:

    SVRMGR> @catparr.sql
    
    

16. Run utlrp.sql (optional):

    SVRMGR> @utlrp.sql
    
    

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

    Oracle Corporation highly recommends performing this optional step.

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 12; the suggested name was catoutm.log.

    You should look for errors that alert you to insufficient space, and for errors that alert you that a script failed to run. If you see these types of errors, then your migration may not be completely successful. However, you typically can ignore errors about the failure to alter or drop an object that does not exist.

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

    SVRMGR> SET ECHO OFF
    
    

18. 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 migrated Oracle8i database.

    The COMPATIBLE initialization parameter controls the compatibility level of your database. Set the COMPATIBLE initialization parameter in your initialization parameter file based on the compatibility level you want for your migrated database.

    See Also: "Setting the COMPATIBLE Initialization Parameter" for information.

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

19. Complete the procedures described in Chapter 8, "After Migrating or Upgrading the Database".

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

Troubleshooting Errors During Migration

Errors may be caused by the following actions or omissions:

• performing a migration step out of order

• failing to fulfill the prerequisites for migration

• encountering an occasional conversion irregularity

  
  

  See Also: Appendix A, "Troubleshooting Migration Problems" and Oracle8i Error Messages for information about errors during migration and about corrective action for each error.

Abandoning the Migration

If you took a backup of your Oracle7 database before you ran the Migration utility, then the easiest way to abandon a migration is to restore that backup. However, if you do not have a backup, or if you took the backup after running the Migration utility, then you must complete the procedure described in this section to abandon the migration.

You can run the Oracle8i Migration utility multiple times and still return to the Oracle7 database. However, running the Migration utility automatically eliminates the Oracle7 database catalog views. Therefore, to return to the Oracle7 database after running the Migration utility, you must run the Oracle7 catalog.sql script to restore the Oracle7 database catalog views.

To abandon the migration, you generally must restore the Oracle7 database by completing the following steps in the Oracle7 environment:

1. Start the Oracle7 database using Server Manager.

2. Drop the user MIGRATE:

   SVRMGR> DROP USER MIGRATE CASCADE;
   
   

3. Rerun catalog.sql and catproc.sql:

   SVRMGR> @catalog.sql
   SVRMGR> @catproc.sql
   
   

4. If Server Manager is installed, then run catsvrmg.sql:

   SVRMGR> @catsvrmg.sql
   
   

5. If Parallel Server is installed, then run catparr.sql:

   SVRMGR> @catparr.sql
   
   

6. If Oracle replication is installed, then run catrep.sql:

   SVRMGR> @catrep.sql
   
   

   Note: The Oracle8i Migration utility upgrades release 7.1 and release 7.2 databases to release 7.3. If the original Oracle7 production database was release 7.1 or 7.2 and the migration is run but abandoned before the conversion to Oracle8i, then the Oracle7 database will be left with a dictionary that is release 7.3. However, in such a case, you do not need to downgrade from release 7.3 to release 7.1.or 7.2; your release 7.1. or 7.2 software should work with the data dictionary without the need for further action.