Informatica Config
Informatica Sequence Generator Config
Most configuration problems come from start values, increment rules, or restart expectations. Lock those first.
Config Priorities
- Start value decides the first emitted number in the mapping run.
- Increment controls how far the generator advances each row.
- Restart behavior matters when a workflow resumes after a failure or a partial load.
Settings to Check
| Setting | What to verify | Risk if wrong |
|---|---|---|
| Start value | Matches the next unused key range. | Duplicate keys in target tables. |
| Increment by | Uses the expected step size. | Unexpected gaps or collisions. |
| Cycle | Usually off for surrogate keys. | Values wrap and overwrite old key ranges. |
| Recovery plan | Documents how restarts re-align keys. | Partial loads become inconsistent. |
Safe Configuration Sequence
- 1Find the current maximum surrogate key in the target table.
- 2Set the start value above that maximum before the next load.
- 3Keep increment at 1 unless you have a documented multi-stream strategy.
- 4Test a restart path so the mapping does not reuse already written keys.
Code
Pre-load target check
SELECT COALESCE(MAX(customer_key), 0) AS current_max_key
FROM dim_customer;FAQ
Should I enable cycle?
Not for surrogate-key generation. Cycling makes value reuse possible and breaks key uniqueness.
Why did my restarted workflow skip values?
Sequence-style generators often favor uniqueness over perfect continuity, so gaps are normal after retries.
Related