network i/o error dbms

[tamerali]

plz i need u help , i have sde geodatabse for oracle , but i have problem in it , it containing 4 feature classes ,

it works good , but when i am add one of them (gis _trade feature class) , error occurred  when i zooming it or any thing

,other feature classes is ok , but when im add this layer  , they too have the same problem

the selected object failed to draw , network i/o error
i am sorry for my bad english
arcgis 9.3
arcsde 9.3
oracle 10g

[VinceAngelo]

Welcome to the Esri User Forums!  In order to get the best possible answer you need
to post a question with enough information for others to understand the problem --

• What *exact* version of ArcSDE and ArcGIS are you using (9.3.? SP?)


• What *exact* version of Oracle are you using (10.?.?.?)


• What geometry storage type are you using? (SDEBINARY/SDELOB/ST_GEOMETRY/

SDO_GEOMETRY)

• What does 'sdelayer -o describe_long' report on the layer?

Note that Oracle 10.2.0.1 is not supported with ArcGIS (10gR2 won't be supported by
Oracle in a few weeks, either, but 10.2.0.1 is known to be failure-prone).

- V

[tamerali]

Database: Oracle 11g R2
ArcSDE 9.3 Service Pack 2
ARCGIS 9.3 Service Pack 2
SDO_GEOMETRY

[MarcoBoeringa]

This really sounds like a geometry problem, with invalid geometries in the specific layer with problems, since you can access the other database layers normally.

ArcGIS includes two tools for dealing with that. The Help for 9.3.1 lists them here: Check Geometry and Repair Geometry.

However, I am not sure if they also exist at plain 9.3, or were introduced only at 9.3.1. If you can't find them, they were probably introduced at 9.3.1, and you need to run the ArcSDE Command Line tools instead. You can find more information on this in the document here:

http://resources.esri.com/help/9.3/geodatabase/pdf/admincmd.pdf

You probably need to use the "sdelayer" command. Vince can undoubtedly further guide you on the exact syntax to be used in your case if using the ArcSDE Command Line tools for checking the validity of the geometries.

Your alternative is using SQL*Plus and the SDO_GEOM.VALIDATE_LAYER command.

Be aware though, that what Oracle considers a valid geometry, isn't 100% compatible with what ArcSDE considers a valid geometry, there are a few minor idiosyncrasies between the systems. Nonetheless, checking will be useful as well.

To be 100% sure there aren't "ArcSDE invalid" shapes in the database, you really need to run the ArcGIS / ArcSDE tools though...

[VinceAngelo]

ArcGIS 9.3 did not have a Service Pack 2 release.  Oracle 11gR2 support
by ArcGIS was introduced at ArcSDE 9.3.1 SP2.  The reqested 'sdelayer'
output would have provided the actual software in use.

An invaild geometry is unlikely to produce an application server crash
(which is what the Network I/O error indicates), though you should
certainly confirm that all non-Esri geometries pass both Oracle and
Esri  geometry tests (see 'sdelayer -o feature_info').

Why did you state you were using Oracle 10g earlier, but 11g later?
You can't use a 10g client library on the ArcSDE server to reliably
communicate  with an 11gR2 database.

- V

[tamerali]

thank you for u reply , what did u mean about : you should
certainly confirm that all non-Esri geometries pass both Oracle and
Esri geometry tests .

[MarcoBoeringa]

thank you for u reply , what did u mean about : you should
certainly confirm that all non-Esri geometries pass both Oracle and
Esri geometry tests .

Vince means any geometries / features not initiallly created in ArcGIS. E.g. data created and maintained in AutoCAD and stored in SDO_Geometrry / Oracle Spatial.

This data may not confirm to ArcSDE standards for valid geometry, as it has not been created by ArcGIS. This is an often encountered cause of compatibility issues between ArcGIS and SDO_Geometry maintained by CAD or imported from CAD sources/drawings.

[tamerali]

thank you Marco  , how can i test this , i already have SE_ANNO_CAD_DATA field in my table .

[MarcoBoeringa]

Tamer,

I was not suggesting the fact that CAD maintained data is part of your geodatabase by itself is a problem.

The problem is that some features may have errors / be invalid, at least as considered by ArcGIS.

Think of a polygon with just two vertices to define its outer boundaries, you need a minimum of three vertices (a triangle) to enclose an area. Two vertices can only define a line... These geometries are INVALID and should not be in your dataset. Unfortunately, CAD datasets quite often contain problematic geometries, as the data may be less stricly maintained (no topology checks).

I already pointed out the tools you need to check if any geometrie is invalid in post no. 4 in this thread

[tamerali]

but my table is point layer , i don't know, it could possible invalid geometry ?