Odi 11g again disappointed me ......

There is no major change relative to 10 Gb. Unlike owb, an interface has many components available. It can only be simple from source to target. Complex conversions require nesting of interfaces. For certain database features, you need to write km. The package process control function is not strong. For example, loop operations can only be completed in procedure. Procedure and km are basically coding.

Therefore, the role of ODI is limited to the integration of different types of databases. The complicated conversion is still completed by using owb after being loaded to the Oracle database. However, currently, ODI does not seem to provide tools for calling owb directly, and ELT is not very reliable in processing large data volumes. The packages generated by owb have redundant operations, it is not as efficient as self-written SQL statements.