topic Re: postgresql error in Data Management Questions

postgresql error

TateM — Mon, 03 Mar 2014 18:20:59 GMT

hello all, I have an error and looking for some guidance to resolve this error.

I'm using Add Query Layer to pulling a Query Feature Class from an PostgreSQL spatial database. And when I open up the attribute table to view all the records it gave me an error.

"Error reading OID from table. Reading rows has been stopped. Check that the datasource is valid. Linestring or poly boundary is self-intersecting".

I found a knowledge base article http://support.esri.com/zh-cn/knowledgebase/techarticles/detail/40896 , but I'm not really sure what to make of this.

Please any help or directions would be greatly appreciated. TIA.

Re: postgresql error

AsrujitSengupta — Mon, 03 Mar 2014 20:30:49 GMT

Copy that Feature Class to a File gdb and run 'Check geometry" tool on that. It should list all the features with invalid geometries.
Then you can either go through the features reported in this and correct them OR run the "Repair Geometry" tool, which will repair these. Then copy this corrected FC back into the postgreSQL database and try again.

However I would suggest you read about these tools a bit before executing them!

Checking and repairing geometries:
http://resources.arcgis.com/en/help/main/10.1/index.html#//001700000042000000

Check Geometry (Data Management):
http://resources.arcgis.com/en/help/main/10.1/index.html#//001700000034000000

Repair Geometry (Data Management):
http://resources.arcgis.com/en/help/main/10.1/index.html#//00170000003v000000

Re: postgresql error

TateM — Tue, 11 Mar 2014 22:13:27 GMT

Thanks Asrujit.

Is there anyway in ArcMap that we can tell it to IGNORE the error and keep on drawing or displaying it? Because other layers who have the same error works fine(displaying/drawing) with the only exception is that these layers have less record/rows than the one that broke down and gave the error.