Migrate and Reload Metadata Manager Resources
Some models are changed between Metadata Manager versions. If a model has significant changes, such as renamed classes, you must migrate and reload the resources that are based on the model.
If a model has significant changes, the upgrade process marks the resources that are based on the model as deprecated. You cannot create, configure, edit, load, or add schedules for a deprecated resource. If there are deprecated resources in the repository, you must migrate them to the current version of Metadata Manager. You must also migrate resource configuration files for deprecated resource types if you want to upload them into the current version of Metadata Manager. After you migrate resources, you must reload them.
You cannot migrate deprecated Netezza resources or resource configuration files to the current version of Metadata Manager. You must create new Netezza resources to replace the deprecated resources.
The following table lists the types of resources that you must migrate and reload when you upgrade from version 10.0:
| Metadata Source Type
| Resource Type
|
|---|
|
Business Intelligence
| Cognos
Tableau
|
| Data Integration
| Microsoft SQL Server Integration Services
|
| Data Modeling
| ERwin
SAP PowerDesigner
|
| Database Management
| JDBC
|
When you upgrade from version 10.0, you must also purge and reload some data integration and database management resources.
The following table lists the types of resources that you must purge and reload when you upgrade from version 10.0:
| Metadata Source Type
| Resource Type
|
|---|
| Data Integration
| PowerCenter
|
| Database Management
| Cloudera Navigator
IBM DB2 for Linux, UNIX, and Windows
IBM DB2 for z/OS
IBM Informix
Microsoft SQL Server
Oracle
Sybase ASE
Teradata
|
Migrate resources and resource configuration files with the migration utilities, rmu and rcfmu.
