|
Oracle® Migration Workbench User's Guide
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 Part No. B15857-01 |
|
 Previous |
 Next |
|
Oracle® Migration Workbench User's Guide
Release 10.1.0 for Microsoft Windows 98/2000/NT/XP and Linux x86 Part No. B15857-01 |
|
|
Previous |
Next |
acceptance test
A collection of tests that the migrated database must pass before the source database is considered successfully migrated to the destination database. The tests are designed around how the users avail of the system.
application system
The database schema and application files that have been developed for a third-party database environment.
Binary Large Object (BLOB)
A large object data type whose content consists of binary data. This data is considered raw as its structure is not recognized by the destination database.
Capture wizard
An intuitive wizard that takes a snapshot of the data dictionary of the source database, populates the Source Model, and optionally creates the Oracle Model.
CHAR data type
An Oracle data type provided for ANSI/ISO compatibility. A CHAR column is a fixed-length column and can contain any printable characters, such as A, 3, &, or blanks, and can have from 1 to 2000 bytes or can be null.
client
A system that runs an Oracle-supported application and connects to the shared databases on an Oracle server.
data type
The kind of information contained in a variable or dimension (for example, whole numbers, decimal numbers, alphabetic characters, logical data). Each variable or dimension can have only one type of data.
dependency
A relationship between two migration entities. For example, a database view is dependent upon the table to which it refers.
destination database
The Oracle database where you want to populate the migrated database objects.
foreign key
Integrity constraint that requires each value in a column or set of columns to match a value in a related table's UNIQUE or PRIMARY KEY. FOREIGN KEY integrity constraints also define referential integrity actions that dictate what Oracle should do with dependent data if the data it references is altered.
migration component
Part of an application system that you can migrate to an Oracle database. Examples of migration components are tables and stored procedures.
migration entity
An instance of a migration component. The table EMP is a migration entity belonging to the table MIGRATION COMPONENT.
Migration Workbench
A graphical tool that helps you to migrate a third-party database to a destination database.
Migration Workbench repository
Migration Workbench Software Development Kit (MWSDK)
A representation of a public Application Programming Interface (API) that enables third-party developers to extend the features of Migration Workbench to other platforms.
Migration wizard
An intuitive wizard that helps you migrate the source database to a destination database.
offline capture
The process of using Migration Workbench capture scripts to connect to the source database and create a set of files that describe the database structure. You can then use Migration Workbench to populate the Source Model and optionally generate the Oracle Model from these files.
offline data transfer
The process of generating and using scripts to copy data from the source database to the destination database. During this process you must:
Use Migration Workbench to generate data unload scripts for the source database and corresponding data load scripts for the destination database
Run the data unload scripts to create text files of data from the source database
Run the data load scripts using SQL*Loader to populate the destination database with data from these text files
offline schema creation
The process of generating a set of SQL scripts using Migration Workbench and running these scripts while connected to the destination database using SQL*Plus.
online capture
The process of using Migration Workbench to connect to the source database, extract the database structure, and populate the Source Model.
online data transfer
The process of using Migration Workbench to copy data from the source database to the destination database. During the online data transfer process, Migration Workbench must connect to both the source and destination databases.
online schema creation
The process of using Migration Workbench to connect to the destination database and create the migrated database objects.
Oracle Database
The software used to create and maintain the database system, as well as the actual data stored in the database.
ORACLE_HOME
An alternate name for the top directory in the Oracle directory hierarchy on some directory-based operating systems. It corresponds to the environment where Oracle products run. This environment includes the location of installed product files, the PATH variable pointing to the binary files of the products, registry entries, net service names, and program groups.
Oracle Model
A representation of the structure of the destination database. The Oracle Model is stored in the Workbench repository. Migration Workbench populates the Oracle Model using the information from the Source Model.
Oracle Open Database Connectivity (ODBC) driver
The Oracle ODBC driver provides a standard interface that allows an application to access many different data sources. The source code of the application does not have to be recompiled for each data source. A database driver links the application to a specific data source. A database driver is a dynamic link library that an application can invoke on demand to gain access to a particular data source. Therefore, the application can access any data source for which a data driver exists.
primary key
The column or set of columns included in the definition of a table's PRIMARY KEY constraint. The value of a primary key uniquely identify the rows in a table. Only one primary key can be defined for each table.
Progress window
The part of Migration Workbench user interface that contains informational, error, or warning messages describing the progress of the migration process.
reserved word
In SQL, a set of words reserved for use in SQL statements; you cannot use a reserved word as the name of a schema object.
schema
Named collection of objects, created and stored in a database, that are associated with a specific user, such as tables, views, synonyms, and indexes.
source database
The third-party database, such as Microsoft Access, that you want to migrate to an Oracle database.
Source Model
A representation of the structure of the source database that is stored in the Workbench repository.
SQL*Loader
An Oracle tool used to load data from operating system files into destination database tables.
Structured Query Language (SQL)
The internationally accepted standard for defining and manipulating relational databases.
tablespace
A database is divided into one or more logical storage units called tablespaces. Tablespaces are grouped into logical structures of storage called segments, which are further divided into extents.
third-party database
A database other than Oracle that Migration Workbench can assist in migrating to an Oracle database.
tnsnames.ora
A file that contains connect descriptors mapped to net service names. You can maintain this file centrally or locally for use by all or individual clients.
trigger
Stored database procedure automatically invoked whenever a table or view is modified, such as by INSERT, UPDATE, or DELETE operations.
Workbench core
A component of Migration Workbench that provides a framework that works with different Workbench plug-ins to migrate third-party databases.
Workbench plug-in (plug-in)
A component of Migration Workbench that works with the Workbench core to migrate the source database to the destination database. Individual plug-ins are available to migrate different third-party databases to an Oracle database.
