Page History
...
| Info | ||
|---|---|---|
| ||
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
Source Metadata:
- A RED Metadata Repository on SQL Server, Oracle or Teradata which has a RED version of 8.6 or higher
- ODBC DSN and user with at least select permissions to the source metadata database.
Data Warehouse:
- Any data warehouse platform where the RED 10 version of the WhereScape Target Enablement Pack is available.
...
Destination Metadata
- Metadata has been validated.
- All objects have been versioned.
- Nested jobs are not supported in RED 10, these should be separated out prior to the migration for best results.
| Info |
|---|
*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. |
Migration Target
Destination Metadata:
- An empty PostgreSQL database to become your migrated metadata repository.
- An ODBC DSN and user with full permissions on the database (see setting up users in PostgreSQL for RED).
- Compatible PostgreSQL command line tools.
Tooling Metadata
Tooling Metadata: Metadata:
- A supported RED Metadata Repository on PostgreSQL (with lowercase db name).
- ODBC DSN and user with full permissions on the metadata database.
- Compatible PostgreSQL command line tools .
Configuration:
- RED 10 compatible WhereScape Target Enablement Pack installed.
- A clean repository: except EP installation no new objects should be created.
- Azkaban Scheduler installed and operational.
- Set Default Update Templates in Object Type Maintenance if not already set.
Connections:
- All connection objects in the source metadata will be migrated to the target metadata so only the target connection for Custom* database created as a part of the EP install is required.
...
- .
Migration Tool
- The tool should be unzipped to a local directory on the system where the migration script will be run.
- Requires a Windows user with permissions to run a cmd as administrator in order to relax the PowerShell ExecutionPolicy to run the migration script.
- The latest RED 10 version should be installed on the system running the migration with a valid license installed and the EULA accepted for the windows user running the migration tool.
- PostgreSQL tools should be available on the environment variable “Path” for the Azkaban service user. Psql.exe is used in a Powershell script to bulk load the source metadata to the target.
...