use 'OLEDB CONNECT 64bit oracle happen 1 change 1.00000000000000000000000000000000000

[#1]

When I user ''OLEDB CONNECT TO [Provider=OraOLEDB.Oracle.1;User ID=fbi_dw;Data Source=mic133] (XPassword is DORLQTRMITccWcBHBDZOXGC);'' to connect oracle .I reload again ,my date has someting error. how to solve it

[#2]

yes，it is。

[#3]

Did anyone find a workaround for this yet? I am also having this issue for oracle oledb connections.

[rbecher]

Would like to help but, would need more information about the case.

Again, is this causing by querying Oracle Views?

[#5]

My issue is when using datatype Number with precision 38 and scale 0.

No views just regular tables

Thanks!.

[rbecher]

Hi all,

finally I did some researches on this issue. This happens if the column type is defined as number in Oracle, without precision and scale. I created an 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);

Now, 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 NUMER(38)) or by using num#( ) function in QlikView (see attached QVW file).

- Ralf

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.