Oracle Data Integrator 12c is out and, as part of the Oracle Data Integration suite, it delivers high-performance data movement and transformation among enterprise platforms with its open and integrated E-LT architecture
The latest ODI 12c version works in conjunction with Oracle Golden Gate, the Oracle’s database replication tool, in order to provide near real-time data replication to the analytical applications.
Cintra Software and Services, an Oracle platinum partner, with several Oracle Data Integrator deployments and years of experience in Data Warehouse projects, has created a set of ODI 12C best practices.
MANAGING WORK REPOSITORIES
- A master repository can have many work repositories. You can also have multiple master repositories, each of them having his own set of work repositories. Each repository has an ID set at creation time.
- A repository is not a document. It is the “source of truth”, the central reference that cross-references all the artifacts it contains for easing the maintenance.
- Two repositories with the same ID possibly contain objects with the same internal ID, which mean the same object for ODI. Transferring objects between these repositories is similar to copying files with same names across different directories, and may lead to object replacement.
REPOSITORIES MAINTANANCE
- ODI stores all its information into a metadata repository, stored into a relational database. Once you know this, it is very tempting to start hacking your way through the repository tables to “go faster”.
- The repository does not implement all the logic that exists in the graphical interface, and does not implement all the business logic that exists in the Java code. Performing request to build for example dashboards or reports on top of the repository is acceptable, but writing or altering repository information is dangerous, and should be left to troubleshooting or support operations, under control of the Oracle Support.
Other related posts: