ODI 12c SVN / Git Partial Tag Adds New Version of All Modified Objects Impacting ODI Performance
(Doc ID 2316954.1)
Last updated on JULY 30, 2024
Applies to:
Oracle Data Integrator - Version 12.2.1.2.6 to 12.2.1.4.200618 [Release 12c]Oracle Data Integrator on Marketplace - Version 1.0.2 to 12.2.1.4.200618
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Information in this document applies to any platform.
Symptoms
When versioning artifacts in Oracle Data Integrator (ODI) 12c integrated with Apache Subversion (SVN) Version Control System (VCS), in addition to the selected and dependent objects, new versions are created for non-dependent objects in the SVN branch.
It is expected that only selected objects and their dependencies are versioned.
To reproduce the issue:
- Log into trunk or branch repository
- Modify an object, i.e.:
Project: PRJ1
Folder: TESTFOLDER1
Package: TESTPACKAGE1 (make a change such as adding OdiBeep) - Save the change.
- Make the same change to another object, i.e.:
Folder: TESTFOLDER2
Package: TESTPACKAGE2 (make a change such as adding OdiBeep). - Save the change.
- Create a partial tag, and only include one package:
Project: PRJ1
Folder: TESTFOLDER1
Package: TESTPACKAGE1 - Notice once the partial tag has been created, both TESTPACKAGE1 and TESTPACKAGE2 have new versions in SVN
The same can be observed when in an ODI environment configured with Git.
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! |