Even Though ODI Is Configured with Git / SVN VCS, Options to Apply Deployment Archive Are Not Disabled
(Doc ID 2805169.1)
Last updated on JULY 30, 2024
Applies to:
Oracle Data Integrator - Version 12.2.1.4.0 to 12.2.1.4.210517 [Release 12c]Oracle Data Integrator on Marketplace - Version 12.2.1.4.201011 to 12.2.1.4.210517
Information in this document applies to any platform.
Symptoms
Using Oracle Data Integrator (ODI) 12.2.1.4, even though the documentation mentions that the option to initialize Deployment Archive should be disabled when a Repository is configured with Version Control System (VCS), this option is not only available, but it also works.
According to documentation "Initialize Deployment Archive" and "Patch Deployment Archive" options should be disabled:
https://docs.oracle.com/en/middleware/fusion-middleware/data-integrator/12.2.1.4/odidg/release-management.html#GUID-FFE9165C-D618-476E-87C0-C7E9C0670458
"You can initialize an ODI repository that is not connected to VCS with the contents of an initial deployment archive. If VCS connectivity is configured then it is assumed to be a development repository and thus the options to apply deployment archive are disabled."
The issue can be reproduced at will with the following steps:
- Configure ODI Repository with Git
=> the repository is empty - Add all non-versioned objects
=> this will add topology objects, and work repository global templates, as there are no other work repository objects - Initialize a Deployment Archive
Team -> Deployment Archives -> Initialize Deployment Archive...
=> this works
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! |