Integration Does Not Activate After Changes DB Stored Procedure
(Doc ID 2535639.1)
Last updated on JANUARY 18, 2020
Applies to:Integration Cloud Service - Version N/A and later
Information in this document applies to any platform.
Changes were made to database objects for an interface,
After updating tables, object definitions, and pl/sql packages, and clicking through all invoke/trigger nodes in integration, no errors were shown on integration and integration saves with no issues.
When attempting to activate integration several errors are seen like this one:
oracle.apps.mapper.utils.MapperException: An error occurred during the addition of a secondary source in the ''req_a6576c50300d421aa5c812e270eabed9.xsl''map. The Mapper Exception is: : A stylesheet parameter already exists with the name ''GetXXXX'' in the ''req_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xsl'' map. In order to add a new stylesheet parameter the name must be unique.
What could the issue be?
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