I have testing SQLAnywhere12(3457) & 16(1324) by Windows 7 Build 7601 Service Pack 1 on X86_64 I am connecting Oracle10g & Oracle11g by ODBC
I am able to create Remote Server & Proxy tables and read data from proxy table. but problem is if I put condition to retrieve data, database die while I am using SQLAnywhere12(3840) & 16(1324) but if I use SQLAnywhere12(3457) I don't encounter this problem
CREATE EXISTING TABLE "DBA"."INWARD"( "OWNER_CODE" VARCHAR(12) NOT NULL, "ASN_NO" DECIMAL(8,0) NOT NULL, "WHS_CODE" VARCHAR(8) NOT NULL, "ASN_DATE" TIMESTAMP NULL, "ETA_DATE" TIMESTAMP NULL, "PO_NO" VARCHAR(24) NULL, "STATUS_CODE" VARCHAR(1) NOT NULL) AT 'wms;;WMS_DATA;INWARD';
I'm sorry. I just tried a few simple tests but failed to reproduce the problem that you are seeing. Could you please provide a full repro including information on exactly what statement was used to create the table in Oracle. We do not need the exact data, but the Oracle schema/definition may be important here.
Another thing we need to know is which Oracle driver are you using? Are you using the iAnywhere Oracle ODBC Driver or one provided by Microsoft or some other vendor? Keep in mind that the server will crash if the underlying driver crashes so this may be a driver bug not a server bug. The fact that you did not see the problem with build 3457 could simply be due to the fact that we have made many fixes in the Remote Data Access layer to ensure VARCHAR2 data gets handled correctly. Maybe the driver does not handle that very well. If you are not using the iAnywhere Oracle ODBC Driver, then it might be worthwhile to switch to the iAnywhere driver and see if that resolves the issue.
Either way, we need this extra information before we can proceed.
answered 07 Mar '13, 13:49
I had some problems in regard to numeric columns with Oracle. Can you try to use a integer for ASN_NO ? Does this make a difference ? Only a guess.
answered 07 Mar '13, 05:17