How to fix ODI Mapping Issues in OCI with LKM Oracle Pull
Abotts Logo Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Upworks Logo Abotts successfully decouples and migrates Upwork EBS custom schema to oracle cloud.
Abotts Logo ABOTTS partners with County in Los Angeles to upgrade their court infrastructure into new technologies.
Upworks Logo Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
QuinStreet Logo QuinStreet partners with Abotts to archive and manage their IT systems on Oracle cloud (OCI).
Gnorth Logo Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.
Abotts Logo Abotts Partners with singapore based tech giant to help migrate their public sector customer from Sybase to SQL server.
Upworks Logo Abotts successfully decouples and migrates Upwork EBS custom schema to oracle cloud.
Abotts Logo ABOTTS partners with County in Los Angeles to upgrade their court infrastructure into new technologies.
Upworks Logo Upworks Inc partners with ABOTTS to build their Oracle Cloud Infrastructure (OCI) and migrate their custom applications to OCI.
QuinStreet Logo QuinStreet partners with Abotts to archive and manage their IT systems on Oracle cloud (OCI).
Gnorth Logo Abotts Inc Partners with Gnorth consulting to deploy exadata and ODA for a large public sector customer.

How to Fix ODI Mapping Issues in OCI with LKM Oracle Pull

Issues while running ODI mapping in OCI. (ODI Marketplace)

 

  • Using LKM Oracle to Oracle Pull (DB Link)

  • Pulling data from Oracle DB to Oracle Autonomous Database

  • Using ADB as staging


In the screenshot below, we are running a mapping to push  data from Onprem to Oracle Autonomous DB.  However, an error occurred when running the mapping.
Error Screenshot


Upon investigating the issue, we discovered that the Create_DB_Link option in the Loading Knowledge Modules of the mapping was set to True, which caused the problem. This setting led to the automatic creation of a database link for the source database, resulting in the error.To resolve this issue we Manually Create a DB link using below Document.
https://docs.google.com/document/d/1erV5a6QjXzZDxwE22usQ6zzXONpVOPoqC-IReHyW_TI/edit?usp=drive_link

Once the database link is created go to the loading Knowledge Module Properties of the mapping, as shown in the image below. Set the Create_DB_Link option to False, as depicted in the screenshot


Then, specified,  the newly created database link name in the Source_Access_DB_Link option, as highlighted in the screenshot below.

We added the KM Oracle Insert as highlighted in the screenshot below. Causing the Issue to resolve and smooth running of the mapping.