The Secure Agent generates success and error files after you run a mapping. Success and error files are
.csv
files that contain row-level details.
You cannot use success and error files when you run a mapping in advanced mode.
The Secure Agent generates a success file after you run a mapping. The success file contains an entry for each record that successfully writes into Amazon Redshift. Each entry contains the values that are written for all the fields of the record. Use this file to understand the data that the Secure Agent writes to the Amazon S3 bucket and then to the Amazon Redshift target.
The error file contains an entry for each data error. Each entry in the file contains the values for all fields of the record and the error message. Use the error file to understand why the Secure Agent does not write data to the Amazon Redshift target.
The Secure Agent 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 mapping properties for success files:
You must provide the file path where you want the Secure Agent to generate the success rows file.
The success rows file uses the following naming convention:
<timestamp>success
Consider the following guidelines when you configure the mapping properties for error files:
You must provide the file path where you want the Secure Agent to generate the error rows file.
The success rows file uses the following naming convention:
<timestamp>error
The insert and upsert tasks error rows file follows the same naming convention.
When you define a error file directory, you can use the variable
$PMBadFileDir
. When you use the
$PMBadFileDir
variable, the application writes the file to the following Secure Agent directory: