Upgrading from Version 10.0

10.2

Back Next

Re-create Netezza Resources

Effective in version 10.1.1, the Netezza model is changed to support multiple schemas. Metadata objects in the Netezza model are organized by schema instead of by database. Because of the model change, you must re-create Netezza resources in the current version of Metadata Manager.

The model change makes Netezza resources behave like other relational resources. When you create a Netezza resource, you select the schema or schemas from which to extract metadata. Metadata Manager organizes Netezza objects in the metadata catalog by schema. When you configure connection assignments to Netezza, you select the schema to which to assign the connection.

The upgrade process marks the previous Netezza model and all resources that are based on the model as deprecated. You can view the deprecated model and resources, but you cannot create, configure, edit, load, or add schedules for deprecated resources.

After you upgrade, you must create new resources to replace the deprecated Netezza resources. You cannot run the rmu or rcfmu migration utilities to migrate Netezza resources from the previous version of Metadata Manager to the current version.

To re-create Netezza resources, perform the following tasks:

If you added custom class attributes to the previous Netezza model, add the attributes to the new model.

If you uploaded rule set definition files to the previous model, upload the rule set definition files to the new model.

Create new resources to replace the deprecated resources.

When you create a new resource, select the schemas from which you want to extract metadata.

Load the new resources to import the metadata.

If you updated the values of custom attributes or the business names for objects in the previous resources, update these values in the new resources.

If any business intelligence, data modeling, or data integration resource contains a connection to a Netezza database, perform either of the following tasks:

If the resource uses automatic connection assignments, reload the resource or use the

Resource Link Administration

window to reestablish the data lineage links.

If the resource uses manual connection assignments, reassign the connections to a Netezza schema instead of a database. Then, reload the resource or use the

Resource Link Administration

window to reestablish the data lineage links.

Optionally, delete the deprecated Netezza resources.

Metadata Manager Service