Community
Select to view content in your preferred language

Create Inspire View Service with Oracle needs ST_GEOMETRY instead of SDELOB

490
1
10-07-2011 08:28 AM
ChristineWhite
by
Occasional Contributor
‎10-07-2011 08:28 AM
Environment: ArcGIS 10.0 SP 2, ArcGIS for INSPIRE 1.0 SP 1 on Windows 2008 R2 and
ORACLE 11g R1 64bit on LINUX.

The geodatabase was set up with the default geometry storage (SDELOB) and the Geodatabase XML-Workspace document was imported without issue. There was no problem using Add Inspire Layer to create the MXD, but if the service is created and started with Inspire View-Capabilities it fails with following error:

...Unknown exception of type: The GEOMETRY_STORAGE type 'SDELOB' is not supported. Please check your dbtune settings! ... Server Object instance creation failed on machine...

If the GEOMETRY_STORAGE type in dbtune is set to ST_GEOMETRY, then the service can be created and started without errors.

ArcGIS for INSPIRE installation documentation should be updated for Oracle.
Tags (2)
0 Kudos
1 Reply
andrejtrunkl
by
Deactivated User
‎10-23-2012 11:32 AM
Environment: ArcGIS 10.0 SP 2, ArcGIS for INSPIRE 1.0 SP 1 on Windows 2008 R2 and
ORACLE 11g R1 64bit on LINUX.

The geodatabase was set up with the default geometry storage (SDELOB) and the Geodatabase XML-Workspace document was imported without issue. There was no problem using Add Inspire Layer to create the MXD, but if the service is created and started with Inspire View-Capabilities it fails with following error:

...Unknown exception of type: The GEOMETRY_STORAGE type 'SDELOB' is not supported. Please check your dbtune settings! ... Server Object instance creation failed on machine...

If the GEOMETRY_STORAGE type in dbtune is set to ST_GEOMETRY, then the service can be created and started without errors.

ArcGIS for INSPIRE installation documentation should be updated for Oracle.


we have experianced the same problem, the only thing to add to this post, is that if the Geometry field is SDELOB then the inspire featureclasses are not visible in ArcMap nor in ArcCatalog.

So It is a potential bug situation
0 Kudos