Connections

Connections ( Bulk data load )

Note Oracle source

Connection created with source database as Oracle

Oracle as source

1. Target datatype is created as Numeric/Double when source is Number:

Issue description: When the datatype at source is Number without any precision or scale then datatype created in the target redshift is of Numeric/Double

Explanation: As per the AWS documentation when the scale and precision is 0 at the source we have to use a Real equivalent datatype in the target, Refer for this link more details in the data types section.

Generic

• When a task is created with Target location as S3 and has a transformation rule to remove column then data is being distorted in the csv files that are created in S3. This is because of a bug on AWS end and nothing has to do with Amorphic, AWS doesn’t have any ETA when this issue will be fixed, if AWS fixed the issue then it will get automatically reflected in Amorphic.

Connections ( Normal data load )

S3 connection as source

Description: If the source folder has multiple files with same names(In subfolders) then only one file will be ingested into the target.

Explanation: This occurs when the file type is of xlsx and the target is of DWH (AuroraMysql/Redshift) because when an xlsx file is uploaded to a dataset in Amorphic with target of DWH then the file will be converted to csv to load the data into DWH because xlsx file cannot be loaded directly into DWH. Because of this conversion, files cannot be compared between source and target as the filetype and size changed between source and target.

Resolution: Keep the file names unique in the source folder and this issue will not be seen