Error using the Amazon Redshift connector - "Invalid JSONPath format: Member is not an object"

Error using the Amazon Redshift connector - "Invalid JSONPath format: Member is not an object"

book

Article ID: KB0076462

calendar_today

Updated On:

Products Versions
TIBCO Cloud Integration - Connect ( Scribe ) -

Description

Product: TIBCO Scribe® Online 
Connector: Amazon Redshift

Error: "Operation failed. Label: Copy AmazonS3Storage, Name: AmazonS3StorageCopy, Message: ERROR:XX000,Load into table 'contacts' failed. Check 'stl_load_errors' system table for details. : Error in calling Operation Copy System.Exception: ERROR:XX000,Load into table 'contacts' failed. Check
'stl_load_errors' system table for details."

Looking at the 'stl_load_errors' system table in Redshift shows the following error:Invalid JSONPath format: Member is not an object.

Issue: The issue is due to the data not being exported in the correct format. You need to ensure that the data is exported in “Redshift” format. Any data that has been exported into the bucket that was not in “Redshift” format will cause an issue, so you will need to export all the data into a new bucket."

Issue/Introduction

The “Invalid JSONPath format: Member is not an object” error is due to the data not being exported in the correct format.

Resolution

1. Re-export the data into a different bucket ensuring the format is Redshift and verify the data. Map only the required fields needed, not all fields.
2. If one entity is exported in non-Redshift format it will cause this problem.

In troubleshooting we identified the problem was a 'zipcode' field where the values contained a '+' symbol

Additional Information

https://help.scribesoft.com/scribe/en/index.htm#sol/conn/redshift.htm?Highlight=redshift
https://docs.aws.amazon.com/redshift/latest/dg/r_STL_LOAD_ERRORS.html