Populating the Driver Table

The driver table must include a single column that contains the object ID of objects you want to include in the export.

The driver table must include a single column that contains the object ID of objects you want to include in the export. You do not need to list every object. Within the limits described in Objects Included and Objects Excluded, the utility automatically includes additional objects as follows:

• Domains. If you enter the object ID of a Domain in the driver table, the utility exports all definitions in the Domain, all Application Areas in the Domain, and all objects in the Application Areas, including object definitions, Work Areas, object instances in the Work Areas, and the object definitions and container objects required for them to exist; see "Object Definitions and Instances, and their Containers" in the Oracle Life Sciences Data Hub Application Developer's Guide for further information.
• Application Areas. If you enter the object ID of an Application Area in the driver table, the utility exports the Application Area and all objects contained in it, including object definitions, Work Areas ,and object instances in the Work Areas, and the object definitions and container objects required for them to exist.
• Work Areas. If you enter the object ID of a Work Area in the driver table, the utility exports all object instances in the Work Area and the object definitions and container objects required for them to exist.
• Object instances. If you enter the object ID of an object instance in the driver table, the utility exports all objects required for the instance object to exist, including both primary and secondary definitions that are instantiated by the instances, any source and target Table instances, and all container objects above them in the object hierarchy. See the Oracle Life Sciences Data Hub Application Developer's Guide Appendix on "Object Ownership" for further information.

  Note:

  Some objects may be listed explicitly in the driver table and also included in the export because of their relation to another object. The utility ignores such duplication and exports each object only once.