Deployment Suite for Oracle 6

Redgate Change Control 2 release notes

Deployment Suite for Oracle has been replaced by Redgate Deploy - Oracle. This page is therefore no longer being updated. For the latest documentation, please click here.

2.30.9261 - June 25 2020

Improvements

  • Improved error messaging when attempting to commit if no files are selected.
  • Improved error messaging for when saving migrations scripts fails.

Changes

  • Extended integrated Flyway license

Fixes

  • Fixed error when committing if the repository root was not the same as the RCC project root.

  • Fixed the rendering of the changes table on the Version Control tab.

2.29.9197 - June 22 2020

Improvements

  • Added a confirmation modal when pushing commits.

  • Stop listing remote git branches that have been deleted in the branch-switch dropdown.

  • Enable primary actions to be triggered by pressing ctrl+enter.

  • Allow specific files to be selected for committing.

Changes

  • Upgraded the Redgate Oracle Schema Comparison engine to v5.7.4.3169
  • Upgraded Flyway to v6.4.4

Fixes

  • Fixed an issue where the user-defined logging level was being reset to Default when opening the app.

  • Fixed an issue where no comparison differences would be shown after deleting local migration scripts from the project.

  • Fixed an issue where an error message was being incorrectly displayed during the New Project wizard.

  • Fixed an issue where the default placeholder text for the JDBC Url was missing from the baseline setup modal.

2.28.9017 - June 11 2020

New Features

  • Added a couple of new version control integration features:
    • Create new branches
    • Switch branches from any tab

Improvements

  • Added description to the pull and push actions
  • Improved success message when pulling changes
  • Improved the commit pane design
  • Improved error messages when using the Version Control tab

Changes

  • Upgraded the Redgate Oracle Comparison engine to v5.7.4.3129

2.27.8815 - June 5 2020

New Features

  • **Experimental**: Version control Redgate Change Control projects from within the application. This is currently limited to a few basic git actions (pull, push, commit). Learn more.
    • Pull latest changes from the remote repository
    • Commit new migration scripts
    • Push new commits to the remote repository

Improvements

  • Improves the information modal shown when editing migration scripts when working with a shadow scripts folder.

  • Adds page auto-refresh after performing a reset or resync of a shadow scripts folder.

  • Improved error messaging throughout the app.

Changes

  • Upgraded Redgate Oracle comparison engine to v5.7.4.3111

  • Upgraded flyway to v6.4.3

Fixes

  • Corrects the wording of the baseline success message

  • Fixes an issue where the shadow scripts folder desync success message was not cleared on manually refreshing the page.

  • Fixes an issue where updating the shadow scripts folder during a baseline would fail if there were no comparison differences.

  • Fixes an issue with broken styling in the New Project wizard.

2.26.8552 - May 28 2020

New Features

  • **Experimental**: Use a shadow scripts folder for generating migration scripts instead of a shadow database. Learn more
    • Requires the environment variable SHADOW_SCRIPTS_FOLDER to be set.
    • Enable users to reset and resync the shadow scripts folder from the help menu.

Changes

  • Improves progress and error messaging in the UI when creating new projects.

  • Improves the copy to clipboard button design

  • Improves styling of error messages arising from flyway failures

Fixes

  • Removes the introductory page from the New Project wizard.

  • Upgrade Redgate Oracle schema comparison engine to v5.7.4.3068

2.25.8163 - May 14 2020

Changes

  • Improved the types of error messages displayed in the UI.
  • Upgraded the Redgate Oracle Comparison engine to v5.7.4.3020
  • Upgrade the Redgate SQL Comparison engine to v14.2.14.15827
  • Upgrade Flyway to v6.4.2

Fixes

  • Validation errors are now displayed on the generate migrations tab.

2.24.8037 - May 12 2020

Changes

  • Upgraded the Redgate SQL Server comparison engine to v14.2.14.15786
  • Upgraded the Redgate comparison reports generator to v5.1.1.576

Improvements

  • Paths to Source Control for Oracle projects are now validated in the new project wizard.

Fixes

  • An error is now displayed in the new project wizard if invalid credentials are provided for the baseline target.

2.23.7927 - May 09 2020

Improvements

  • Added a help widget for setting target schemas for hybrid-mode projects in the New Project wizard

Changes

  • Upgraded the Redgate Oracle Comparison engine to v5.7.4.2983

2.22.7845 - May 06 2020

Changes

  • Improved error reporting during saving migration scripts.
  • Upgraded the Redgate Oracle Comparison engine to v5.7.4.2980

Fixes

  • Migration scripts can now be saved in Hybrid mode.

2.21.7806 - May 05 2020

Changes

  • Baselining is no longer required for unsupported database types.
  • Some log messages have had their formatting improved.
  • UI improvements have been made to the test connection button in the new project wizard.

Fixes

  • Migrations are no longer marked as pending in Hybrid mode projects.
  • The generate scripts page is now disabled for unsupported database types.
  • The config file property redgate.scriptsSource  is now set to a relative path instead of a literal one during hybrid-mode project creation.

2.20.7737 - May 3 2020

Changes

  • Upgraded the Oracle comparison engine to v5.7.3.2974

Fixes

  • Fixed an issue where a prompt to baseline the project wrongly when using hybrid mode.

2.19.7543 - April 28 2020

Improvements

  • Errors are now reported after managing credentials.

Changes

  • Upgraded the Oracle comparison engine to v5.7.2.2927

Fixes

  • Fixed an issue where baselining could cause an ENAMETOOLONG error.

2.18.7333 - April 22 2020

Changes

  • Upgrade Flyway to v6.4.0

Fixes

  • Errors when saving migration scripts are now shown in the UI

2.17.7297 - April 20 2020

New Features

You can now use Source Control for Oracle filter files to filter out database objects.

How to use:

To use filters with RCC you will have to first generate a filters file using Source Control for Oracle. See https://documentation.red-gate.com/soco5/using-source-control-for-oracle/using-filters.

Once you have a filters file:

  • make sure you copy and paste the file to the root of your project (i.e. the same level as your .conf file).

  • go to your .conf file and add redgate.filter=./<filters file>

2.16.7261 - April 20 2020

New Features

You can now use Schema Compare for Oracle ignore rules to filter database objects.

How to use:

To use ignore rules with RCC you will have to first generate an ignore rules file using Schema Compare for Oracle. See https://documentation.red-gate.com/sco5/setting-up-the-comparison/using-ignore-rules.

Once you have an ignore rules file:

  • make sure you copy and paste the file to the root of your project (i.e. the same level as your .conf file).
  • go to your .conf file and add redgate.ignoreRules=./<ignore rules fileName>

Fixes

  • Fixed an issue where a baseline error was displayed after clicking the "skip and create" button in the New Project Wizard.

2.15.7155 - April 16 2020

Improvements

  • The Help menu now contains a 'Manage My License' option on Windows installations.

Changes

  • No longer require .Net Framework 4.7.2 for installation.

2.14.7016 - April 11 2020

Improvements

  • Improved the validation of the user-provided settings when creating a baseline

  • Improved validation checks of connection details provided during the New Project wizard

  • Enabled database baselining when working with hybrid projects

Changes

  • Upgraded the Oracle comparison engine to v5.7.2.2892
  • Upgraded Flyway to v6.3.3
  • Changed the default tab to be 'Generate migrations'
  • No longer allow progression through the New Project wizard with invalid connection details

Fixes

  • Fixed an issue where warnings were not displayed in the New Project wizard when returning to a previously visited step

2.13.6826 - April 6 2020

Improvements

  • Added a help popup for setting the schema on the Development Source page in the New Project wizard.
  • Show better errors when opening invalid projects.

Changes

  • Upgraded the Oracle comparison engine to v5.7.2870.

Fixes

  • Improved the error messages shown when performing a baseline fails.

  • Fixed an issue where users were prompted to enter shadow database credentials when no shadow database was configured.

2.12.6622 - March 31 2020

Changes

  • Upgrade Oracle Schema Comparison engine to v5.7.1.2841.

  • Upgrade Flyway to v6.3.2.

  • Clarify the descriptive text on the Generate Migrations summary page.

  • Use the Source Control for Oracle logo on the development source page in the New Project wizard.

Fixes

  • Correctly ship all third-party licenses including the Oracle FUTC.

  • A missing schema is now considered to be empty when performing a comparison.

2.11.6390 - March 23 2020

Improvements

  • Enabled projects with no shadow database connection set up to be opened without throwing an error.

  • Added a Learn More link to the development source set up page in the New Project wizard.

Changes

  • Updated the Oracle Schema Compare Engine to v5.7.1.2812.

2.10.6230 - March 13 2020

New Features

  • Using Source Control for Oracle as a development source is no longer an experimental feature.

Improvements

  • Redesigned the New Project wizard to enable creation of projects using the hybrid mode (i.e. Source Control for Oracle as development source).
  • Add warning messages to the UI when resolving project parameters goes wrong.

Changes

  • DEPRECATED: The *.conf parameter Redgate.experimental.scriptsSource is now deprecated in favour of Redgate.scriptsSource

  • Upgraded Redgate Oracle Schema Compare Engine to v5.7.1.2785
  • Upgraded Flyway by Redgate to v6.0.3

Fixes

  • Fixed an issue where the rcc-author.exe file had the incorrect copyright details.
  • Ignore permission differences when generating migration scripts in hybrid mode.
  • Fixed the afterMigrate__fix_invalid_objects.sql script to enable it to comply with the default Code Analysis for Oracle rules used by Redgate Change Automation.

2.9.5930 - March 5 2020

Changes

  • Renamed the DEVELOPMENT DATABASE tab to DEVELOPMENT SOURCE.
  • Upgraded redgate.oracle.schemacompare.engine to v5.7.1.2748

Fixes

  • No longer incorrectly report the creation of a migration script when no script was created.
  • Fixed an issue where generated Repeatable Migration scripts were incorrectly displayed as empty.
  • Fixed an issue where the previously opened projects list was being cleared.

2.8.5753 - March 2 2020

Improvements

  • Started ignoring redgate_schema_history table indexes when generating comparison differences.

Fixes

  • Fixed an issue where objects that are depended upon by changed objects were incorrectly automatically included in migration scripts.

2.7.5655 - February 26 2020

Fixes

  • Fixed an issue where objects belonging to the schema history table would appear in the differences table.

2.6.5603 - February 21 2020

Fixes

  • Fixed an issue which could reset recently opened projects list.
  • Updated Flyway to v6.2.4
    • Fixes an issue where Flyway could crash if the schema history table was in an unexpected state.
    • Oracle SQL*Plus parsing extended to support SPOOL

2.5.5397 - February 18 2020

Improvements

  • Added ability to enable verbose logging via help dropdown.
  • General error handling improvements / fixes.

Fixes

  • Ensure all Redgate CLIs are appropriately signed.
  • Fixed an issue where loading project failed due to a missing config.
  • updated Flyway to v6.2.3
    • Includes fix for https://github.com/flyway/flyway/issues/2669.

Changes

  • update dependency redgate.oracle.schemacompare.engine to v5.7.0.2668

2.4.4938 - February 05 2020

Changes

  • Updated dependency redgate.oracle.schemacompare.engine to v5.7.0.2630.

Fixes

  • General error handling improvements / fixes.
  • Avoid cases where RCC crashed with a white screen.
  • Provides additional information in some cases when Flyway failed.

2.3.4166 - January 14 2020

Improvements

  • The difference table's UI performance has been improved.
  • A better error is displayed when an invalid path is given to the New Project Wizard.

Changes

  • The auto-generated afterMigrate.sql file has now been renamed to afterMigration__fix_invalid_objects.sql.

Fixes

  • Fixed an issue where the Apply to database tab's content was not updated after a baseline completes.
  • Completing a baseline successfully now displays the correct success message.
  • Fixed an issue where the list of added dependencies, in the script generation tab, was being reported incorrectly.
  • Fixed an issue where we were not accepting underscores in the hostname part of a JDBC URL.

2.2.3902 - December 19 2019

Improvements

  • Improved error handling when oracle jdbc drivers are missing from the flyway installation.
  • Improved error message when schemas are missing from the dev or shadow databases.

Changes

  • - The default baseline version is now "001" instead of "0.1".
  • Improved the layout of the baseline page.
  • The "last updated" / "new changes" messages on the "Generate migrations" tab have been improved to be clearer and more visible.

Fixes

  • Fixed an issue which prevented the baseline suggestion message from appearing on the "Apply to database" tab.
  • Automatically generated versions will now preserve leading zeros from the previous version.
  • Fixed an issue where a v2 Deployment Suite for Oracle license key would not correctly activate a v2.1 installation.

2.1.3732 - December 13 2019

Improvements

  • Checking for updates to the tool can now be triggered manually from the Help menu.
  • Log files for the tool can now be reached through the Help menu.
  • Credentials entered in the New project wizard are now encrypted instead of written to the flyway.conf file.
  • The Test connection buttons in the New project wizard now check all the necessary fields are completed.
  • Improve the content and location of baseline messages

Changes

  • The parameters Username, Password and Schemas are now required in the New project wizard.
  • The Show files on disk buttons have been removed and replaced with clickable folder paths in the header bar.

Fixes

  • Fixed an issue in hybrid mode where the path to the scripts source was being incorrectly resolved.
  • Fixed an issue where the table of migrations on the Apply to database page was sorting incorrectly.

2.0.3671 - December 10 2019

New Features

Redgate Change Control is no longer marked as a beta, and now uses full Redgate licensing. A new trial should be started: if you need any assistance then get in touch.

Improvements

  • When redgate.experimental.scriptsSource is specified, the product will now check for a DatabaseInformation.xml file in the specified location. This helps ensure a correct scripts folder is specified.
  • Handy "Show files on disk" buttons have been added in various places to the UI.

Changes

  • The column headers in the comparison results table have been renamed to match SQL Change Automation.
  • The credentials page wording has been updated to specify dev and shadow databases.

Fixes

  • Fixed an issue where a failure in the script generation step didn't have a way to get back to the comparison.
  • If the flyway baseline step fails, the generated baseline script will no longer be left behind.
  • Empty baseline scripts will now be saved if necessary.
  • Any errors while saving generated migration scripts to disk will now be correctly displayed in the UI.
  • Fixed an issue where stale results would occasionally be shown in the comparison results diff viewer.
  • Running comparison operations are now fully cancelled when new migration scripts are applied to the database.
  • The flyway schema history table is now filtered out of the recent changes notification check.

Known issues

  • We've identified a possible issue when upgrading from RCC 1.3 or earlier where the comparison may fail with a Could not load assembly Newtonsoft.Json error. If this occurs, then uninstalling and reinstalling RCC will fix the issue.

Didn't find what you were looking for?