Data migration flow

For data conversions, an OUAF application typically has two table-owning schemas, CISADM and STGADM, as shown in this diagram.

The CISADM schema owns all database objects, including the base tables, of an OUAF application. The staging schema, STGADM, designed specifically for data conversion, serves as a structural counterpart to the CISADM schema. Additionally, the STGADM schema defines the configuration and runtime tables for the DIH and uses the UA_. prefix.

Upon initialization, the CISADM schema contains all necessary empty tables, views, and other Oracle objects essential for the application’s functionality. Most conversion processes occur in the staging schema. The DIH transfers source data to its corresponding targets within the STGADM schema and primarily interacts with the CISADM schema during the final stages of the conversion process, specifically when moving newly converted application objects from staging to production.

The base conversion tool requires that all source data be accessible via SQL SELECT statements. This source data can be stored in the same schema, in other schemas, or even across different databases. If needed, it can be defined as synonyms or views in the staging schema. However, if a table resides in another database, a database link would be necessary to access it from STGADM, which could potentially result in inefficiencies in the conversion process; therefore, this is not recommended. Ideally, the source data should be located on the same physical database as the staging schema.