A Table Map identifies and matches two sets of tables.
Use a Table Map to:
- Direct the placement of data in a Convert, Create,
Insert, Load, or Restore Process.
- Exclude one or more tables from a Compare, Convert,
Create, Insert, Load, or Restore Process.
Depending on the process for which you are using
a Table Map, the two sets of tables are referred to as Source Tables
and Destination Tables, or Source 1 Tables and Source 2 Tables:
- Source Tables are extracted or archived tables
that contain data to be used in a Create, Convert, Insert, Load, or
Restore Process.
- Destination Tables are the tables into which
data is created, converted, inserted, loaded, or restored.
- Source 1 Tables and Source 2 Tables contain
data to be used in a Compare Process.
Note: Matched tables can have different Creator IDs or names.
Table Maps are stored in the Optim™ Directory or embedded in a process request.
As
an option, you can use a Column Map for any pair of tables in a Table
Map. Column Maps identify and match columns in a pair of tables. A
Column Map must be used when column names or attributes are dissimilar
or data transformations are needed. For complete details on defining
and editing Column Maps, see Column Maps.
Naming Conventions
The
fully qualified name of a Table Map is in the form: identifier.name.
- identifier
- Identifier assigned to the Table Map (1 to 8 characters).
- name
- Name assigned to the Table Map (1 to 12 characters).
It is helpful to use a logical set
of naming conventions to identify the use for each and to organize
definitions for easy access.
Section Contents
This
section explains how to create and maintain Table Maps, including
how to:
- Specify tables to correlate in a Table Map.
- Specify Column Maps in a Table Map.
- Merge Table Maps.
- Edit Archive Actions, when a Table Map is used in
a Restore Request.