Skip to main content

Qlik Replicate

Discussion board for collaboration on Qlik Replicate.

Announcements
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
jdhruva
Contributor II
Contributor II

How to handle data type conversion

Experts need your guidance here. We are migrating from Oracle to Snowflake using QLIK. Part of the replication process we noticed that columns with datatype Number(20,2) in Oracle is transformed into Number(22) in Snowflake using QLIK. Data after the decimal is truncated in snowflake after a full/CDC load. Can you please help us fix this issue? Is there is a setting we need to configure to handle this transformation?

Labels (2)
14 Replies
SwathiPulagam
Support
Support

Hi @jdhruva ,

 

The case 00051525 is related to parallel load issue which i am currently working on with you.

I will create a new case on behalf of you for this datatype conversion issue.

 

Thanks,

Swathi

jdhruva
Contributor II
Contributor II
Author

We are discussing with Swathi through QLIK support. We will update once we have a solution to this issue.

Heinvandenheuvel
Specialist
Specialist

Check your Oracle Source Endpoint - advanced settings - 

lyka
Support
Support

Hello,

Are you using logstream?  If yes, is the "Expose Number As" option  for both source endpoints configured the same?

Also, is the target table created by Replicate?

Thanks

Lyka

SwathiPulagam
Support
Support

Below is the solution we provided in the case :

 

Please refer to the Replicate user guide:

"
https://help.qlik.com/en-US/replicate/May2022/Content/Replicate/Main/Oracle/ora_source_data_types.ht...

NUMBER (P,S)

NUMBER according to the "Expose number as" property in the Qlik Replicate Oracle source database settings. "


NUMBER in oracle to Replicate handled as described in the document. There is no internal NUMBER datatype in replicate so we can't handle dynamic changes in the datatype as like Oracle. To Overcome this issue, we introduced "Expose number as" property in Oracle endpoint.


Ex: If NUMBER is defined with specific Precision and Scale on the source then replicate will create same NUMBER(P, S) on target.
If no Precision and Scale is defined on the source then as we explained replicate can't decide what would be the length. You have to review all your NUMBER columns and decide the best value for the "Expose number as" property.
If a different NUMBER column has to be defined with different Precision and Scale then it has to be set at table level transformation.


Please create a feature request with your use case. The product manager will review and prioritize the request.

 

Thanks,

Swathi