Tuesday, October 26, 2021

ODI 12c - CKM with Flow control and Static control and Recycle errors

Here, we will show the setups required for Flow control , Static control and Recycle errors.

Brief steps:

1. Create a Primary key constraint on target data store.

2. Create a map and Select flow or static or recycle errors option

Flow diagram for LKM, IKM,CKM:

Implementation steps:

Step1: open the target data store constraints and control tab to checj if there is any duplicate rows.

Step2: Create  a new map and prividd LKM, IKM and Flow control as False and Statc control as true and run. You will see the the duplicate or null errors in E$_EMP table.

Step3: Now make Flow control also True

Step4: Now make Recycle errors as True

Monday, October 25, 2021

ODI 12C - CDC implementation using JKM

Here, we will see how to capture changed data(New inserted data and update data) using JKM and send the data to Target.

Implementation steps:

Step1: import JKM 

Step2: model -- Journalizing -- select Journalizing mode . Here choosing Simple and select KM.

Step3: Open Datastore and constraints -- create primary key as empno.

Step4: EMP datastore -- CDC -- Subscriber -- subscribe. Add one subscriber.

Step5: Add to CDC

Step6: Start Journal ans select subscriber.

Step7: you can check that Subscribers will be created and J$ and JV$ tables.

add emp table in the journalized table.

do the mapping Nd select subscriber in the logical Journalizing section

Add LKM and IKM and flow control as false.

select source unit and check the option Journalized Data only.

Friday, October 22, 2021

ODI 12c - Manually run a load plan if schedule not worked automatically

If schedule does not work automatically then we can run the load plan manually.


Operator tab →Load plans and scenarios →select your load plan→ right click on and run and select your agent and ok.

ODI 12c - Procedure and use options

Procedure in ODI:

  • A procedure in Oracle Data Integrator (ODI) consists of a series of commands executed in sequence. Commands contain code that can be executed by database engines, the operating system where the Agent is running, or directly by ODI. 
  • You can also define options in the procedure to control its behavior at run time. A very useful property of procedures is that they are reusable and can be inserted into packages. Thus, just as procedures comprise commands, a package can contain several procedures as steps.
  • You use procedures in a package or a scenario, or you can run them directly from the Designer Navigator.

Implementation Steps:

Step1: Designer -- Projects -- your project -- procedure -- new procedure

Step2: Define Procedure name, and source and target technology if needed.

Step3: Tasks -- Add new task

Step4: Created couple of tasks. For 1st task provide name

Step5: Target command -- select technolgy, context, logical schema, and command.

Step6: Need to provide source command if you want to select some fields.

Step7: Mention the same for remaining 2 commands

Step8: For this 3rd command, used source command to select the data from source emp table.

Step9: Assign the selected source fields in the target insert values using :fieldname

Step10: Save and run it.

Note: Select the Ignore Errors check box so that the procedure runs even if this command fails.

Step11: To use options, go to Options and add option

Step12: Added 3 options

Step13: Go to Tasks and option section and select the options to be used for a particular task.

Featured Post

11g to 12c OSB projects migration points

1. Export 11g OSB code and import in 12c Jdeveloper. Steps to import OSB project in Jdeveloper:   File⇾Import⇾Service Bus Resources⇾ Se...