Specifying Target Order FAQS

1. What is the default behavior of target loading in ODI when multiple targets are used in a mapping?

• By default, the targets are loaded in an arbitrary order unless a specific order is defined using the Target Load Order property.

2. How can I define the target load order in ODI?

• You can define the target load order in the Target Load Order field in the Property Inspector by selecting the mapping and entering the desired order. You can also use the gear icon to open the Target Load Order Dialog for more options.

3. What happens if I don't define a target load order?

• If you do not define a target load order, ODI will compute a default order based on primary key/foreign key relationships between the target datastores. The targets will be loaded in this computed order.

4. Can I modify the default target load order?

• Yes, you can modify the default load order. However, if the modification conflicts with primary key/foreign key relationships, ODI will display a warning when you validate the mapping.

5. How does the target load order affect reusable mappings?

• The Target Load Order property also applies to reusable mappings. If a reusable mapping contains a source or target datastore, you can include it in the Target Load Order property of the parent mapping.

6. Why is the target load order important when foreign key relationships exist?

• The target load order is critical when foreign key relationships exist between targets. For example, if one target depends on another (e.g., EMP depends on DEPT), you must load the dependent target (DEPT) first to ensure data integrity.

7. How can I rearrange the target load order in ODI?

• To rearrange the target load order, you can open the Target Load Order Dialog by clicking the gear icon in the Property Inspector. From there, you can move targets to the Ordered Targets field and adjust their processing order using the available icons.

8. What should I do if I see a warning after modifying the target load order?

• If you modify the target load order in a way that conflicts with primary key/foreign key relationships, ODI will display a warning during validation. You can choose to ignore the warning if necessary, but it's important to ensure the order still respects the data relationships.

9. Can I use target load order when working with multiple targets in a reusable mapping?

• Yes, you can specify the target load order for reusable mappings, ensuring that the parent mapping properly coordinates the loading order of multiple targets within the reusable mapping.

10. How does the target load order dialog help in managing multiple targets?

• The Target Load Order Dialog provides a convenient interface to manage the order in which targets are loaded. It lists all available datastores and reusable mappings, and allows you to move them into the Ordered Targets field, giving you full control over the sequence of processing.