AnsweredAssumed Answered

9.3.1 to 10.4.1 Upgrade - Versioned editing failing.

Question asked by Jeremy.Clark on Nov 29, 2016
Latest reply on Nov 30, 2016 by Jeremy.Clark

Hi,

 

I'm currently attempting to complete a version upgrade of a SDE database on a MSSQL server and while the core database and feature classes upgrade successfully, when attempting to re-implement versioned editing the edits are failing to save.

 

      The source database is from version 9.3.1, SQL server 2008 is the database engine.

      The target database will be version 10.4.1, SQL server 2012 (SP3) is the database engine.

 

The error message we are receiving when attempting to save edits is as follows:

 

The following scenario successfully edits data within this database:

  • Upgrade the database 9.3.1 -> 10.4.1 (including restored users etc), connect as a database user, use the sde.DEFAULT version, edit directly into default (SUCCESS)

 

We have tried multiple variations to upgrade the database including:

  • Compress the database and clean up all states/versions, upgrade the database 9.3.1 -> 10.4.1 (including restored users etc), recreate versions (), use the newly created version (eg. GISDADMIN.WGIS_Edits_Spaceuser) 
  • Upgrade the database 9.3.1 -> 10.4.1 (including restored users etc), compress the database, recreate versions (no versions show up from 9.3.1), use the newly created version (eg. GISDADMIN.WGIS_Edits_Spaceuser) 
  • Upgrade the database 9.3.1 -> 10.3.1 (including restored users etc), compress the database and clean up all states/versions (including orphaned), upgrade 10.3.1 -> 10.4.1 , compress the database, recreate versions, use the newly created version (eg. GISDADMIN.WGIS_Edits_Spaceuser)

 

This appears to occur regardless of version naming and the user creating the version.  

 

Has anyone run into these issues before with upgrading an SDE database from 9.3.1 to 10.x?  Appreciate any suggestions for resolving this short of rebuilding the entire database!

 

Thanks,

 

Jeremy.

Outcomes