Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Best Practices for Working With Batch Jobs

While you design and plan your batch jobs, consider the following issues:

Define your schema.

The schema is fundamental to all your Informatica MDM Hub tasks. Without a schema, your batch jobs have nothing to do.

In Oracle environments, limit the parallel degree by which Oracle gathers statistics to avoid using an excessive amount of processes. Excessive processes for gathering statistics could leave insufficient resources for Hub processing. See Limiting the Parallel Degree for Statistic Gathering.

Define mappings before executing Stage jobs.

Mappings define the transformations performed in Stage jobs. If you have no mappings defined, then the Stage job will not perform any transformations in the staging process.

Define match rules before executing Match jobs.

If you have no match rules, then the Match job will produce no matches.

Before running production jobs:

Run tests with small data sets.

Run tests of your cleanse engine and other components to determine whether each component is working as expected.

After testing each of the components separately, test the integrated system in its entirety to determine whether the overall system is working as expected.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Best Practices for Working With Batch Jobs

Best Practices for Working With Batch Jobs