Skip to main content
Version: v3.0 print this page

Datasources

Note: Oracle source

Datasource 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.

S3 Datasource​

2. Ingestion failure for duplicate file names in source folder​

Issue Description: If the source folder contains multiple files with the same name (in subfolders), only one file will be ingested into the target.

Explanation: This occurs when the file type is XLSX and the target is a Data Warehouse (Aurora MySQL / Redshift).

  • When an XLSX file is uploaded to a dataset in Amorphic with DWH as the target, the file is converted to CSV before loading.
  • Since XLSX files cannot be loaded directly into DWH, this conversion changes the file type and size.
  • As a result, the system cannot compare source and target files correctly.

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

Generic Issues​

  • When a datasource flow is created with Target Location as S3 and includes a transformation rule to remove a column, data distortion occurs in the CSV files stored in S3.
  • This issue is due to a bug on AWS's end and is not related to Amorphic.
  • AWS has not provided an ETA for fixing this issue. Once AWS resolves it, the fix will automatically reflect in Amorphic.