Preface

This guide provides detailed information about migrating a database from IBM DB2/400 V4R5 to Oracle8, Oracle8i, or Oracle8i Appliance. It describes several differences between IBM DB2/400 V4R5 and Oracle and describes how those differences are handled by the Migration Workbench during the conversion process.

It also provides guidelines on how to modify IBM DB2/400 V4R5 applications to work with the new Oracle database. If you have an investment in IBM DB2/400 V4R5 applications, you can retain this investment while adding the advanced features of Oracle to the application architecture.

This preface contains the following sections:

• Audience
  
  
• What You Should Already Know
  
  
• How This Reference Guide is Organized
  
  
• How to Use This Reference Guide
  
  
• Related Documentation
  
  
• Conventions

Audience

This guide is intended for anyone using the Migration Workbench to convert an IBM DB2/400 V4R5 database to Oracle.

What You Should Already Know

You should be familiar with relational database concepts and with the operating system environments under which you are running Oracle and IBM DB2/400 V4R5.

How This Reference Guide is Organized

This reference guide is organized as follows:

• Chapter 1, "Overview"

  Introduces the Migration Workbench and describes the features of this tool.

• Chapter 2, "Oracle and IBM DB2/400 V4R5 Compared"

  Contains detailed information about the differences between data types, data storage concepts, and schema objects in IBM DB2/400 V4R5 and Oracle.

• Chapter 3, "Migration Process"

  Describes the architecture of IBM DB2/400 V4R5 and Oracle. It explains how to prepare the IBM DB2/400 V4R5 database for migration. This chapter also describes how to migrate from IBM DB2/400 V4R5 to Oracle using the Migration Workbench.

• Chapter 4, "Troubleshooting"

  Describes how to solve problems you might encounter when using the Migration Workbench.

How to Use This Reference Guide

You must read Chapter 1, "Overview", which provides an introduction to the concepts and terminology of the Migration Workbench.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/

Accessibility of Code Examples in Documentation

JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.

Related Documentation

For more information, see these Oracle Migration Workbench documents:

• Oracle Migration Workbench Frequently Asked Questions (FAQ)
  
  
• Oracle Migration Workbench Release Notes

To download release notes, installation documentation, white papers, or other collateral, visit the Oracle Technology Network (OTN). You must register online before using OTN. You can register at:

http://otn.oracle.com/membership/index.htm

If you already have a user name and password for OTN, then you can go directly to the Migration Workbench documentation section of the OTN Web site at:

http://otn.oracle.com/tech/migration/workbench

Conventions

This section describes the various conventions used in the text and code examples in this documentation. It describes:

• Conventions in Text
  
  
• Conventions in Code Examples

Conventions in Text

This guide uses various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use:

Convention	Meaning	Example
Bold	Bold type indicates GUI options. It also indicates terms that are defined in the text, terms that appear in the glossary, or both.	The C datatypes such as ub4, sword, or OCINumber are valid. When you specify this clause, you create an index-organized table.
Italics	Italic type indicates book titles, emphasis, syntax clauses, or placeholders.	Reference Guide Run Uold_release.SQL where old_release refers to the release you installed before upgrading.
UPPERCASE (monspace)	Uppercase monospace type indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, user names, and roles.	You can specify this clause only for a NUMBER column. You can back up the database using the BACKUP command.
lowercase (monspace)	Lowercase monospace type indicates executables and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values.	Enter sqlplus to start SQL*Plus. The department_id, department_name, and location_id columns are in the hr.departments table.

Conventions in Code Examples

Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace font and are separated from normal text as shown in this example:

SELECT * FROM dba_users WHERE username = 'MIGRATE';

The following table describes typographic conventions used in code examples and provides examples of their use:

Convention	Meaning	Example
Square Brackets [ ]	Indicates that the enclosed arguments are optional. Do not enter the brackets.	DECIMAL (digits [ , precision ])
Curly Braces { }	Indicates that one of the enclosed arguments is required. Do not enter the braces.	{ENABLE | DISABLE}
Vertical Line |	Separates alternative items that may be optional or required. Do not type the vertical bar.	{ENABLE | DISABLE} [COMPRESS | NOCOMPRESS]
Ellipses ...	Indicates that the preceding item can be repeated. You can enter an arbitrary number of similar items. In code fragments, an ellipsis means that code not relevant to the discussion has been omitted. Do not type the ellipsis.	CREATE TABLE ... AS subquery; SELECT col1, col2, ... , coln FROM employees;
Italics	Indicates variables that you must supply particular values.	CONNECT SYSTEM/system_password
UPPERCASE	Indicates case-insensitive filenames or directory names, commands, command keywords, initialization parameters, data types, table names, or object names. Enter text exactly as spelled; it need not be in uppercase.	SELECT last_name, employee_id FROM employees; SELECT * FROM USER_TABLES; DROP TABLE hr.employees;
lowercase	Indicates words supplied only for the context of the example. For example, lowercase words may indicate the name of a table, column, or file.	SELECT last_name, employee_id FROM employees; sqlplus hr/hr