My Oracle Support Banner

"ODI-10245: Cannot import SNP_KMTEMPLATEJOIN null" is Received when Applying a Patch Deployment Archive in ODI 12C (Doc ID 2424875.1)

Last updated on NOVEMBER 19, 2021

Applies to:

Oracle Data Integrator - Version to [Release 12c]
Information in this document applies to any platform.


In a new Oracle Data Integrator (ODI) production environment (master, work and execution repository newly created), a patch deployment archive from the development environment fails with the following error:

FAILED: ODI-11002: Error occurred while importing Objects ODI-11002: Error occurred while importing Objects ODI-10245: Cannot import SNP_KMTEMPLATEJOIN null (with global id: <GUID> and internal id: <ID>) belonging to <NAME>LKM (with global id: <GUID> and internal id: <ID>) because its referenced object is not found in the target repository.

The issue has been reproduced by support with the following steps but it may be possible to encounter the issue using different steps:

  1. From the existing work repository in the development environment, create a deployment archive from the full repository: Team/Deployment Archives/Create from repository/Full repository (all physical topology objects included).
  2. Create new schemas for master/work/execution in the production environment's DB as sys as sysdba
  3. Create master/work repository with ODI Studio (New gallery)
  4. Initiate the master/work repositories from the deployment export.
  5. When trying to import any Patch deployment archive (Team -> Deployment Archives -> Patch Deployment Repository -> with or without including any physical objects) into the new environment, the error appears.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.