topic network i/o error dbms in Data Management Questions

network i/o error dbms

tamerali — Mon, 27 May 2013 07:30:38 GMT

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

Re: network i/o error dbms

VinceAngelo — Tue, 28 May 2013 11:53:57 GMT

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/

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

Re: network i/o error dbms

tamerali — Sun, 02 Jun 2013 05:34:33 GMT

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

Re: network i/o error dbms

MarcoBoeringa — Sun, 02 Jun 2013 09:24:56 GMT

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...

Re: network i/o error dbms

VinceAngelo — Sun, 02 Jun 2013 12:17:04 GMT

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

Re: network i/o error dbms

tamerali — Tue, 04 Jun 2013 06:00:17 GMT

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 .

Re: network i/o error dbms

MarcoBoeringa — Tue, 04 Jun 2013 06:36:23 GMT

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.

Re: network i/o error dbms

tamerali — Tue, 04 Jun 2013 08:47:53 GMT

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

Re: network i/o error dbms

MarcoBoeringa — Tue, 04 Jun 2013 09:52:06 GMT

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

Re: network i/o error dbms

tamerali — Tue, 04 Jun 2013 10:00:10 GMT

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

Re: network i/o error dbms

VinceAngelo — Tue, 04 Jun 2013 10:14:32 GMT

If you had mentioned points in any of your previous posts, or had provided the
'sdelayer -o describe_long' output when requested, or had reported the output
of 'sdelayer -o feature_info' we would have been better able to help.

At this point, you'll probably be better off using Tech Support, since you're
dealing with configuration and/or corruption issues that are not easily solved
via these Forums.

Good luck.

- V

Re: network i/o error dbms

tamerali — Thu, 22 Aug 2013 10:30:46 GMT

Layer Configuration ..: DEFAULTS

Layer Description ....: <None>
Table Owner ..........: PROJECT
Table Name ...........: GIS_TRADE
Spatial Column .......: SHAPE
Layer Id .............: 21
SRID .................: 1
Minimum Shape Id .....: 1
Offset ...............:
falsex:   -5120900.000000
falsey:   -9998100.000000
System Units .........:      10000.000000
Z Offset..............:          0.000000
Z Units ..............:          1.000000
Measure Offset .......: <None>
Measure Units ........: <None>
XY Cluster Tolerance .:          0.001
Spatial Index ........:
parameter:    SPIDX_RTREE
exist:        Yes
array form:   -2,0,0
Layer Envelope .......:
minx:    357656.20280,        miny:   2888018.48770
maxx:    372293.78830,        maxy:   2897430.10350
Entities .............: npc
Layer Type ...........: In-Line Spatial Type
Creation Date ........: 08/18/13 14:36:08
I/O Mode .............: NORMAL
Autolocking ..........: Enabled
Precision.............: High
User Privileges ......: SELECT, UPDATE, INSERT, DELETE
Coordinate System ....: PROJCS["WGS_1984_UTM_Zone_38N",GEOGCS["GCS_WGS_1984",DAT
UM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich"
,0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAM
ETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Centra
l_Meridian",45.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin
",0.0],UNIT["Meter",1.0]]