Table of Contents

Search

  1. Preface
  2. Data integration tasks
  3. Mapping tasks
  4. Dynamic mapping tasks
  5. Synchronization tasks
  6. Data transfer tasks
  7. Replication tasks
  8. Masking tasks
  9. Masking rules
  10. PowerCenter tasks

Tasks

Tasks

Rules and guidelines for flat file sources and targets

Rules and guidelines for flat file sources and targets

Use the following rules and guidelines for flat file sources and targets:
  • All date columns in a flat file source must have the same date format.
    Rows that have dates in a different format than the one specified in the
    synchronization
    task definition are written to the error rows file.
  • Each flat file target must contain all fields that will be populated by the
    synchronization
    task.
  • The
    synchronization
    task truncates a flat file target before writing target data to the file.
    To avoid overwriting target data, you might use a post-session command to merge target data with a master target file in a different location.
  • The flat file cannot contain empty column names. If a file contains an empty column name, the following error appears:
    Invalid header line: Empty column name found.
  • Do not map binary fields when you use a flat file source or target in a
    synchronization
    task.
  • Column names in a flat file must contain printable tab or ASCII characters (ASCII code 32-126). If the file contains a character that is not valid, the following error appears:
    Invalid header line: Non-printable character found. The file might be binary or might have invalid characters in the header line.
  • You can use a tab, space, or any printable special character as a delimiter. The delimiter can have a maximum of 10 characters. The delimiter must be different from the escape character and text qualifier.
  • For flat file sources and targets with multibyte data on Linux, the default locale must be UTF-8.

0 COMMENTS

We’d like to hear from you!