Table of Contents

Search

  1. Preface
  2. Mappings
  3. Mapplets
  4. Mapping Parameters
  5. Mapping Outputs
  6. Generate a Mapping from an SQL Query
  7. Dynamic Mappings
  8. How to Develop and Run a Dynamic Mapping
  9. Dynamic Mapping Use Cases
  10. Mapping Administration
  11. Export to PowerCenter
  12. Import From PowerCenter
  13. Performance Tuning
  14. Pushdown Optimization
  15. Partitioned Mappings
  16. Developer Tool Naming Conventions

Developer Mapping Guide

Developer Mapping Guide

Column Indicators

Column Indicators

A column indicator appears after every column of data. A column indicator defines whether the data is valid, overflow, null, or truncated.
The following table describes the column indicators in a reject file:
Column Indicator
Type of data
Writer Treats As
D
Valid data.
Good data. Writer passes it to the target database. The target accepts it unless a database error occurs, such as finding a duplicate key.
N
Null. The column contains a null value.
Good data. Writer passes it to the target, which rejects it if the target database does not accept null values.
T
Truncated. String data exceeded a specified precision for the column, so the value was truncated.
Bad data, if you configured the mapping target to reject overflow or truncated data.
Null columns appear in the reject file with commas marking their column. The following example shows a null column surrounded by good data:
0,D,5,D,,N,5,D
The column indicator "D" also appears after each row indicator. The following example shows the column indicator "D" after the row indicator "0":
0,D,2001123456789,O,S. MacDonald,D,Ira,D,415-541-514566,T
Either the writer or target database can reject a row. Consult the log to determine the cause for rejection.

0 COMMENTS

We’d like to hear from you!