The Code Implemented in ODI 12c Knowledge Module Steps Gets Silently Corrupted
(Doc ID 2585896.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
The code implemented in Oracle Data Integrator (ODI) 12c Knowledge Module (KM) steps gets corrupted - the changes are lost or messed up when closing the KM editor.
For example, in the screen copy below, observe the code originally implemented from line #23 to #28 of a randomly chosen genuine ODI knowledge module:
<%=odiRef.getGrpBy(i)%>
<%=odiRef.getHaving(i)%>
<%}%>
"""
<%} else {%>
Edit the code, and add the following comment at line #27:
///ceci est un commentaire pour tester la persistance du code écrit
Apply the changes, close the Editor window, and re-open the Editor window. Note that the KM changes do not need to be saved. It also is not required to close the knowledge module:
<%=odiRef.getGrpBy(i)%>
<%=odiRef.getH///ceci est un commentaire pour tester la persistance du code écrit aving(i)%>
<%}%>
"""
<%} else {%>
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! |
In this Document
Symptoms |
Cause |
Solution |
References |