How To Avoid Redoing The OIC Mapper Of ADW Connection Even After Metadata/connection Refresh?
(Doc ID 2887396.1)
Last updated on AUGUST 02, 2022
Applies to:
Oracle Integration-OIC - Version 18.2.5 and laterInformation in this document applies to any platform.
Goal
After loading data into a target database using OIC, and completing all the field mappings, during testing, it was found that one of the fields in the target database had to change from number to string.
This change was done in the target database, however, in OIC mapper, the datatype still remained as number.
When the options to 'Refresh the target connection's metadata' and 'Regenerate all endpoints' in the integration were tried, the following message was received from OIC:
In the end, the entire mapper was deleted, and the mapping was re-done all over again.
Why did OIC give the message - This integration does not support regenerating all endpoints.
How can such changes be achieved in the future, without re-doing the entire mapper; Changes like DataType updates, max Field Length updates etc.?
Solution
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
Goal |
Solution |