Release 2 (8.1.6) for Windows 98
A85313-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Personal Edition Administrator's Guide Release 2 (8.1.6) for Windows 98 A85313-01 |
|
This chapter describes the options available to you when you have existing databases on your computer and want to install the latest release of Oracle8i Personal Edition. In particular, it describes how to migrate an Oracle7 database or upgrade an earlier Oracle8 database release to the current release of Oracle8i Personal Edition.
Specific topics discussed are:
Read this chapter if you have existing Oracle7 and/or Oracle8 databases on your computer and you want to install Oracle8i Personal Edition for Windows 98 Release 8.1.6. If you are installing Oracle8i Personal Edition on a computer that has no other Oracle database releases, you do not have to read this chapter.
|
Additional Information:
See Oracle8i Installation for Windows 98 if you want to install Oracle8i Personal Edition on a computer containing no other databases. |
|
Note: The generic Oracle8i Migration guide is the primary source of migration and upgrading information in the Oracle documentation set. You are frequently referred to the generic guide throughout this chapter, in particular to obtain information on what you must do before and after migrating or upgrading. Information on how to run the various migration and upgrade utilities is also provided in the generic guide, but the focus is on UNIX. This chapter provides information on using these utilities on Windows 98. |
If you already have Oracle7, and/or Oracle8 databases on your computer and want to install Release 8.1.6, the following options are available to you.
If you are not sure what option is best for you, read the following overview sections:
An Oracle home is a directory location where you can install software. Multiple Oracle homes functionality enables you to preserve your previous Release 7.x or 8.0.x databases in locations separate from where you will install Release 8.1.6. Installing a new database release in a separate Oracle home allows you to test it before migrating or upgrading your production databases to the new release. There have been modifications to multiple Oracle home functionality since it was introduced in Release 8.0.4. In particular, note:
This section explains the difference between migrating, upgrading, and downgrading, and lists the Oracle database versions that can be migrated or upgraded.
Migrating is the process of transforming an installed version of an Oracle database into a later version. For example, transforming an Oracle7 database to an Oracle8i database is migrating the database system.
Upgrading is the process of transforming an installed version of an Oracle database release into another release of the same version. For example, transforming an Oracle8 database Release 8.0.4 to Release 8.1.6 is upgrading the database system.
Downgrading is the process of transforming an installed version of an Oracle database from a later release back into an earlier release. For example, transforming an Oracle database from Release 8.1.6 back into Release 8.0.4 is downgrading, and transforming an Oracle database from Version8 back into Version7 is downgrading.
|
Additional Information:
See Chapter 10, "Downgrading to an Older Version8 Release" for information about downgrading to Release 8.0, or Chapter 11, "Downgrading to Version7" for information about downgrading to version7 of Oracle8i Migration. |
You can easily migrate or upgrade databases across multiple Oracle homes. If you use the graphical user interface (GUI) Oracle Data Migration Assistant, the earlier database instance on your system is displayed in a list box. You select the Oracle database instance you want to migrate or upgrade and the assistant takes care of any multiple Oracle homes issues.
If you use the command line tool MIG to migrate, or a U*.SQL script to upgrade, you need to copy files from one Oracle home directory to another. You must also ensure the PATH variable is set correctly so that any Oracle database tools you run are started from the correct Oracle home directory.
Check that your Oracle database release can be migrated or upgraded directly to Release 8.1.6. This table provides a list of the database releases you can migrate or upgrade and the tools you can use to perform these tasks:
| Oracle Database Release | Use This Tool... |
|---|---|
|
Release 7.3.4.x |
|
|
Release 8.0.4.0.0 to 8.1.x |
|
|
Release 8.1.5 to 8.1.6 |
An alternative method of migrating or upgrading is to:
The Export Utility puts all of the data in one large binary file that might require large amounts of disk space.
|
Additional Information:
See "Choose a Migration Method" in Chapter 2, "Preparing to Migrate" of Oracle8i Migration for information on when to use the Export/Import utilities for migrating a database. See "Exporting an Existing Database" and "Importing a Database" for information on using these tools on Windows 98. |
Oracle7 and Oracle8i clients can communicate either with Oracle7 or Oracle8i databases. This functionality gives you maximum flexibility when designing your network and deciding when to:
Consider the following "database coexistence" issues before you decide which of the above options is most suitable for your requirements:
Most Oracle7 applications can run on an Oracle8i database. Some applications cannot run on an Oracle8i database unless you upgrade them to versions that support Oracle8i databases. Contact your application vendor to check if your third-party applications are supported with.
Consider the following "client to database connection" issues before you decide if upgrading or migrating is appropriate for your environment:
As the following diagram depicts, an Oracle8i Client Release 8.1 requires Net8 Client Release 8.1, and Oracle8i Release 8.1 database requires Net8 Server Release 8.1.
The Oracle8 Client Release 8.1 and clients must be configured with a service name, as described in "Using the Local Naming Method" in Chapter 5, "Configuring the Network" of Net8 Administrator's Guide.
As the following diagram depicts, an Oracle8 Client Release 8.0 requires a compatible release of Net8 Client, an Oracle7 Client requires SQL*Net Client, and an Oracle8 database Release 8.1 requires Net8 Server Release 8.1 to connect successfully to an Oracle8i database Release 8.1.
While it is not necessary to reconfigure Release 8.0 and Release 7.x clients with a service name, Oracle Corporation recommends doing so to take advantage of new functionality. For example, in the TNSNAMES.ORA file:
net_service_name = (DESCRIPTION= (ADDRESS =...) (ADDRESS =...) ) (CONNECT_DATA= (SERVICE_NAME=SALES) )
This effect may be accomplished by manually replacing SID=SID with SERVICE_NAME=SERVICE_NAME or using the Net8 Assistant's compatibility mode. See "Using the Release 8.0/2.x Compatibility Mode" in Chapter 3 "Upgrading and Migrating" of Net8 Administrator's Guide.
Consider the following questions for an environment with Oracle7 clients connecting to an Oracle8 Release 8.1 database:
No. You must rebuild or upgrade applications to work with Net8 libraries.
No. If an Oracle7 client needs to connect to a remote Oracle8i database, only SQL*Net Client Release 2.x has to be configured on the Oracle7 client. Net8 is backward compatible with SQL*Net Release 2.x. The only limitation is that the new network features available with Net8 are unavailable with this connection type.
Yes. If the Oracle7 client needs to connect to a local Oracle8i database, you must have SQL*Net Client Release 2.x, Net8 Client, and Net8 Server in the same system. Note that Net8 Client and Net8 Server are already installed during the installation of Oracle8i or Oracle8.
If you are using Oracle7 Release 7.3.4 and SQL*Net Release 2.3.4, you can connect to the local Oracle8 database without specifying a service name. Oracle7 client automatically uses the Bequeath Protocol Adapter when connecting to an Oracle8 database.
An Oracle8 Client Release 8.1 requires Net8 Client Release 8.1, an Oracle7 Server requires SQL*Net Server, and an Oracle8 Server Release 8.0 requires Net8 Server Release 8.0.
The Release 8.1 clients must be configured with the SID of the database. For example, the TNSNAMES.ORA would have the following effect:
net_service_name = (DESCRIPTION= (ADDRESS =...) (ADDRESS =...) ) (CONNECT_DATA= (SID=SALES) )
This effect may be accomplished by manually editing the TNSNAMES.ORA file or using the Net8 Assistant's compatibility mode. See "Using Release 8.0/7.x Features and Connecting To a Release 8.0/7.x Service" in Chapter 3, "Upgrading and Migrating" of Net8 Administrator's Guide.
Additionally, the LISTENER.ORA on the database server must still be configured with the description of the SID, as described in "Statically Configuring a Listener" in Chapter 5, "Configuring the Network" of Net8 Administrator's Guide.
Consider the following questions for an environment with Oracle8 clients Release 8.1 connecting to an Oracle7 database.
No. If an Oracle8 client needs to connect to a remote Oracle7 database, only Net8 Client needs to be configured on the Oracle8 client. SQL*Net Release 2.x is upwards compatible with Net8. The only limitation is that the new network features available with Net8 are unavailable with this connection type.
Yes. If the Oracle8 client needs to connect to a local Oracle7 database, you need both SQL*Net Server Release 2.x and Net8 Client on the same system.
Oracle8i Personal Edition Server Release 8.1.6 for Windows 98 supports multiple Oracle Homes. You can run different versions of Oracle databases on the same computer system at the same time. However, each version can only access a database that is consistent with its version. For example, if you have Version 7 Server and Version 8 of Oracle installed on the same computer system, the Version 7 Server can access Version 7 databases, but not Version 8 databases, and the Version 8 Server can access Version8 databases but not Version7 databases. The only way for a Version8 database to read Version7 database files is to perform a migration. You should be aware that after migration the Version7 Server will no longer be able to read the migrated databases.
You can migrate your Oracle7 database to an Oracle8i database and have both Oracle7 and Oracle8i clients connecting to the Oracle8i database. You can not migrate your Oracle7 database to an Oracle8i database in the same Oracle home. The following figure illustrates this network configuration:
You can upgrade your Oracle8 database, for example, Release 8.0.4, to Release 8.1.6 and have both Oracle7 and Oracle8 clients connecting to the Release 8.1.6 Oracle8i database. You can upgrade databases either in the same Oracle home or across different Oracle homes. See "Upgrading an Oracle8 Database Release 8.0.x to 8.1.6" for instructions. The following figure illustrates this network configuration:
This section describes how to migrate an Oracle7 database to the current Oracle8i database release. You can choose either of the following tools to perform a migration:
Oracle Corporation recommends that new users use Oracle Data Migration Assistant to migrate databases because it is the easiest method to perform a migration. If you want to perform a migration manually using command line tools, use MIG.
Before you start a migration using the assistant or MIG, read the following sections:
The following table lists and describes the ten issues you should be aware of that can affect Oracle7 to Oracle8i migration.
| Issues That Affect Migration | Description |
|---|---|
|
|
|
The time it takes to migrate is not dependent on the size of the database, but on the number of objects in the data dictionary. For example, actual migration for a 3 1/2 GB database with 25,473 objects on a Sun E6000 with 20 CPUs, with datafiles stripped on the file system on 128 KB slices can take 1 1/2 hours. Remember to allow extra time for backing up and restoring database in case of problems. |
|
|
|
|
Make sure that all Oracle product versions, operating system versions, and third-party software versions are certified against Oracle8i. |
|
|
Migration leaves all objects (packages, triggers, views, and so on) invalid except for tables. All other objects must be made valid again by recompilation. This can either be done manually (preferably by building a dependency tree before migration from dependency), otherwise this is done automatically as the objects are first accessed. The latter will of course slow down initial access. All estimated or calculated statistics are lost during migration. These need to be recalculated to ensure proper functionality of the Cost Based Optimizer. Some bitmapped indexes will get invalidated. Check all bitmapped indexes in the DBA_INDEXES table and recreate any that are marked as status unusable. |
|
|
If you edit the registry for any reason during the migration process, you need to reboot your computer. |
|
|
Oracle7 read-only tablespaces are readable by Oracle8i and do not require any conversion. But to prevent Oracle8i rowid conversions to take place every time a table is accessed, the tablespaces in read-only mode should be made read-write. Perform full table scans on all tables in the tablespace. After the full table scans are complete, you can put the tablespaces in read-only mode again. |
|
|
You can return the database to an Oracle7 version up until the ALTER DATABASE CONVERT command is run. If a failure occurs during ALTER DATABASE CONVERT (when it is converting the physical file headers of the datafiles), you must restore the database from backup and rerun the migration. Do not open the database between running the migration and executing the ALTER DATABASE CONVERT command. |
|
|
To avoid restoring the entire database due to any failures during the ALTER DATABASE CONVERT, put all tablespaces, except SYSTEM and ROLLBACK into read-only or offline normal mode. This causes the ALTER DATABASE CONVERT command to only convert the datafile headers for SYSTEM and ROLLBACK. If any errors occur, you need only restore the datafiles for the SYSTEM and ROLLBACK and rerun the migration. If the migration is successful, the headers for the rest of the datafiles will be converted when they are read-write or online. |
|
|
Most migration problems can be avoided if a test migration is performed first. Performing a test migration helps raise any problems that can occur as well as letting you see the amount of time it takes to migrate. See "Test the Migration Process" in Chapter 2, "Preparing to Migrate" in Oracle8i Migration. |
When migrating from Oracle7 Server Release 7.3.x to Oracle8i Release 8.1.6, install the appropriate version of SQL*Net in the 7.3.x Oracle home before using Oracle Data Migration Assistant or MIG. Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net.
Oracle Data Migration Assistant helps you migrate data from an Oracle7 database to an Oracle8i database. During installation of Oracle8i Personal Edition, you are prompted to migrate a database with this assistant if Oracle Universal Installer detects that an earlier database release exists on your computer. If you do not want to migrate a database, uninstall the existing Oracle database, before installing the new database.
Complete the following steps before you use this assistant:
To migrate a database using Oracle Data Migration Assistant:
The following window appears:
This section describes how to use MIG to migrate your Oracle7 database to an Oracle8i database.
|
Note: Information on how to run MIG (sometimes referred to as the Migration Utility) is provided in Oracle8i Migration, but there the focus is on UNIX. This section provides information on using MIG on Windows 98. |
To migrate an Oracle7 database using MIG:
Step 1: What To Do Before Using MIG
Step 2: Shut Down the Oracle7 Database
Step 3: Back Up the Oracle7 Database
Step 4: Install MIG from CD-ROM
Step 6: Create Oracle8i Database Files
Step 7: Remove Oracle7 Software (Optional)
Complete the following steps before you use MIG:
When you are asked to enter commands at the SQL*Plus prompt, remember to use the appropriate version of the tool for the version of Oracle7 Server you are migrating:
| Use... | When Migrating From... |
|---|---|
|
SVRMGR23 |
Oracle7 Release 7.3.x |
Check that your database release can be directly migrated to Oracle8i Personal Edition. MIG only migrates databases that are Oracle7 Release 7.3.x or later.
| Oracle7 Release... | Enter at the MS-DOS Command Prompt... |
|---|---|
|
7.3.x |
|
| Oracle7 Release... | Enter at the SQLDBA or SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
| Oracle7 Release... | Enter at the SQLDBA or SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
The character set value is returned by the database. If the character sets are identical, then you can proceed to run MIG.
If the character sets are different, before you run MIG, you must set the NLS_LANG environment variable at the MS-DOS command prompt as follows:
AMERICAN_AMERICA.database character set
where database character set is substituted with the character set of your Oracle7 database. For example, if the character set of your Oracle7 database is JA16EUC, set the NLS_LANG environment variable as follows:
C:\> SET NLS_LANG=AMERICAN_AMERICA.JA16EUC
Messages output from MIG will now be in English. After MIG finishes, reset the NLS_LANG environment variable to its original value.
Shut down the database. Do not use SHUTDOWN IMMEDIATE or SHUTDOWN ABORT. If the database is not shut down before you start the migration, MIG stops and issues an error message. Also, if the database is not cleanly shutdown, any backup you make may be useless as it was taken while data was being written to the data files.
| Oracle7 Release... | Enter at the MS-DOS Command Prompt... |
|---|---|
|
7.3.x |
|
| Oracle7 Release... | Enter at the SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
The message Connected appears if you are successfully connected to the database.
| Oracle7 Release... | Enter at the SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
Back up the entire Oracle home directory and all its subdirectories.
|
WARNING: If anything goes wrong with the Oracle7 database during migration, you will need to restore the database from the backup. Back up your database now as a precaution! |
Ensure the database was cleanly shut down before you back up. Ensure you back up the database files in the following list (and any other database files you may have created). Also, back up any scripts you may have created.
To obtain the list of database files you must back up:
| Oracle7 Release... | Enter at the SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
| Oracle7 Release... | Enter at the SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
| Oracle7 Release... | Enter at the SQLPLUS Command Prompt... |
|---|---|
|
7.3.x |
|
See "Backing Up and Recovering Database Files", Oracle8 Concepts, Oracle8 Backup and Recovery Guide, and Oracle8i Administrator's Guide for information on how to back up a database.
You can install MIG in either of two ways depending if you want to install the Release 8.1.6 software that includes MIG or just MIG.
To install Oracle8i Personal Edition, including MIG:
The File Locations dialog box appears.
The Available Products dialog box appears.
The Upgrading and Migrating an Existing Database dialog box appears, telling you that a previous Oracle database is detected on your computer. The dialog asks if you want to migrate your older database to the current release using Oracle Data Migration Assistant.
Select a documentation option, and click Next.
The Summary window appears.
The Configuration Tools window appears.
DBMA window will pop-up. Click Cancel. Configration tool will show DBMA has failed, but that is OK.
The End of Installation window appears.
MIG has been installed as part of Oracle Utilities.
If you just want to install MIG, perform the following steps:
The File Locations dialog box appears.
The Available Products dialog box appears.
The Installation Types dialog box appears.
The Available Product Components dialog box appears.
Click Oracle Utilities, of which MIG is a component.
The Summary window appears.
The Configuration Tools window appears.
The End of Installation window appears.
MIG is located in C:\ORACLE\ORA81\BIN.
There are some tasks that you may have to perform before you run MIG.
| PersonalOracle7 Release... | Enter at the MS-DOS Command Prompt... |
|---|---|
|
7.3 |
|
C:\> SET ORACLE_SID=ORCL
C:\> MIG PFILE=ORACLE_HOME\DATABASE\INITSID.ORA SPOOL=C:\MIG.LOG
The MIG command creates the MIGSID.ORA file that is required in a later step to create Oracle8i Personal Edition control files.
MIG runs and displays the operations being performed. MIG can take considerable time to run. Please wait until it has finished running.
Check the results after running MIG. If there are error messages, see Appendix A, "Troubleshooting Migration Problems" of Oracle8i Migration for more information before going to Step 9.
C:\> KNLSTOP
MIG creates a convert file that contains the information of the Version7 control file. Later in the migration process, the convert file is used when you execute the ALTER DATABASE CONVERT command to create a new control file for Version8.
The default location of the convert file is ORACLE_BASE\ORACLE_HOME\RDBMS where ORACLE_HOME is the Version8 Oracle home. The default filename is CONVERT.ORA.
After successfully running MIG, perform a cold backup of the Oracle7 database. This backup serves the following purposes:
|
Additional Information:
See Chapter 10, "Developing Applications", Oracle8 Concepts, Oracle8 Backup and Recovery Guide, and Oracle8i Administrator's Guide for information on how to back up a database. |
CONTROL_FILE = ORACLE_HOME\DATABASE\NEWCONTROL.ORA
DISK_ASYCH_IO = FALSE
See Oracle8 Reference for a complete description of the DISK_ASYNCH_IO parameter and other initialization parameters.
COMPATIBLE=8.0.5.0.0
|
Additional Information:
Some new features of Oracle8i Release 8.1.x require a compatibility setting of 8.1.0 or higher. See Chapter 8, "Compatibility and Interoperability" of Oracle8i Migration for more information. |
SQL> STARTUP NOMOUNTPFILE=ORACLE_HOME\DATABASE\INITSID.ORA
|
WARNING: Successful execution of this command is the point of no return to Oracle7. If you need to return to the Oracle7 database, please restore it from the backup you made in "Step 3: Back Up the Oracle7 Database". If an error occurs during this step, you must correct the condition(s) that caused the error(s). |
This command uses the MIGSID.ORA file that was created earlier when you ran MIG. All data files that are online are converted to Oracle8i Personal Edition format, and new control files are built. Control files are considerably larger in Version8 than in Version7. Control files in the tens of kilobytes size range in Version7 could be expanded into the range of tens of megabytes automatically during migration to Version8. This size increase could be important if a control file is on a raw device or if its available disk space is restricted.
All rollback segments that are online when the Oracle8i database is opened are also opened and converted to the Oracle8i database format.
SQL> SPOOL CATOUT.LOG
Oracle Corporation supplies other scripts with Oracle8i Personal Edition that create additional structures you can use in managing your database and creating database applications. These scripts are also located in ORACLE_HOME\RDBMS\ADMIN. See the chapter "SQL*Scripts" in Oracle8 Reference for a complete list and descriptions of available scripts.
SQL> SHUTDOWN
Performing a clean database shutdown flushes all caches, clears buffers, and performs other Relational Database Management System (RDBMS) housekeeping activities. These measures are an important final step to ensure the integrity and consistency of the newly migrated Release 8.1.6 database.
The Oracle7 database has now been migrated to the Oracle8i database and is ready for use.
You can remove Oracle7 software if you have successfully migrated to Oracle8i Personal Edition and have a backup of the Oracle7 software. Oracle Installer warns you of any product dependencies that might cause problems if particular products are removed, and prompts you to confirm the deinstallation.
To remove Oracle7 software:
The Software Asset Manager window appears.
This section describes how to upgrade an Oracle8 database Release 8.0.x to Release 8.1.6. You can choose either of the following database tools to upgrade:
Oracle Corporation recommends that new users use Oracle Data Migration Assistant to upgrade databases because it is the easiest and quickest method to perform an upgrade. If you already have upgrade scripts from a previous Oracle database release, you can edit them to include the new upgrade scripts.
Oracle Data Migration Assistant helps you upgrade data from an Oracle8 database Release 8.0.x to Release 8.1.6. During installation of Oracle8i Personal Edition, you are prompted to upgrade a database with this assistant if Oracle Universal Installer detects that a Release 8.0.x database exists on your system. If you do not want to upgrade during the installation process, you can just install this assistant and use it later.
Before you use this assistant, ensure the Oracle8 database to be upgraded is at least Release 8.0.3.0.0
To upgrade a database using Oracle Data Migration Assistant:
The following window appears:
You can run SQL scripts in SQL*Plus to upgrade an Oracle8 database Release 8.0.x to Release 8.1.6.
Upgrading consists of the following tasks:
Step 1: Shut Down the Release 8.0.x Database
Step 2: Back Up the Release 8.0.x Database
Step 3: Edit the COMPATIBLE Parameter in the 8.0.x INITSID.ORA File
Step 4: Install Oracle8i Personal Edition Release 8.1.6
SQL> CONNECT INTERNAL/PASSWORD
SQL> SHUTDOWN
Perform a full offline backup of the database.
Ensure the database is cleanly shutdown before you back up. Ensure you back up the database files in the following list (and any other database files you may have created). Also, back up any scripts you may have created.
|
SYS1SID.ORA, USR1SID.ORA, RBS1SID.ORA, TMP1SID.ORA |
|
|
INITSID.ORA |
|
|
LOG1SID.ORA, LOG2SID.ORA |
|
|
CTL1SID.ORA |
To obtain the list of database files you must back up:
SQL> SPOOL V8DBFILES.LOG
SQL> SELECT MEMBER FROM V$LOGFILE;
SQL> SELECT NAME FROM V$DATAFILE;
SQL> SELECT VALUE FROM V$PARAMETER WHERE NAME = 'control_files';
See Chapter 10, "Developing Applications", Oracle8 Concepts, Oracle8 Backup and Recovery Guide, and Oracle8i Administrator's Guide for information on how to back up a database.
Ensure the COMPATIBLE parameter is left unset if it has not been set in the INITSID.ORA file. Leave the COMPATIBLE parameter unchanged if it has been previously set.
|
Additional Information:
Some new features of Oracle8i Release 8.1.x require a compatibility setting of 8.1.0. See Chapter 7 "Compatibility and Interoperability" of Oracle8i Migration for more information. |
The File Locations dialog box appears. Do not change the text in the Source: text box. This is the location of files for installation.
The Available Products dialog box appears.
The Upgrading and Migrating an Existing Database dialog box appears, telling you that a previous Oracle database is detected on your computer. The dialog asks if you want to migrate your older database to the current release using Oracle Data Migration Assistant.
Select a documentation option, and click Next.
The Summary window appears.
The Configuration Tools window appears.
DBMA window will pop-up. Click Cancel. Configration tool will show DBMA has failed, but that is OK.
C:\> SET ORACLE_SID=ORCL
SQL> SPOOL UPGRADE.LOG
| To Upgrade... | Run Script1 | Enter at the SQL*Plus Prompt... |
|---|---|---|
|
8.0.4.0 or 8.0.4.1 to 8.1.6 |
U0800040.SQL |
where |
|
1
The CATALOG.SQL and CATPROC.SQL scripts, which create the system catalog views and all the necessary packages for using PL/SQL, are run whenever you execute any of these U*.SQL scripts. |
SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLRP.SQL
Check the spool file UPGRADE.LOG you created in Step 6 and verify that every package and procedure compiled successfully. Correct any problems you find in the file. If you are upgrading from Release 8.0.2, also check the UPGRADE2.LOG spool file.
SQL> SPOOL UTLRESULT.LOGSQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLCONST.SQLSQL> SPOOL OFF
A bad date constraint involves invalid date manipulation. An invalid date manipulation is one that implicitly assumes the century in the date, causing problems at the year 2000. The UTLCONST.SQL script runs through all of the check constraints in the database and sets constraints as bad if they include any invalid date manipulation. UTLCONST.SQL selects all the bad constraints at the end. After you run the script, the UTLRESULT.LOG file includes all the constraints that have invalid date constraints. UTLCONST.SQL does not correct bad date constraints, but it does disable them. Either drop the bad constraints or recreate them after you make the necessary changes.
SQL> EXIT
Some new features of Oracle8 Release 8.1.x require a compatibility setting of 8.1.0. See Chapter 7 "Compatibility and Interoperability" of Oracle8i Migration for more information.
Additional Information:
Your database is upgraded to Release 8.1.6.
During migration from Oracle 7.x or Oracle 8.0.x to Oracle8i, the following issues need to be addressed:
SQL*Net and Net8 8.1 use configuration files from ORACLE_HOME\network\admin by default, while Net8 8.0 uses configuration files from ORACLE_HOME\net80\admin by default. If you want all the Oracle products to use configuration files from the same location, you can set the registry variable TNS_ADMIN.
Before installing an Oracle8i server ensure that any existing Net8 or SQL*Net listeners on the same computer are stopped. An existing listener may prevent the Net8 8.1 listener from starting during the Oracle8i install due to listener endpoint conflicts with an existing listener.
If Net8 8.1 listener could not be started during Oracle8i installation due to conflicts in listening endpoints, you can start your Net8 8.1 listener by using the listener control program:
From a command prompt:
lsnrctl start <listener_name>
where <listener_name> is LISTENER for typical install or the name given during custom install.
When you migrate Oracle7 or Oracle8.0 database to an Oracle8i database, the SID of the database needs to be removed from the Oracle7/8.0 home LISTENER.ORA and added to Oracle8i home LISTENER.ORA file.
In Oracle8i, when the LISTENER.ORA contains the TCP/IP system name in ADDRESS, the Listener listens on all addresses for the system. Therefore, even if a system has multiple interface cards with different TCP/IP host names, listening using any of the host names ensures that the Listener will listen on all interface cards. It is an error to configure multiple addresses for the same port in LISTENER.ORA.
For Oracle7 or Oracle8.0, the Listener only listened for the TCP/IP host name specified in LISTENER.ORA and you had to specify listening addresses for multiple TCP/IP host names of a system. The default LISTENER.ORA created for Oracle7/ Oracle8.0 contained multiple addresses, for example,
LISTENER = (ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=system1)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)) )
The above addresses are invalid for Oracle8i and the ADDRESS line containing 127.0.0.1 must be removed.
For Oracle7 and Oracle8.0 default installation, native authentication is turned off. Make sure that native authentication, has not been set to sqlnet.ora for Oracle client and Oracle server, in other words:
sqlnet.authentication_services = (NTS)
This should be commented if present in sqlnet.ora file.
When migrating from Oracle7 Server Release 7.3.x to Oracle8i Release 8.1.6, install the appropriate version of SQL*Net in the 7.3.x Oracle home before using Oracle Data Migration Assistant or MIG. Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net.
The Oracle Optimal Flexible Architecture (OFA) is a feature of Oracle8i for Windows 98 Release 8.1.6. It has been available for Oracle on UNIX for some years. OFA is a set of file naming and placement guidelines recommended by Oracle Corporation for Oracle software and databases. It can also be thought of as a set of "good habits" to adopt when organizing Oracle directories and files on your computer. All Oracle products on the Oracle8i for Windows 98 are OFA-compliant; that is, Oracle Universal Installer places Oracle products in directory locations that follow the OFA guidelines.
One of the many benefits of OFA is that you can separate Oracle software executables from database files. Previously, database files were placed in ORACLE_HOME\DATABASE, (for example, C:\ORAWIN95\DATABASE) a subdirectory of the Oracle home directory that also contained Oracle software. Using OFA, you can put Oracle software in X:\ORACLE_BASE\ORACLE_HOME and database files in X:\ORACLE_BASE\ORADATA\DB_NAME.
|
Additional Information:
For more information on OFA and the type of directory structure where you should place your database files after migration or upgrade, see "Optimal Flexible Architecture Overview". |
Oracle8i Navigator uses the PO8 user account to connect to the local Oracle8i Personal Edition database. Create the PO8 user account for the Oracle8i Navigator to function properly.
To create the PO8 user account:
where MANAGER is the password for the SYSTEM account when Oracle8i Personal Edition is initially installed. If you have changed this password, enter the new one.
|
 Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|