The Esri Community
Services & Programs
GeoNet Resource Hub
to create and rate content, and to follow, bookmark, and share content with other members.
Will Upgrading to 10.2 Cause Geodatabase Problems?
Discussion created by
on Oct 22, 2013
on Dec 14, 2013 by crafty762
Show 0 Likes
Our users are currently at 10.0. We have a personal SDE geodatabase with checkout replicas. Will upgrading to 10.2 cause problems with replicas or access to the parent GDB?
This content has been marked as final.
Show 2 comments
(Required, will not be published)
Oct 22, 2013 11:18 AM
You can refer
Replication and geodatabase releases
Show 0 Likes
Dec 14, 2013 3:56 AM
Upgrading geodatabases can be painful; you should always first perform this in a test environment using a fresh copy of your production data. The Upgrade Geodatabase tool from 10.1, 10.1 SP1, and 10.2 behaves strangely at times, and often times you won't know if the upgrade will fail until you actually perform it for real. Running the Prerequisite Check can be helpful to find some issues, but it won't catch everything. I've not found issues with my data or with my object classes until I actually attempt the upgrade itself.
You DON'T want to do this in production only to find out that the upgrade fails and can't complete successfully.
When that happens, my experience is that many of the database changes made by the upgrade tool prior to the failure (which usually occurs at the very end, conveniently) are not reversed. Therefore, your database will "think" it's been upgraded to a certain extent and your clients have have major issues connecting. Even the SDE.VERSION table shows an updated release and build number despite the upgrade failing.
So, to me, the decision on whether or not you should upgrade to 10.2 might be a two-part set of questions:
(1) from a software standpoint, can I upgrade? do I have the right desktop and server software components in place? As an example, 9.3.1 clients won't be able to connect to your geodatabase if you're upgrading to 10.2 from 9.3.1. I know you said your clients are 10.0, but these are the kinds of things to think about across your entire environment. Keep client connectivity requirements and geodatabase system requirements in mind before making the decision.
(2) will my geodatabase actually
an upgrade successfully (which is best vetted in a test environment to find all of the potential pitfalls)?
Now, in terms of your replicas, I would recommend that you drop the replicas and rebuild them once the upgrade is complete. You may even be forced to by the software. If you are required to clean up some of your data prior to the upgrade (believe me, I've seen this many times... a 10.0 instance of SDE allows certain geometry issues but 10.2 is much more picky), then altering the data may be reason enough to have to drop and rebuild the replicas. Dropping the replicas needs to be done as the replica owner; otherwise you'll have "orphaned" versions that can only be deleted using SDE command line. Also, before making the upgrade your safe bet is to take your geodatabase to State 0 if there are versioned object classes. This is my suggestion after having done this many, many times in the past. If you're not familiar with how to achieve State 0, I suggest reading about it online and understanding how Compress works.
Show 0 Likes
Retrieving data ...
Hedonic pricing using geostatistical
Upgrade step 2 of 2 : Failed. Refresh auto-deployed services during upgrade
Beta release of 3D Flood Impact solution
Survey123 Inbox not returning data value from service
Survey123 – allow a survey to open the 'Inbox' menu by default instead of the 'Collect' menu, when a survey is launched from another application with the 'arcgis-survey123://?itemID=' Custom URL Scheme