Erroneous Versions on Instance

Discussion created by MCusumano on Mar 6, 2014
Latest reply on Mar 7, 2014 by vangelo-esristaff
Hey everyone, thought I'd throw this out there as everyone at our organization, including our vendors Schneider and IBM have no clue.

We went through an upgrade back in December from 9.1 to 10.1. Our three SDE databases are Land, Electric, and Gas. All run on Oracle platform.

Since the upgrade we have had erroneous versions pop up on our Land instance. They are usually called LAND_ELECTRIC, which are created on electric (normally). Other times they are labelled SN_xxx (ie SN_145) indicating they were created with ArcFM Session Manager (again, only used in electric instance). They are almost always dated November 13, 2013, even to this day (this date is from when we began a data freeze on database updates before the upgrade took place). Other times the versions have a current date (ie March 2014).

This morning our instance default version on land had a date of November 13, 2013 after a compress to state 0 last night by IBM. There is no custom code running in the compress, it is done using core functionality through ArcCatalog. However all of our updates since then are in place (meaning the database does not really reflect its state from November 2013).

If anybody could give us a lead to pursue it would be very much appreciated. Thanks.