Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello all,
I'm still new to Qlik replica product “Attunity” and was looking for support on a unexpected decimal truncation that occurs after the data is loaded at the target database.
We pull data from and Oracle database where the column that we are facing an issue with is a decimal (18,2) ex:[35.25] and it shows in the correct format in the Oracle source table.
we built a task in attunity to replicate to a target database “Snowflake” and the result seems to truncate the two decimal points ex:[35.00] for all values.
We are currently running on a 2021.5. version. this was not an issue in the previous version that we had. Can I please get some guidance on how to solve this issue?
So what is the datatype on target, can you 'describe' the table there?
How was the target table created? Was Replicate allowed to (drop and) create?
Maybe there is something in the task or endpoint json. Can you share that (remove excess explicit tables)
When you 'manually' - outside Replicate - store a row with decimal value into the Snowflake target table, how does it look like coming back on a select?
hth,
Hein
Hi Hein,
Thank you for response.
So what is the datatype on target, can you 'describe' the table there?
How was the target table created? Was Replicate allowed to (drop and) create?
Maybe there is something in the task or endpoint json. Can you share that (remove excess explicit tables)
When you 'manually' - outside Replicate - store a row with decimal value into the Snowflake target table, how does it look like coming back on a select?
Regards,
Ayman
1. could you check what is your oracle endpoint / advanced tab / Expose NUMBER as: what is this set for ?
2. if you change the Expose NUMBER as: to varchar, and reload the table, what is the value , on the target ?