It's a very common practice to keep the ODI Target and Work Schema to reside in one database. All the temporary objects created by the Knowledge modules are thus created inside the schema as the Target data store. Is this a good approach ?
It is Oracle recommended to keep the temporary objects created by the Knowledge Modules in a separate schema rather than keeping them along with the target schema. A dedicated work schema would help you organize and distinguish your temporary objects from actual target tables. Bringing the temporary objects under one schema means that you can easily drop the objects from the work schema.
Points to remember
- Always better to define Work Schema separately in the Topology rather than for each Interface.
 |
| Work Schema definition in Topology. |
- Always define the work schema separately from target schema for ease of organizing and managing your work schema.
You can see it here in this Oracle Data Integrator Best Practices - White Paper that clearly says to define a dedicated schema for Work/Staging.
No comments:
Post a Comment