The WhereScape Migration tool allows you to migrate metadata repositories from WhereScape RED Classic to WhereScape RED 10+. The following sections provide information on how to install and use the WhereScape Migration tool.

The Migration Tooling requires a 'Custom Target' enabled license. This is because the tooling will use the Custom Target database type for loading into the destination PostgreSQL RED metadata database. For customers on a traditional SQL Server, Oracle or Teradata targets your license may need to be temporarily upgraded to support the migration by adding a Custom Target.
| License Fields | Values | Migration Requirements |
|---|---|---|
| Licensed Metadata Database Type(s) | SQL Server, Oracle, Teradata | One or more of SQL Server, Oracle or Teradata |
| Licensed Target Database Type(s) | SQL Server, Oracle, Teradata, Custom | 'Custom' at a minimum |
| Licensed Custom Target Database Type | MySQL | Any Custom Target Type (see the note that follows) |
Licensed Custom Target Database Type is the label in your license given to your Custom target, this will be used for PostgreSQL targets during migration. This is just a display label for the underlying Custom target type. It could be set to anything in your own license and will be discernable in database type dropdowns by having a trailing '*'. So MySQL will appear as MySQL* in RED. For example: your license might have a label of Snowflake*, RedShift* or Synapse* but the underlying database type in RED is Custom. |
Source Metadata:
Data Warehouse:
Destination Metadata:
Tooling Metadata:
The WhereScape Red Migration Tool is a set of scripts and jobs that you can run from RED GUI, the scripts can be divided into three categories.
Scripts running



You must create two PostgreSQL connections with the following characteristics:
| Name | Database Type | Target Name |
|---|---|---|
| Target | Custom* | red |
| Reports | Custom* | red |
*Custom will be your licensed Custom Database Target type which might have a different label in the UI than 'Custom', basically for these two connections we can't use the inbuilt SQL, Oracle or Teradata target types. |
The connection named 'Target' will be your PostgreSQL connection to your database to house the migrated RED metadata repository.



The connection named 'Reports' will be your PostgreSQL connection to your Migration Tooling metadata repository, which allows us to add targets to the tooling metadata database for reporting.






Once the installation finishes, click Finish to close the installer and launch RED.

Enter your login settings and click Connect.

When WhereScape RED starts for the first time, after the installation steps described in the previous section, the script that prepares the Migration Tool executes automatically.
If you get failures in the Reports pane after opening WhereScape RED, then one or more of the preparation steps in the host script named '1_prepare_migration' did not succeed.
Take note of the failure message and see if you can correct the issue, then rerun the script. On subsequent script runs you may get additional failures due to the earlier run having already applied a change but in general rerunning this script will not cause issues and some failures may be dismissed.
If you have not set up the required connections, the Results pane will display a failure message similar to the image shown below. Please expand the Connections node in the left tree and add or amend connections as required before rerunning the script.

If you do add or adjust connections at this point, then ensure you 'Save your Connection Profile' and restart RED so that the in-memory profile of connections credentials is up to date.
The Migration Preparation Script will prompt for two items:


Next, we'll need a Windows Scheduler installed to perform the migration tasks. Follow the Windows Scheduler Installation instructions to install a WhereScape RED Scheduler
Remember your Profile Encryption Secret for later entry into the Scheduler Profile Maintenance wizard. |
After installing the Scheduler ensure to enter your scheduler credentials into the Configuration page of the Scheduler tab in RED, then Save your Profile again to ensure your credentials are preserved between RED sessions.

Before running any jobs, you must first setup the Scheduler Profile which adds the encrypted connection credentials rows for the connections in RED. This makes those credentials available to scheduled jobs. To do this run the Host Script 'wsl_scheduler_profile_maintenance'
You will need your Profile Encryption Secret added during Scheduler installation. |
-
-