Mapping Knowledge Modules FAQS

1. What are Knowledge Modules (KMs) in ODI 12c?
• Knowledge Modules (KMs) are pre-built templates or scripts that define how data will be transferred between data servers, how transformations are applied, and how data is loaded into target systems. They help streamline the process of data integration by specifying the tasks to be performed.
2. What types of Knowledge Modules are there?
• There are four main types of Knowledge Modules:
• IKMs (Integration Knowledge Modules): Responsible for defining how data is transformed and loaded into a target system.
• LKMs (Loading Knowledge Modules): Used to specify how data is transferred between data servers.
• CKMs (Check Knowledge Modules): Used for error checking and validation of data during the flow or for static control to check table constraints.
• EKMs (Extract Knowledge Modules): Responsible for extracting data from source systems (though not detailed here, EKMs are used for extraction tasks).
3. How do I import Knowledge Modules into my project?
• You can import Knowledge Modules into your project by selecting them from the Knowledge Modules tab or making them available as global KMs. Once imported, they can be selected for use in the data flow.
4. What is the purpose of IKMs (Integration Knowledge Modules)?
• IKMs define the transformation logic and data loading mechanisms. They are used to specify how data should be processed (transformed) and loaded into the target system.
5. How do LKMs (Loading Knowledge Modules) work?
• LKMs are used to define how data is transferred from one data server to another. They specify the data transfer mechanisms (e.g., using JDBC, database links, etc.) for efficient movement of data between systems.
6. What are CKMs (Check Knowledge Modules) used for?
• CKMs are used for data validation and error-checking during data integration processes. They can be used for:
• Flow control: To check for errors during the loading process.
• Static control: To validate data in a table or model at any point in the process to ensure data integrity and constraints.
7. When do I use CKMs (Check Knowledge Modules)?
• You use CKMs when you need to verify the integrity of the data, either during the data flow (e.g., while loading data into a target) or for static control (e.g., checking constraints on tables or models at any time).
8. Can I select different Knowledge Modules for different tasks in my mapping?
• Yes, you can select different Knowledge Modules for different steps of your mapping based on the task at hand. For example, you might use a LKM for transferring data between two servers, an IKM for transforming and loading data into a target, and a CKM for checking data integrity.
9. What are some examples of transfer strategies I can use with Knowledge Modules?
• You can select different strategies for transferring data based on the database systems involved:
• JDBC for transferring data between different types of databases.
• Oracle Database Link for transferring data between two Oracle databases.
10. Can I customize the Knowledge Modules in ODI 12c?
• Yes, you can customize the standard Knowledge Modules in ODI to suit your specific requirements by modifying the underlying scripts or logic.
11. Are Knowledge Modules reusable across different projects?
• Yes, Knowledge Modules are reusable. You can use the same KM across multiple projects as long as it fits the required transformation or data transfer task.
12. How do Knowledge Modules improve data integration in ODI 12c?
• Knowledge Modules simplify the design and execution of data integration tasks by providing pre-built, customizable solutions for transforming, transferring, and validating data. They enhance the efficiency and maintainability of data integration processes.