But that’s not the only reason, it also stems from the best practice of separating your environments in entirety development, test, production, so each can be maintained, upgraded, and patch separately.
The RCU doesn’t provide an option for separating the repositories into two different schemas, therefore the standard is to use one single schema.
The latter practice was more common in the past, before the Repository Creation Utility (RCU) was really the main mechanism for creating the repositories. The Master and Work repositories can reside in the same database schema or as their own schemas in the same database instance. More on all of these objects in a later post. The Execution Work repository only stores the execution objects, Scenarios and Load Plans, and there is no development capability. In a Development Work repository you’ll find all of the design objects (mappings, packages, procedures, etc) and datastore metadata. Work repositories can be of 2 different types: development or execution. Each Master repository can be linked to one or more Work repositories. The Master repository contains information about security (users, profiles, etc), topology (data connections, contexts, physical/logical schemas), and ODI versioning. This metadata is stored away in two different repositories: the Master repository and the Work repository. Componentsīefore diving into the architecture, we need to understand the different components that are part of the Oracle Data Integrator installation. In this article, I’ll walk through different components of Oracle Data Integrator and some of the architecture choices you’ll need to make in order to get started with ODI 12c. In my ( " target="_blank), I shared the history of ODI and a bit about what sets it apart from other ETL tools on the market. I’m writing a Getting Started series to help folks get interested in the product and maybe even teach a few old dogs (including myself) some new tricks. I’ve decided that it’s time for a refresher on Oracle Data Integrator 12c.