ODI 12c Caching Issue on Logical Agent Relative to Newly Created Physical Agent
(Doc ID 2554049.1)
Last updated on JUNE 12, 2023
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 and laterOracle Data Integrator on Marketplace - Version 12.2.1.4.200123 and later
Information in this document applies to any platform.
Symptoms
When a new Physical Agent is created in the Oracle Data Integrator (ODI) 12c Studio > Topology, it's visibility is partial only:
- In the "Physical Architecture" > Agents view
--> one can see the Physical Agent created.
- In the "Contexts" view > edit a Context, and from the "Agents" tab, try to map the newly created Physical Agent to any of Logical Agents
--> the Physical Agent created does show in the list, and can be used.
- In the "Logical Architecture" > Agents view > edit a Logical Agent, and from the "Definition" tab, try to map the newly created Physical Agent to any of Context
--> the Physical Agent created does n o t show in the list.
EXPECTED BEHAVIOR:
The newly created Physical Agent should be accessible from the "Logical Architecture" > Agents view, and any other view in the Topology.-----------------------
STEPS TO REPLICATE THE BEHAVIOR:
- In ODI 12c > Topology > Physical Architecture, create a Physical Agent called "My Agent". Apply the changes, and refresh the Topology view.
- In ODI 12c > Topology > Contexts, edit any of the existing Contexts, and go to the "Agents" tab. Try to assign the newly created Physical Agent to any of the Logical Agents existing.
Observe "My Agent" is showing in the "Physical Agents" list, which is correct.
- In ODI 12c > Topology > Logical Agents, edit any of the existing Agents, and go to the "Definition" tab. Try to assign the newly created Physical Agent to any of the Contexts existing.
Observe "My Agent" is n o t showing in the "Physical Agents" list, which is incorrect / unexpected.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |