The following sections explain details about the settings that you specify in the Create New Mapping Definition dialog box.
To link feature classes
- Click the Feature Classes tab.
Feature classes that have not yet been linked, are marked with a special icon
. - Select the source feature class, and the final feature class.
- Click Link Feature Classes.
The linked feature classes are added to the Linked Feature Classes list. Icons indicate that some attributes need to be mapped.
- Click the Feature Attributes tab.
- Select the linked feature classes row, and under Link Feature Attributes, link the attributes.
When you specify a mapping, you can use the table name / attribute name NULL to explicitly not migrate the item. Then the system does not mark the item as Not Linked. For example, when you share your configuration with another user, the NULL items would not be marked as Not Linked. However, any additional feature classes and attributes of the other industry model are marked as Not Linked, and missing mapping definitions can be added.
Feature Attributes
When you link feature attributes, the system checks the attribute type. For example, you cannot link an attribute of type Number(10) to an attribute of type Number(1), or you cannot link an attribute of type SDO_GEOMETRY to an attribute of type Varchar2.
If the final attribute is of type NOT NULL, a DECODE command inserts a default value.
If both the source attribute name, and the final attribute name is ORIENTATION, and if the source attribute is of type Number(20,8), and the final attribute is of different type, the system changes the final attribute type to Number(20,8).
FID attribute
When you link the source attribute FID to the final attribute FID, the application creates a system attribute T2T_FID. In the list, T2T_FID is displayed in parentheses, next to the FID attribute. T2T_FID stores the source FID. The final FID will be newly generated during the data transfer, in order to generate consistent FIDs. T2T_FID (the source FID) is used to restore any relations between the features.
Feature relations
Optionally, relations to other features are restored. For this purpose, the source FID is stored in system attribute T2T_<attribute name>, and an update SQL script (Post SQL) is created. The Post SQL will be run after the migration. In the Linked Feature Attributes list, under Properties, the entry PostScript indicates that a Post SQL has been created.
To edit the Post SQL, click the Edit icon. See also Oracle Data Import: SQL Statements and Placeholder.
Domain table relations
If both the source attribute, and the final attribute has a relation to a domain table, you have to map the domain tables. That means, you assign the values of the source domain table to the values of the final domain table.
Example: A source domain table specifies colors, such as 1=Red, 2=Blue, 3 = Black. You map the source domain table to a final domain table, where the following values are stored: 53=Red, 54=blue, 55=Black. Then you map the domain values, so the migration changes the values: 1 to 53, 2 to 54, 3 to 55.
To copy a value of the source domain table to the final domain table, select the value, and click the Copy icon. For example, to add missing values. This creates a KEY value, starting at 10001 for numeric keys, and copies the SHORT_VALUE.