ODI Objects Not Marked Versioned in VCS After Back and Forth of "Switch Versioning Application"
(Doc ID 2465052.1)
Last updated on JULY 26, 2024
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 and laterOracle Data Integrator on Marketplace - Version 1.0.2 and later
Oracle Data Integrator Cloud Service - Version 17.2.1 and later
Information in this document applies to any platform.
Symptoms
In an Oracle Data Integrator (ODI) repository configured with Version Control System (VCS), when attempting to switch versioning applications multiple times, none of the ODI objects show as versioning in the VCS, even though they were checked in before. This can happen while using GIT or Apache Subversion (SVN).
To reproduce:
- Login to ODI Studio and configure with VCS
In the Team dropdown, select Swich Versioning Application.... - In the Team dropdown, under the Settings sub-menu select Edit Connections... and configure with the VCS.
- Once configured, add ODI objects to VCS:
In the Team dropdown, under the VCS Actions sub-menu, select Add non-versioned Objects... - Then switch versioning applications to ODI
In the Team dropdown, select Switch Versioning Application.... - Now switch back to the VCS:
In the Team dropdown, select Switch Versioning Application....
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! |