Hi Mark, An iODBC Driver Manager trace would be useful to have to see where the fails are occurring with the EasySoft ODBC driver. We have not performed any testing of Virtuoso with the EasySoft ODBC driver and thus would recommend the use of the OpenLink Multi-Tier ODBC Drivers, which have been extensively tested with the Virtuoso.
The Virtuoso Virtual Database Engine, attempt to use the rich metadata available in ODBC to dynamically determine the mappings of remote Database types to Virtuoso equivalents, but we would need to see specifically what ODBC calls are failing to comment on what type cannot be mapped below. For point 1 below you could use replication to attempt to replicate the tables from Oracle to Virtuoso, but given it uses the the VDB layer will probably encounter similar issues. For Point 2 their is no means of manually choosing the type the VDB maps datatypes into Virtuoso it is all done dynamically. For point 3 you could create views in Oracle with the columns in the tables you want to be linked into Virtuoso as views and procedures can be linked into Virtuoso also. Generally you would be best to use the OpenLink Multi-Tier ODBC Driver as suggested in the support case you logged. Best Regards Hugh Williams Professional Services OpenLink Software Web: http://www.openlinksw.com Support: http://support.openlinksw.com Forums: http://boards.openlinksw.com/support Twitter: http://twitter.com/OpenLink On 25 May 2010, at 03:33, Mark James wrote: > Hi, > I'm trying to load a number of oracle tables as a virtual tables. These > tables contain complex datatypes within certain columns. > > Eg - > CREATE or REPLACE TYPE "CUST_ADDRESS_TYP" > as object > (streed_address varhar2(40), > postal_code varchar2(10), > city varhar2(30), > state_province varchar2(10), > country_id char(2) > ); > > or > create or replace type "phone_list_type" as varray(5) OF varchar2(25); > > > When trying to load these tables I get the error - > OE.CUSTOMERS HY000 VD052: Remote DSN ORACLE_OE: > [Easysoft][Oracle]Unable to map datatype( 108 ) for column ( 4 ) > > Is there a way to either - > Map these objects directly into objects within virtuoso > Map these objects by exploding them into standard data types within virtuoso > Simply exclude these columns from the table import > None of these options seemed to be available within conductor. > > Cheers > Mark > ------------------------------------------------------------------------------ > > _______________________________________________ > Virtuoso-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
