Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsConnecting to an Oracle database with OLEDB results in lots of trailing decimal zeroes.
This happens if the data type is defined as "number" in Oracle, without setting the precision and scale attributes.
Example:
CREATE TABLE "TIQ"."TEST_NUMBER"
("COLUMN1" NUMBER,
"COLUMN2" NUMBER(38,0) );
Insert into TIQ.TEST_NUMBER (COLUMN1,COLUMN2) values (1,2);
Insert into TIQ.TEST_NUMBER (COLUMN1,COLUMN2) values (3,4);
If you load this into QlikView via OLE DB x64 the COLUMN1 will have the issue, but COLUMN2 will not.
You can fix this either in the database by changing the column type, or in the query by using CAST(COLUMN1 as NUMBER(38)) or by using num#( ) function in QlikView.
If no precision and no scale are specified for an Oracle NUMBER column then it can contain arbitrary floating point numbers, and floating point numbers can be large.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us