07-12-2016 05:20 AM
Hello everybody !
I am wondering which version of Oracle client must be installed on desktop to satisfy "Features Database output" - Select Data source (for Oracle). I have installed Oracle client 11G R2 32-bit with Administrator option (required for Geomedia) and "Features Database output" -Select Data source throws error " Could not load file or assembly .Version 220.127.116.11....the system can not find the file specified ".
Would it be necessary for Spatial model editor to install 64 bit Oracle client or the Oracle 12c client?
07-12-2016 07:36 AM
Oracle12c Client is required to make this work. Please follow the below installation procedure
07-13-2016 02:28 AM
Thanks for answer!
The Oracle client installation procedure described abowe allows me to create Oracle Feature Proxy file (*.ofp) in Imagine 2016 and to add in Imagine Map window the vector layer from Oracle data source. It works fine.
But Standalone Spatial Editor 2016 ->add Features Database Output operator, click on Output Database port and then " Add Oracle" -> " Use Oracle Database authentification" -> adding the same Oracle credentials as before for Imagine *.ofp calls different error now "Object Reference not set to an instance of an object".
My intent is to output vector features into Oracle DB from standalone Spatial editor.
08-09-2016 09:22 PM
Sorry for the delayed response and we apologize for the inconvenience that you are facing while using the functionality. Unfortunately this is a known issue and we are actively working on it.
08-13-2016 05:08 PM
Out of curiosity, are your ORACLE database and client versions in sync?
I recall having trouble connecting to Oracle Spatial from desktop CAD/GIS, which resolved upon using synced client and database versions, e.g., use the 64-bit 11g client with the 64-bit 11g database, and so on. In my case, AutoCAD or ArcGIS (I forget which) wouldn't work using a 64-bit 11g client on a Windows7 box to talk to a 32-bit ORACLE 10g database on Windows Server 2003.
08-15-2016 03:44 AM
Now I have 3 (!) Oracle client installations on the same computer . And the server is 64-bit Oracle 11G R2 on Windows server 2012.
The reason is simple: according to instructions in thread above I installed two Oracle instant clients 32 bit and 64 bit for Imagine 2016. I believe the two clients (32 and 64 bit ) for Imagine is mandatory because part of Imagine code is still 32 bit?
And I did separate 32 bit Oracle 12c client installation with " Administrator" option for Geomedia 2016. I want to run both products - Imagine and Geomedia on same computer and run spatial models from "Spatial model Editor" standalone .
I believe is is intended workflow for vector feature interoperability between Geomedia and Imagine (via relational database not only ESRI shape) .
After deinstallation of Oracle 11G 32 bit client (with Administration option, size 1.02 GB) and installation of Oracle 12c 32 bit client (with Administration option) the behaviour of "Features Database Output" is changed. No more error " "Object Reference not set to an instance of an object". But Oracle table is always empty. I discovered what " Features Database Output" operator populates only Oracle SDOSYS table but not GDOSYS (necessary for Geomedia).
Would be great to recieve new hotfix for " Features Database Output" operator with full instructions how to deal with situation - both Geomedia desktop and Imagine is installed on 64 -bit Windows (but Geomedia of course is 32 bit) . As well as SQLserver client configuration too.
08-15-2016 07:32 AM
It's been about 6 years since I last used GeoMedia so this might be outdated info, but I recall there was a utility that shipped with GeoMedia that set up the GDOSYS schema, which only contained metadata for your spatial data stored in some other schema (in your case, that appears to be SDOSYS). It was a small utility that only had 5 or so buttons arranged in one column. If you find that, maybe you could unregister and reregister your data tables.
I suppose the multiple clients not be a problem so long as each software is using the client it's happy with, but that's the part that gave me headaches.
08-17-2016 11:05 PM
The behavior you've described for Features Database Output operator occurs if you use mixed or lower case characters for the value on port OutputTableName. Table names need to be upper case to be correctly recorded in the GDOSYS metadata tables. We're working on a fix to ensure that the value on the OutputTableName is converted to upper case before being used to create the output table.