Preface

The Oracle Migration Workbench Frequently Asked Questions (FAQ) provides questions and answers about to the Oracle Migration Workbench. It is a useful guide regardless of the conversion tool you are using to perform a database migration, however Oracle Corporation recommends that you use the Migration Workbench to migrate from your existing database platform to an Oracle Server. This preface contains the following sections:

Audience

This guide is intended for anyone migrating a Microsoft Access, Informix Dynamic Server, Microsoft SQL Server, Sybase Adaptive Server, or MYSQL Server database to Oracle8i or higher.

What You Should Already Know

You should be familiar with relational database concepts and with the operating system environment of your Oracle Server and the database that you want to migrate.

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.

Conventions Used in This Guide

The following typographic conventions are used in this guide:

Convention	Description
UPPERCASE	Uppercase text indicates case-insensitive file names or directory names, commands, command keywords, initialization parameters, data types, table names, or object names. Enter text exactly as spelled.
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.
[]	In text, key names are represented by uppercase letters enclosed in brackets, for example [RETURN]. In command syntax, brackets indicate optional items: `cvtcrt` termname `[`outfile`]`
Italics	Italic type indicates variables, including variable portions of file names. It is also used for emphasis.
Code Examples	Monospace type indicates commands, directory names, user names, path names, file names, and text quoted from screen output. 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.
Bold	Boldface type indicates emphasis.
{ }	Braces indicate required items: `.DEFINE {macro1}`. Do not enter the braces.
\|	A vertical line indicates a choice within braces or brackets: SIZE filesize [K\|M] Do not enter the vertical bar.
...	Ellipses indicate an arbitrary number of similar items: `CHKVAL fieldname` value1 value2 ... valueN Do not type the ellipsis.
SQL*Plus prompt	The SQLPlus prompt, `SQL>`, appears in SQL statements and SQLPlus command examples. Do not enter the prompt when entering the examples.
Microsoft-DOS prompt	The Microsoft-DOS prompt, >, appears in Microsoft-DOS command examples. Do not enter the prompt when entering the examples.
Storage measurements	Storage measurements use the following 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