Unsupported Autodesk FDO Provider to Oracle with XE – works…er..

Ok, I managed to get Autodesk FDO Provider for Oracle working with Autodesk MapGuide Enterprise 2009 with Oracle XE.  The trick was simple.

Just make sure that the SCHEMA, the USERS, the TABLES and all the COLUMNS are in upper case.  That’s it.  I was stuggling with theming, connecting, etc with Oracle XE and Autodesk FDO Provider for Oracle.  I had reverted to the SL-KING Provider for Oracle (due to the fact that the Autodesk FDO Provider for Oracle does not offically supports XE and I couldn’t get it working).

So I created a new users, loaded it up with tables, including a geometry column called GEOMCOL all in upper case, added an entry to the SDO_GEOM_METADATA table, a spatial Index, and voila! I have the Autodesk FDO Provider for Oracle working “tickety-boo” with XE. 

Yay!

One Response to “Unsupported Autodesk FDO Provider to Oracle with XE – works…er..”

  1. Gord

    This is a pretty common problem. There are a lot of Oracle schemas that have been created from other systems (MS Access is the worst offender) where mixed or lower case has been used when the table was created.

    Oracle will double quote these tables so any SQL must include the quotes which is a pain – select * from mytable will fail. select * from “mytable” works.

    I had one large and complex database that was generated from a personal geodatabase that was full of this context. The work around – create views of all of the tables using uppercase table names and everything worked fine

Leave a Reply