Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon Redshift Configuration
  4. Amazon Redshift Connections
  5. PowerExchange for Amazon Redshift Data Objects
  6. Amazon Redshift Mappings
  7. Pushdown Optimization
  8. Amazon Redshift Lookup
  9. Appendix A: Amazon Redshift Datatype Reference
  10. Appendix B: Troubleshooting

PowerExchange for Amazon Redshift User Guide

PowerExchange for Amazon Redshift User Guide

Success and Error Files

Success and Error Files

The success file contain an entry for each record that successfully writes into Amazon Redshift. The error file contains an entry for each data error.
The Data Integration Service generates success and error files after you run a mapping. Success and error files are .csv files that contain row-level details. The Data Integration Service does not overwrite success or error files. Access the error rows files and success rows files directly from the directories where they are generated. You can manually delete the files that you no longer need.
Consider the following guidelines when you configure the data object operation properties for success files:
  • Specify the Success File Directory in the data object operation properties. Specify a directory on the machine that hosts the Data Integration Service.
  • The success rows file uses the following naming convention:
    infa_rs_<operation>_<schema.table_name>.batch_<batch_number>_file_<file_number>_<timestamp>_success.csv
    .
Consider the following guidelines when you configure the data object operation properties for error files:
  • Specify the Error File Directory in the data object operation properties. Specify a directory on the machine that hosts the Data Integration Service.
  • For insert tasks, the error rows file uses the following naming convention:
    infa_rs_<operation>_<schema.table>.batch_<batch_number>_file_<file_number>_<timestamp>_error.csv
    . For upsert tasks, the error rows file uses the following naming convention:
    infa_rs_<operation>_<schema.table>_<timestamp_inLong>.batch_<batch_number>_file_<file_number>_<timestamp>_error.csv
    .

Sample Error File

If a target table has the fields f_integer, f_char, and f_varchar, and if a row is rejected, the Data Integration Service generates an error file in the following format:
Errors Details
f_integer
f_char
f_varchar
"Query Start Time: 2014-03-24 11:41:30.629 Offending File: INSERT_bdt_with_composite_key.batch_0.csv.0.gz Line Number: 4 Column Name: f_char Column Type: char Offending Value: .......Furniture Values Intl LLC_upd_upd ERROR Reason: Multibyte character not supported for CHAR (Hint: try using VARCHAR). Invalid char: c3 a6"
"3"
""我Furniture Values Intl LLC_upd_upd""
""001E000000SI3jIIAT""
"Query Start Time: 2014-03-24 11:42:00.763 Offending File: INSERT_bdt_with_composite_key.batch_8.csv.0.gz Line Number: 80 Column Name: f_char Column Type: char Offending Value: .......Heitkamp Inc_upd_upd ERROR Reason: Multibyte character not supported for CHAR (Hint: try using VARCHAR). Invalid char: c3 a6"
"9999"
""我Heitkamp Inc_upd_upd""
""001E000000SHd7ZIAT""

0 COMMENTS

We’d like to hear from you!