informatica - How Sequence Generator behave when it is aborted? -

how sequence generator behave when aborted?

if sl.no 1 50 loaded target table sequence generator , workflow got aborted, during next run current value? either 1 or 51?

if depends on whether sequence generator transformation reusable or not , if have configured number of cached values.

if non-reusable , not using number of cached values start 1 because due fatal error, @ end of session, not able update repository final current value plus one.

if non-reusable using number of cached values 100, start @ 101 next.

if it's reusable , number of cached values 100, still behave scenario#2 above.

when using number of cached values option draws number configured (100 in our example) , updates repository @ start of session.

**non-reusable vs reusable **

say have table gets loaded 2 different mappings , using sequence generator load keys table. if use non-reusable sequence generator , run these mappings in parallel run contention of keys. why? because non-reusable sequence generator (integration service) starts value saved in repo , @ end of session updates repo next available value.
when use combination of non-reusable , number of cached values (say set 100), start value saved in repo , reserve or cache 100 values session , update repo's next available value. if 30 used in session, remaining 70 discarded. means 70 key values never used. if 100 used access repo again.

in case of reusable transformation mandates configure number of cached values.

the other major difference between reusable , non-reusable cannot reset sequence reusable transformation.