Important Messages when Upgrading from Earlier Versions

When Upgrading from previous major versions of RED (a change in the first two version numbers), it is necessary to update each RED metadata repository to complete the upgrade. This is done by completing a validation and recompile of all metadata procedures in WhereScape Setup Administrator. 

Important Message when upgrading to 9.0.2.1 from 9.0.1.x

• Upgrade the RED application and RED Windows Schedulers

Important Message when upgrading to 9.0 Product line from 8.x or earlier 

• Major release change, upgrade all; RED application, RED Windows Schedulers, and the RED Metadata 

Important Message when upgrading from 8.6.1.2 

• You must reenter any encrypted field values in your existing Extensible Source Connections when using this release for the first time.

Important Messages when upgrading from 8.2.1.1 or earlier

• A new metadata service attribute for the DSN architecture has been added in the RED 8.3.1.0 release. Any existing templates that include authentication to the RED repository must be updated to include this attribute if the RED repository is migrated to a 64-bit ODBC DSN (if the attribute is not defined, then a 32-bit architecture is assumed).

For example: [WslMetadataServiceClient.Architecture]::_64bit 

• The Unix and Linux Scheduler scripts for Oracle and Teradata have been altered and need to be applied manually.

Important Messages when upgrading from 8.1.1.0 or earlier

• Teradata customers upgrading from RED versions before RED 8.0.1.0 please be aware that later versions of Setup Administrator have functionality to test the RED metadata tables’ primary indexes. When suboptimal primary indexes are detected Setup Administrator creates a copy of the affected table with the recommended primary index, copies the data to the new table, and finally removes the old table. Please note that sufficient free space in the metadata database is required to temporarily duplicate the largest metadata table that requires migration. Also, any custom statistics on these tables will need to be reapplied.
• WhereScape from the RED 8.2.1.1 version has added certification for the following metadata and target databases:
  • Oracle 12C Release 2
  • Teradata 16.20
  • Microsoft SQL Server 2017
• Cube and Cube Virtual objects are to be deprecated in a subsequent release. Cube objects must be migrated to OLAP Cube objects.
• Microsoft is deprecating support for their Microsoft OLE Driver for Oracle. WhereScape recommends that customers currently using this software migrate to the Oracle OLE Driver.
• WhereScape recommends that you use an Oracle or SQL Server metadata repository and the Windows Scheduler if you wish to use Custom database targets.
• WhereScape wishes to advise customers that work is underway to migrate RED to a 64-bit application over the next 12 months. While the transition is planned to minimize the impact on customers, there may be a requirement to transition to 64-bit ODBC data sources, as part of the upgrade path for this future release of WhereScape RED. No changes are required in the interim. More details will be made available closer to the time the work is completed.

Important Messages when upgrading from 8.0.1.0 or earlier

• SQL Server customers taking advantage of the multiple database support feature are recommended to apply three-part naming in their references to SQL Server tables. For example, in a custom procedure please refer to a data warehouse table using the format <database name>.<schema name>.<table name>. This will offset the impact of different users or machines having different default database set.
• Customers using custom database targets to support RedShift or Snowflake are advised to contact their WhereScape representative for information on taking advantage of RED’s enhanced custom database support features.
• The Data Vault hash key functions for Teradata and Oracle repositories have been changed in the templates (wsl_teradata_utility_dv and wsl_oracle_utility_dv). Data Vault customers running on Teradata or Oracle who were using these templates from the RED 6.9.1.0 release are advised to retain that version of the template unless they migrate any key generated using the previous hash key function.
• The Windows and the UNIX/Linux generated Load and Export scripts for Teradata have been updated to use the new environment variables for identifying the TDPID, the user name and the password to connect to the metadata repository, the target database and the source database for Loads and Exports. Please refer to the section Script Environment Variables of the WhereScape RED User Guide for more information.

Important Messages when upgrading from 6.9.1.0 or earlier

• The Linux Scheduler scripts for Oracle, Teradata, and DB2 have been altered and will need to be applied manually. 

Important Messages when upgrading from 6.8.7.0 or earlier

• In RED, File and Script-based loads from Windows connections create a format file for the BULK INSERT operation in the Work Directory of the Windows Connection. This only applies when loading into an SQL Server target. This directory must be accessible to both the machine running SQL Server and the machine running the WhereScape RED Scheduler. Unless these are always the same machine, a UNC path or mapped network path will be required.
• Legacy hub, link, and satellite objects, created in RED 6.8.7.0 or earlier are still supported in subsequent releases. However, they do not utilize the Data Vault enhancements introduced in release 6.9.1.0.