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.
PROCEDURES AND PACKAGES USAGE
- Maintaining the procedures/packages coding needs requires manual effort that sometimes is difficult to be validated and deployed across multiple source/targets.
- Procedures do not maintain cross references to other ODI artifacts such as data stores, models, etc, making their maintenance very complex compared to interfaces.
ERRORS HANDLING
- Applying an organized error handling helps to track the specific exception happens during the execution.
- Considering different error cases when designing packages.
CONTEXT INDEPENDENT
- It is used to create and manage connections to data sources and agents and is usually restricted so that only administrators have access.
Operator
- Avoid adding qualified object names (E.g.: schema.object)in artifacts like (procedure, variables, interfaces, etc..) – this can be set dynamically by the execution context.
Other related posts: