My Oracle Support Banner

SVN: ODI Artifact That Was Re-imported or Re-Created After a Delete Fails to Be Added to VCS with Error "ODI-12050: Unable to add object" (Doc ID 2313858.1)

Last updated on MAY 24, 2018

Applies to:

Oracle Data Integrator - Version 12.2.1.2.6 and later
Information in this document applies to any platform.

Symptoms

When attempting to import an Oracle Data Integrator (ODI) object, i.e. a mapping, that was exported from another master / work repository (MR/WR) into a versioned MR/WR where it existed previously but was deleted, the following error occurs when adding the object for versioning:

ODI-12050: Unable to add object [Mapping:MAP_<NAME>], as an ODI artifact exists with the same name in Subversion repository.

The same occurs if the object was manually re-created instead of imported.

The issue can be reproduced at will with the following steps:

  1. Delete a versioned object such as mapping from branch repository
  2. Clone trunk repository, login with ODI Studio and don't apply or configure any versioning
  3. Modify the same mapping that was deleted in branch and export it
  4. Import the mapping to branch, ie: right-click on Mappings, and select to import using synonym insert_update mode
  5. Select to add the mapping to Apache Subversion (SVN), ie: right-click on mapping, select "Version" Add to VCS....

or:

  1. Delete a versioned object such as mapping from branch repository
  2. Manually re-create an object with the same name and save
  3. Select to add the mapping to Apache Subversion (SVN), ie: right-click on mapping, select "Version" Add to VCS....

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!


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