Automatic PowerCenter Mappings and Workflows Rules and Guidelines
Automatic PowerCenter Mappings and Workflows Rules and Guidelines
When you publish or consume data sets with automatic mappings, consider the following rules and guidelines:
Data Integration Hub
creates PowerCenter entities for each automatic mapping. Each PowerCenter entity name starts with the prefix
DIH__
. Do not manually change or delete the PowerCenter entities.
You cannot use high precision processing in PowerCenter to run automatic mappings. To use high precision, use a custom mapping.
Do not manually change or delete tables in the publication repository that store data sets from publications with automatic mappings.
Automatic mappings run with the DIH__STAGING and the DIH__REPO PowerCenter connections. To prevent publication or subscription failure, do not change or delete the connections.
When you publish varbinary or nvarchar datatypes from a Microsoft SQL Server database source, PowerCenter converts the data size limit to a fixed size of 100 MB. If you create a subscription with an automatic mapping that writes the published data to a Microsoft SQL Server database target, you must change the data size limit to MAX when you create the target tables before you run the subscription workflow.
When you use tables from a default schema to publish from a relational database or to subscribe to a relational database, the schema name is not persistent.
When you use tables from a non default schema to publish from a relational database or to subscribe to a relational database, the schema name is persistent.
Schema names are saved in the Mapping tab of the PowerCenter session in the following locations:
For publications, the schema name is saved in the Source properties in the
Owner Name
field.
For subscriptions, the schema name is saved in the Target properties in the