v
5 After Migrating the Database
Back Up the Version 8 Database 5-2
Check for Bad Date Constraints 5-2
Rebuild Invalidated Bitmap Indexes 5-3
Test the Database and Compare Results 5-3
Tune the Target Database 5-3
Add New Features as Appropriate 5-4
Develop New Administrative Procedures as Needed 5-4
6 Upgrading Version 7 Applications
Upgrading Oracle Applications to Version 8 6-2
XA Calls: Incompatibility with Release 7.1 XA Calls 6-2
Upgrading Precompiler and OCI Applications 6-2
Upgrading Precompiler Applications 6-3
Simplified Upgrading of Existing Applications 6-4
Upgrading OCI Applications: Enabling Constraints 6-5
OCI Application Link Line 6-5
Applications Using Version 6 OCI Libraries 6-6
Upgrading LONGs to LOBs 6-6
Upgrading Version 7 Forms or Developer/2000 Applications 6-6
Data Dictionary Views Update 6-6
Upgrading SQL*Plus Scripts 6-7
PL/SQL V2 Compatibility Mode 6-7
PLSQL_V2_COMPATIBILITY Flag 6-8
Keyword Behavior Differences: Version 7 vs. Version 8 6-9
New Keywords or Types Behavior Differences: Version 7 vs. Version 8 6-9
SQL*Net or Net8 6-10
Upgrading SQL*Net V1 to SQL*Net V2 6-10
Version 7 Net2 Clients and Connection Manager 6-10
Net8 Features Available to Relinked Version 7 Clients 6-11
Version 8 Net8 Clients 6-11
Backup Management: EBU and Recovery Manager 6-12
Dictionary Protection 6-12
Password Management 6-13
Version 7 or Lower Client with Version 8 Server 6-14
vi
Version 8 Client with Version 7 or Lower Server 6-14
Export/Import Usage, Partitioned Objects 6-14
Migration and Compatibility Issues for Thread Safety, OCI 6-14
Upgrade and Compatibility Issues for Standby Database 6-15
Compatibility Issues for Export/Import 6-16
Downward Compatibility Techniques and Limitations 6-16
NCHAR and NLS Use 6-16
Migration and NCHAR and NLS 6-16
NCHAR and NLS Compatibility and Interoperability 6-17
7 Migration Issues for the Version 8 ROWIDs
Migrating Applications and Data 7-2
DBMS_ROWID Package 7-3
ROWID Conversion Types 7-3
ROWID Conversion Functions 7-4
Conversion Procedure Examples 7-5
Example 1 7-5
Example 2 7-6
Example 3 7-6
Example 4 7-6
Example 5 7-6
Snapshot Refresh 7-6
Pre-Version 8 Client Compatibility Issues 7-7
ROWID-Related Migration Questions and Answers 7-7
8 Upgrading and Downgrading
Upgrading to a New Version 8 Release 8-2
Product Configurations and Upgrading 8-4
Upgrading the Advanced Queuing Option 8-6
New Fields Enabled for the AQ$_AGENT Data Type 8-6
The Extended Address Field 8-6
New Dictionary Tables 8-7
Downgrading 8-7
Downgrading from Release 8.0.4 to Release 8.0.3 8-7
Downgrading Version 8 to Release 7.x 8-10
vii
A Migration Utility Messages
B Control File Fixed View Changes
Date Columns in Control File Views B-1
Obsolete Views Kept in Version 8 B-2
V$LOG_HISTORY Retained and Upgraded B-2
V$ARCHIVED_LOG Replaces V$LOG_HISTORY B-2
V$BACKUP_CORRUPTION B-4
V$BACKUP_DATAFILE B-5
V$BACKUP_DEVICE B-6
V$BACKUP_PIECE B-6
V$BACKUP_REDOLOG B-7
V$BACKUP_SET B-7
V$CONTROLFILE_RECORD_SECTION B-8
V$COPY_CORRUPTION B-8
V$DATABASE New Columns B-9
V$DATAFILE New Columns B-10
V$DATAFILE_COPY B-11
V$DATAFILE_HEADER B-12
V$DELETED_OBJECT B-13
V$INSTANCE B-14
V$OFFLINE_RANGE B-15
V$RESOURCE_LIMIT B-16
V$TABLESPACE B-16
V$THREAD B-16
Changed Column Types B-17
Database Scheduling Facilities B-17
Changed Fixed Views B-17
New Fixed Views B-18
Table (View) Name Changes B-18
viii
C Version 8 INIT.ORA Changes
COMPATIBLE Parameter C-2
Migrating or Upgrading to Release 8.0.4 C-2
Data Dictionary Protection C-4
DML_LOCKS C-4
NCHAR and NLS Parameters and Compatibility C-4
Pre-Version 8 Parameters Renamed in Version 8 C-5
Release 7.3 Parameters Obsolete in Version 8 C-6
REPLICATION_DEPENDENCY_TRACKING for the Replication Server C-7
Features No Longer Supported in Version 8 C-7
SERIALIZABLE=TRUE or _SERIALIZABLE C-7
D New SQL Key and Reserved Words
E General System Requirements for Migration
Memory Requirements E-2
Basic Memory Requirements E-2
Version 8 Executables E-2
Concurrent Access E-3
Using Oracle Parallel Server E-4
Version 8 New Sizes and Limits E-4
CHAR and NCHAR Maximum Size Support E-5
Index
ix
Send Us Your Comments
Oracle8 Migration, Release 8.0
Part No. A58243-01
Oracle Corporation welcomes your comments and suggestions on the quality and usefulness of this
publication. Your input is an important part of the information used for revision.
■ Did you find any errors?
■ Is the information clearly presented?
■ Do you need more information? If so, where?
■ Are the examples correct? Do you need more examples?
■ What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the chapter,
section, and page number (if available). You can send comments to us in the following ways:
■ electronic mail - infodev@us.oracle.com
■ FAX - telephone number. Attn: Server Technologies Documentation Manager
■ postal service:
Oracle Corporation
Server Technologies Documentation Manager
500 Oracle Parkway
Redwood Shores, CA 94065
United States
If you would like a reply, please give your name, address, and telephone number below.
x
xi
Preface
This manual guides you through the process of planning and executing migrations,
upgrades, and downgrades for the Oracle database system. It describes basic
principles and Oracle product features, and it contains step-by-step instructions for
migration, upgrade, and downgrade operations.
The following topics are covered in this preface:
■ Audience and Assumed Knowledge
■ How Oracle8 Server Migration is Organized
■ Conventions Used in This Manual
■ Your Comments Are Welcome
Oracle8 Migration contains information that describes the features and functionality
of the Oracle8 and the Oracle8 Enterprise Edition products. Oracle8 and Oracle8
Enterprise Edition have the same basic features. However, several advanced
features are available only with the Enterprise Edition, and some of these are
optional. For example, to use Objects, you must have the Enterprise Edition and the
Objects Option.
See Also: Getting to Know Oracle8 and the Oracle8 Enterprise
Edition for information about the differences between Oracle8 and
the Oracle8 Enterprise Edition and the features and options that
are available to you.
xii
Audience and Assumed Knowledge
This manual is for database administrators (DBAs), application programmers,
security administrators, system operators, and anyone who plans or executes
migration, upgrade, or downgrade operations on Oracle software. Users are
assumed to be familiar with Version 7 of the Oracle server (Oracle7) and with their
operating system environment. Users also are assumed to be familiar with Oracle
database management system (DBMS) concepts. The first chapter of Oracle8
Concepts provides a comprehensive introduction to the concepts and terminology
used in this migration manual.
How Oracle8 Server Migration is Organized
This manual contains the following chapters and appendices:
Chapter 1: Migration Overview
This chapter summarizes migration procedures and the responsibilities of database
administrators and application programmers.
Chapter 2: Preparing to Migrate
This chapter describes the steps to complete before migrating the database.
Chapter 3: Migrating Using the Migration Utility
This chapter describes how to migrate a version 7 database to version 8 using the
Migration Utility.
Chapter 4: Migrating Using Export/Import
This chapter describes how to migrate a version 7 or version 6 database to version 8
using the Export and Import utilities.
Chapter 5: After Migrating the Database
This chapter describes the steps to complete after migrating the database to
version 8.
Chapter 6: Upgrading Version 7 Applications
This chapter describes how to upgrade version 7 applications and tools for use
with version 8.
xiii
Chapter 7: Migration Issues for the Version 8 ROWIDs
This chapter covers issues associated with the new version 8 ROWIDs in relation to
migrating columns containing ROWIDs to version 8.
Chapter 8: Upgrading and Downgrading
This chapter describes the steps to complete to upgrade a database from release
8.0.3 to release 8.0.4. This chapter also covers downgrading a version 8, release 8.0.4
database to release 8.0.3 or to version 7, release 7.3.
Appendix A: Migration Utility Messages
This appendix lists the messages displayed by the Migration Utility and includes
an explanation for each message, probable cause(s) of each message, and suggested
corrective action for each error condition.
Appendix B: Control File Fixed View Changes
This appendix briefly describes changes from version 7, release 7.3 to the version 8
server Control File Fixed Views.
Appendix C: Version 8 INIT.ORA Changes
This appendix briefly describes Oracle INIT.ORA file initialization parameters
important for migration. Specifically, this appendix describes initialization
parameters that have been added, changed, or dropped since release 7.3.
Appendix D: New SQL Key and Reserved Words
This appendix lists the keywords and reserved words new to version 8.
Appendix E: General System Requirements for Migration
This appendix discusses system requirements that may be important for successful
migration to version 8.
xiv
Conventions Used in This Manual
The following conventions are used in this manual:
UPPERCASE Words Uppercase calls attention to command keywords, object names,
parameters, filenames, and so on. For example:
“If you create a private rollback segment, its name must be
included in the ROLLBACK_SEGMENTS parameter in the
PARAMETER file.”
Italicized Words Italicized words indicate the first occurrence and definition of a
term, as in the following example:
“A database is a collection of data to be treated as a unit. The
general purpose of a database is to store and retrieve related
information, as needed.”
Italicized words also indicate emphasis and book titles.
Code Examples SQL, Server Manager line mode, and SQL*Plus commands and
statements are displayed in a fixed-width font, separated from
normal text, as in the following example:
INSERT INTO emp (empno, ename) VALUES (1000, ’SMITH’);
ALTER TABLESPACE users ADD DATAFILE ’users2.ora’ SIZE 50K;
Example statements may include punctuation, such as commas
or quotation marks. All punctuation in example statements is
required. Depending on the application, a semicolon or other
terminator may or may not be required to end a statement.
Uppercase words in example statements indicate the keywords
within Oracle SQL. When you issue statements, however,
keywords are not case sensitive.
Lowercase words in example statements indicate words
supplied only for the context of the example. For example,
lowercase words may indicate the name of a table, column, or
file.
Không có nhận xét nào:
Đăng nhận xét