"ODI-14070: Import Failed. The Parent Object Was Not Found In The Repository" when Importing Knowledge Modules in "Synonym INSERT" Mode
(Doc ID 2357394.1)
Last updated on FEBRUARY 03, 2022
Applies to:
Oracle Data Integrator - Version 12.2.1.2.6 to 12.2.1.3.0 [Release 12c]Information in this document applies to any platform.
Symptoms
In Oracle Data Integrator (ODI) 12c, importing a Knowledge Module (KM) in "Synonym Mode INSERT" mode fails with the following error:
com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ODI-14070: Import failed. The parent object was not found in the repository.
at com.sunopsis.dwg.DwgDuplicationTools.synonymImport(DwgDuplicationTools.java:3928)
at com.sunopsis.dwg.DwgObject.importFromObjectLst(DwgObject.java:9950)
at com.sunopsis.dwg.DwgObject.internalImportObjectList(DwgObject.java:8660)
at com.sunopsis.dwg.DwgObject.doImport(DwgObject.java:9140)
at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:7575)
at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:7506)
at com.sunopsis.dwg.DwgObject.importFromXml(DwgObject.java:7489)
at com.sunopsis.graphical.dialog.SnpsDialogImportXml.importFiles(SnpsDialogImportXml.java:890)
at com.sunopsis.graphical.dialog.SnpsDialogImportXml.access$100(SnpsDialogImportXml.java:105)
at com.sunopsis.graphical.dialog.SnpsDialogImportXml$1$2.doAction(SnpsDialogImportXml.java:610)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)
at oracle.odi.core.persistence.dwgobject.TransactionalDwgObjectTemplate.execute(TransactionalDwgObjectTemplate.java:64)
at com.sunopsis.graphical.dialog.SnpsDialogImportXml$1.doLongOperation(SnpsDialogImportXml.java:587)
at oracle.cef.ui.Framework$5.doInBackground(Framework.java:726)
at oracle.cef.ui.Framework$5.doInBackground(Framework.java:718)
at javax.swing.SwingWorker$1.call(SwingWorker.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at javax.swing.SwingWorker.run(SwingWorker.java:334)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.sunopsis.core.SnpsInexistantObjectException: SnpProject.getObjectByIdent : SnpProject does not exist
at com.sunopsis.dwg.dbobj.generated.GeneratedSnpProject.getObjectByIdent(GeneratedSnpProject.java:505)
at com.sunopsis.dwg.dbobj.SnpTrt.checkParentExists(SnpTrt.java:2436)
at com.sunopsis.dwg.DwgDuplicationTools.synonymImport(DwgDuplicationTools.java:3924)
... 20 more
When selecting "Synonym Mode INSERT_UPDATE", the import is successful, but:
- It is always imported as a "global object", regardless of the project folder from where the import was attempted
- The resulting import report incorrectly shows that the imported KM is associated with a project folder even when attempting to import as global object.
The issue can be reproduced at will with the following steps:
- Login to ODI Studio
- In Designer, go to a project and select "Knowledge Modules"
- Right-click and select "Import Knowledge Modules"
- Select "Synonym Mode INSERT" or "Synonym Mode INSERT_UPDATE"
In ODI 11g, only "Duplication" mode is available, and nothing else can be selected.
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |