Unable to See Some Datastores in a New ODI Mapping Dataset after Upgrade or Import
(Doc ID 2738940.1)
Last updated on OCTOBER 04, 2022
Applies to:Oracle Data Integrator - Version 220.127.116.11.200413 and later
Information in this document applies to any platform.
Using Oracle Data Integrator (ODI) Studio version 18.104.22.168, when adding a datastore in a mapping dataset, it is not visible unless the mapping is reopened.
The properties of the dataset show the correct number of datastores.
This issue only occurs consistently for some of the datastores.
After reverse-engineering of the same datastores, the datastores are seen in the dataset, but they appear twice and connected via join.
The following error can be seen in the Studio log:
1 - Create a new mapping with empty dataset
2 - Drag model which has no issue
=> the model is visible
3 - Drag model which has an issue
=> the model is not visible, but it is listed under "Default Properties" -> "Datastores"
4 - Save and exit the mapping
5 - Open the mapping again
=> the model is now visible
6 - Reverse-engineer the model
7 - Retest
=> The datastore shows in the mapping.
=> However, the display shows the datastore twice connected via join for both datastores that are not showing for the imported model.
The datastore with this issue have foreign key constraints.
ODI was upgraded recently from version 12.1.3.
Note that smart export/import also reproduces the issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document