My Oracle Support Banner

"ODI-26210: The repository contains map component and KM definitions that are older than the ones supported by the current client version" Warning after Upgrade to ODI 12.2.1.3 Bundle Patch and MySQL Repositories (Doc ID 2626773.1)

Last updated on JANUARY 13, 2020

Applies to:

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

Symptoms

In an environment where MySQL is used for hosting the Oracle Data Integrator (ODI) master / work repositories, after having upgraded from ODI 12.2.1.3.0 to ODI 12.2.1.3.190415, 12.2.1.3.190515 or 12.2.1.3.190708, the ODI Studio Login continues to show the following warning message at each login:

ODI-26210: The repository contains map component and KM definitions that are older than the ones supported by the current client version.
Clicking Yes will continue the login and the map component definitions will be updated. Clicking No will disconnect from the repository without updating. Do you want to continue?

The following errors are noticed in the Studio log upon login. The same errors are also seen in the ua.log at the time when the repository was upgraded from 12.2.1.3.0. Attempting to re-seed the ODI Knowledge Modules using groovy script also results in the same errors:

Mapping repository seeding failed
(Subtract 18 from the error line number to account for the standard imports)
oracle.odi.domain.adapter.AdapterException
  at oracle.odi.adapter.OdiAdapter.refreshRepositorySeededObjects(OdiAdapter.java:590)
  at oracle.odi.adapter.OdiAdapter$refreshRepositorySeededObjects$0.call(Unknown Source)
  at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
  at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
  at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133)
  at di.run(di.groovy:19)
  at groovy.lang.GroovyShell.runScriptOrMainOrTestOrRunnable(GroovyShell.java:263)
  at groovy.lang.GroovyShell.run(GroovyShell.java:518)
  at groovy.lang.GroovyShell.run(GroovyShell.java:497)
  at groovy.lang.GroovyShell.run(GroovyShell.java:170)
  at oracle.di.studio.groovy.GroovyScriptRunInstance.run(GroovyScriptRunInstance.java:222)
Caused by: com.sunopsis.dwg.SQLWorkReposException: You can't specify target table 'snp_table' for update in FROM clause
  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1058)
  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096)
  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)
  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)
  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2718)
  at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2139)
  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2442)
  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2359)
  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2343)
  at sun.reflect.GeneratedMethodAccessor196.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  ...

 

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


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