Error opening feature class (which can be opened in another application)

[MartinEkstrand]

Hi!

We're using ArcGis 10.1 with ArcSDE 9.3.1 on Oracle 10g.

I've got 2 layers that cannot be opened or modified with ArcCatalog or ArcMap (but they show up in the list. Everything worked just fine until a few days ago when I added some columns from a third party software using SQL. As if this wasn't foolish enough (as it seems on Google) I also had an mxd open with these layers in it.

Now I cant open or use them in any ArcEnviroment of any kind (Also tried Topocad and FME, and on different computers, one of them has ArcGis 9.3.1... No go). Mostly I only get "Error opening feature class". Sometimes when I try to open the properties of the layers I get "Failed to edit the selected object(s). The workspace is not connected. Table attachments not supported in this release of the Geodatabase.". I've also gotten "Arcobjects error -2147216117 - Network I/O error".

The third party application however, can open and use them just fine, although it's reading from a view consisting of the data table + geometry table (the "F****"-tables) for each respective layer. With this in mind I've checked the database. Both the data tables and geometry tables exist with no errors and the connection between them is registered. I read somewhere on Google that the SDE.COLUMN_REGISTRY table could get out of sync when adding columns via SQL. So I checked it, but it's in sync. I also checked some metadata tables but could'nt see anything there (I don't really know what I'm looking for in there though).

My best guess is that the problem lies somewhere "between" ArcGis and the database, since the tables obviosly exists and is working in the third party application. There's no network error either since the rest of the database layers and tables can be used just fine. I'm guessing the problem lies in some kind of registry, metadata tables or cache, but I'm getting all out of ideas.

Anyone have any ideas?

Thanks for the help!

Martin

[VinceAngelo]

Is the table versioned?  Adding columns in the business table without also adding
them to the Adds (An) table could cause all manner of trouble.

The supported mechanism for adding columns to a versioned table is to reconcile
and post all edits, unversion, modifiy the table, then re-version, but you might
be able to just add the columns to the An table.  If that doesn't work, you may
need to roll back to the backup you took before making schema changes.

An SE_NET_FAILURE error usually means that you've caused the gsrvr process
to crash by violating geodatabase integrity (or exposing a bug, but I don't think
that's the case here), not that anything is wrong with the network.

If the simple fix doesn't work, then you'll probably want to work with Tech Support
to get your geodatabase functional again.

- V

[MartinEkstrand]

Hi!

Thanks for answering!

No, it's not versioned. I forgot to mention that. I also forgot to mention we tried a server reboot, with no effect. I have also added columns from the third party software before without problems. All the other tables and feature classes in the database is working with no errors at all. The only ones not working are those 2 feature classes I added columns to.

I guess I'll try tech support.

/Martin

[VinceAngelo]

What columns did you add?  Are the datatypes supported by ArcSDE and ArcGIS?  What do
DESCRIBE {table} at the SQL*Plus prompt and 'sdetable -o describe -t {table}' report?

- V

[MartinEkstrand]

Do you ask for the column names?

On the table PUNKT_SDE I added MARKNAR (number), MARKNKV (number), LOCKNKV (varchar2) and LOCKNAR (varchar2).

On the table LEDNING_SDE I added ANLARKV (number), NMTKV (varchar2), NMF (number), NMFKV (nvarchar2), NMT (number), NMTKV (nvarchar2) and RORGRAV (varchar2)

All the other columns of the table uses the same datatypes so that shouldn't be a problem? It's probably worth noting that after we noticed that the tables didn't work, I removed the columns from PUNKT_SDE using the same third party software to see if that would work (perhaps I shouldn't have done that either?). So now only the table LEDNING_SDE has the new columns.

I've attached two .txt-files with the info from sql*plus and cmd.

/Martin