DB.XML Import

This page is accessed via Business Process Automation > Data Import/Export > DB.XML Import.

Use this page to import DB.XML.

Note: There is also a command line utility available to import DB.XML files. See the Data Management Guide on the Oracle Help Center for details.

Note: If you import a Workbench layout, you must regenerate the layout before using it.

Importing DB.XML

1. Select the Schema to which your data belongs. A database contains a number of tables, indexes, constraints, etc.. Collectively, the definition of these items is known as the database's schema.
2. Enter an Input XML File by clicking Browse. You may select an XML file or CSV.
3. Select a Transaction Code. The default transaction code is I (insert). You may change the transaction code from I to II (insert ignore), IU (insert update), D (delete), or RC (replace children). See DB.XML Transaction Codes in the Data Management Guide for the meaning of the different transaction codes.
4. Enter Managed Tables only if the transaction code is "RC" and the dbObjectName’ attribute is unspecified in the input XML File. (The "dbObjectName" is unspecified in your db.xml file if your file was generated using a sqlQuery). To generate a db.xml file with dbObjectName specified, generate the db.xml file by selecting a dbObjectName. See the Exporting DB.XML section in the Data Management Guide for a procedure on how to do this. Only managed tables will have rows deleted when the transaction code is "RC" (replace children). Separate the table names with commas.
5. When the Refresh Cache checkbox is selected, any objected created or updated by a Project Import will refresh any associated cache. For example, creating a new agent will result in the agent subscribing to its events and so will be triggered when expected.
6. If the Lifetime Events checkbox is select, then any object created, updated, or removed by a Project Import will trigger the "xxx - CREATED", "xxx - MODIFIED" and "xxx - REMOVED" events (where type "xxx" already supports lifetime events) and process any subscribing agent workflow. These events will be raised with the new "MIGRATION" data source and so to trigger agents this data source has to be selected as one of the options (e.g. in addition to INTEGRATION, USER, INTERNAL).
7. The Commit Scope drop-down list allows you to treat a group of objects as one unit of work. When you select "PK" the different objects are handled separately. When you select "SET", the distinct objects are treated as one unit of work. For example, a migration might contain a new set of agents which are all required for the new business logic to work. You want them all to succeed or all to fail so this would be when you would mark the group of agents as committed as a "SET". If you committed each individual agent, you might save one for the Shipment type but not the other for the Order type and so the complete workflow wouldn't be in place.
8. Click Run.