9.0 New features
Data Compare Command Line Wizard
The new Data Compare Command Line wizard simplifies the creation of the command line xml config file.
Schema Compare Command Line
The previous release of the Comparison Toolset for Oracle Database and therefore there are no new features or fixed issuesdid not include a command line for the Schema Compare.
Schema Compare Command Line Wizard
Intended to simplify the creation of the command line config file.
A new and unified interface for all Oracle connection, used by schema, data and the command lines. The connection includes the following changes:
- Adds the option to use Oracle-specific connection settings.
- Includes the ability to check the validity of these settings.
- Removes support of the TNS connection type, mainly for simplicity.
Adds support for Oracle 18c and 19c
This release supports the new Oracle 18c and 19c versions.
9.0 Fixed issues
- The help file is updated, including a new section for the command lines.
- Data command line includes an option to encrypt Oracle credentials and the data source stored in the command line config file. The same option is supported by the schema command line as well.
- Data command line supports the UTF32 file encoding. The previous UTF7 is removed.
- Data Compare script no longer drops disabled triggers or foreign keys. Disabled constraints have no impact on the synchronization process.
- Data command line no longer requires the schema in the object name.
- Data Compare now sets the transaction isolation level to READ COMMITTED. This level works much better than the previous setting, which was Serializable. READ COMMITTED is also the Oracle default value.
- Schema filters are simplified. These filters are intended to provide object exclusion. Initially, filters were advertised to achieve both inclusion and exclusion, which caused confusion.
- Schema Compare no longer collects information about tablespaces, data files, or temp data files. The Oracle views that contain this information require admin permissions and fail in most cases.
- Schema Compare now collects the current user and the user schema from the user context. The Oracle views used in the previous version needed admin permissions.
- A fix in the trigger script now shows the trigger status in Schema Compare. This information is useful when the triggers are disabled.
- A change in the definition parsing of views, procedures, functions, packages, types, and triggers fixes some rare issues related to scripting of these objects.
- Schema Compare now supports the schema triggers, similar to the DDL trigger on SQL Server.