Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Expression transformation
  7. Filter transformation
  8. Input transformation
  9. Joiner transformation
  10. Lookup transformation
  11. Mapplet transformation
  12. Normalizer transformation
  13. Output transformation
  14. Rank transformation
  15. Router transformation
  16. Sequence transformation
  17. Sorter transformation
  18. SQL transformation
  19. Union transformation

Transformations

Transformations

Sequence transformation rules and guidelines

Sequence transformation rules and guidelines

Consider the following guidelines when you create a Sequence transformation:
  • When you map the NEXTVAL or CURRVAL output fields, ensure that the data type of the mapped field is appropriate.
  • When you run the mapping in the Mapping Designer, the current value is not saved so each time you run the mapping, it begins with the initial value.
  • When you run the task in the
    mapping
    task wizard, you can edit the current value to start the sequence with a specified value.
  • Before the Sequence transformation runs,
    Data Integration
    checks for sufficient space between the starting value and the end value. If you set an end value that's too close to the starting value, the mapping fails with a sequence overflow error. This error can occur even if the starting value plus the number of rows processed would be less than the end value. If you encounter a sequence overflow error, increase the end value.
  • You can't use a Sequence transformation in a mapplet.
  • In mappings in SQL ELT mode, you can't use shared sequences.
  • In mappings in SQL ELT mode, a Sequence transformation needs to be connected directly to a downstream Expression transformation or target.

0 COMMENTS

We’d like to hear from you!