Preface

The Oracle Migration Workbench for MS Access Reference Guide provides detailed information about migrating a database from MS Access 2.0, MS Access 95, or MS Access 97 to Oracle8 or Oracle8i. This reference guide describes several differences between MS Access and Oracle, and outlines how those differences are dealt with by Oracle Migration Workbench (Migration Workbench) during the conversion process.

Audience

This reference guide is intended for anyone who is involved in converting an MS Access database to Oracle using the Migration Workbench.

What You Should Already Know

You should be familiar with relational database concepts and with the operating system environments under which you are running MS Access and Oracle.

How the Oracle Migration Workbench for MS Access Reference Guide is Organized

This reference guide is organized as follows:

Chapter 1, "Overview"

Introduces the Migration Workbench and outlines features of this tool.

Chapter 2, "The Migration Process"

Outlines the architecture of MS Access and Oracle, explains how to prepare your MS Access database for migration, and describes how to migrate from MS Access to Oracle using the Migration Workbench.

Chapter 3, "Data Types, Reserved Words, and Functions"

Illustrates the migration of data types and built-in functions from MS Access to Oracle and provides a list of Oracle8i reserved words.

Chapter 4, "Troubleshooting"

Provides tips on how to migrate hyperlinks and how to perform a manual migration if necessary

Chapter 5, "Performance Tuning"

Outlines some measures that can be taken to tune your database.

Appendix A, "MS Access Error Messages"

Provides a list of Microsoft Jet database engine errors.

Appendix B, "Code and Query Samples"

Uses code examples to illustrate the migration process.

How to Use This Reference Guide

Every reader of this reference guide should read Chapter 1, "Overview". That chapter provides an introduction to the concept and terminology of the Migration Workbench.

Conventions Used in This Reference Guide

The following typographic conventions are used in this reference guide:

Table 0-1 Typographic Conventions

Convention	Description
UPPERCASE	Uppercase text indicates case-insensitive filenames or directory names, commands, command keywords, initializing parameters, data types, table names, or object names. Enter text exactly as spelled; it need not be in uppercase.
[UPPERCASE]	Key names are represented by uppercase letters enclosed in brackets, as square in [RETURN].
Italicized Characters	Italic type in text indicates the complete names of documents, emphasizes a single word or short phrase, indicates variables, or indicates the first instance of an important word or phrase.
Code Examples	Monospace text distinguishes examples of commands and statements from the rest of the text. Monospace text must be entered exactly as shown. Example statements may include punctuation, such as commas or quotation marks. All punctuation in example statements is required. All example statements terminate with a semicolon (;). Depending on the application, a semicolon or other terminator may or may not be required to end a statement.
UPPERCASE in Code Examples	Uppercase words in example statements indicate the keywords within Oracle SQL. When you issue statements, however, keywords are not case sensitive.
lowercase in Code Examples	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.
Bold	Boldface type in text indicates emphasis with stress, a term defined in the text or the glossary or in both locations, or case-sensitive filenames or directory names.
>	Right-facing angle brackets appear in navigation paths to indicate movement from one Web page to another.
{ }	Curly braces indicate that one of the enclosed arguments is required. Do not enter the braces themselves.
[ ]	Square brackets indicate that the enclosed arguments are optional. Do not enter the brackets themselves.
|	A vertical bar separates alternative items that may be optional or required. Do not type the vertical bar.
...	Ellipses indicate that the preceding item can be repeated. You can enter an arbitrary number of similaritems. In code fragments, an ellipsis means that code not relevant to the discussion has been omitted. Do not type the ellipsis.
SQL*Plus Prompts	The SQL*Plus prompt, SQL>, appears in SQL statement and SQL*Plus command examples. Enter your response at the prompt. Do not enter the text of the prompt, SQL>, in your response.
MS-DOS Prompts	The MS-DOS prompt, >, appears in MS-DOS command examples. Enter your response at the prompt. Do not enter the prompt in your response.
Storage Measurements	Storage measurements use these abbreviations: K, for kilobyte which equals 1024 bytes M, for megabyte which equals 1 048 576 bytes G, for gigabyte which equals 1 073 741 824 bytes