Sychronization of a SDE feature class and SDE table

[JoJoMekkattil]

I have been trying to figure this out for two weeks now and I'm getting no where. I am new to this technology so if you do not understand something I will try to explain further. Here is my situation:

First I have two SDE feature classes called CIP.structure_exisiting_area and CIP.VIEW_ADDRESS_QUERY. I also have a SDE table called CIP.FACADDRESS.

I had a user add and removed some buildings from the SDE database and I was to "create_view" in the oracle database for the Buildings Address layer which is shown on a viewer called ims_viewer.

To delete the view I ran the following command:
sdetable -o delete -t view_address_query -i ESRI_SDE -s nvzrgeobase2 -D GIO -u *** �??p ******

It replied back if I was sure I wanted to delete the table view_address_query to which I replied Y and it deleted it.

Then I ran the next command:
sdetable -o create_view -T view_address_query �??t CIP.STRUCTURE_EXISTING_AREA,CIP.FACADDRESS �??c CIP.STRUCTURE_EXISTING_AREA.buildng_id,CIP.STRUCTURE_EXISTING_AREA.shape,CIP.FACADDRESS.SEQNBR,CIP.FACADDRESS.FAC_NBR,CIP.FACADDRESS.ADDRESS,CIP.FACADDRESS.ZIP -w "CIP.STRUCTURE_EXISTING_AREA.buildng_id = CIP.FACADDRESS.FAC_NBR" -u *** -p ********

And states that the view view_address_query was successfully created.  Finally, I grant select access to the ims_viewer through ArcCatalog.  However, when I go to my CIP.VIEW_ADDRESS_QUERY feature class I notice that a building that is suppose to be gone is still there.

What am I doing wrong? Any help would be greatly appreciated.

[JonDeRose]

I realize that this is an old post but wanted to respond in case this may help someone else encountering similar behavior.

From the description it sounds as though an edit (delete) which was made and reconciled/posted to the default has not been compressed.  As a result the spatial view has not been updated with this delete and it would still be visible when the view was accessed.

It is important to note that a spatial view is created on the business/base tables of a feature class. Even if the default version (sde.DEFAULT) is edited, the edits are stored within the delta (A and D) tables and the view will not reference these until they are reflected within the base. If you were to compress the geodatabase the edits will be moved to the business table and should then be reflected within the view.