nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS 10.x Geodatabase with ArcGIS for Desktop 10.1 clients

Anonymous User

Hi,

We are keen to explore as part of our upgrade process some of the new 10.1 functionality, but due to system constraints at the back-end (namely gdb replication) we won't be in a position to migrate GDB quickly. That said, I'm keen to see some desktop users get early visibility to 10.1.

Are there any obvious issues that i could encounter with running a 10.1 desktop client with a 10.x back-end? During beta, i did notice sde connection files once opened with ArcGIS 10.1 made them un-useable by a 10.x client. Any insights as the 'new' functionality that will be lost due to dependencies on a 10.1 backend?

I'm also assuming gdb rep is 'not' backward compatible (such that a parent (or child) can be a mixture of 10.1 & 10 GDB's?)).

I'm reluctant to do any of the above but thought i would pose the question.

Brad

Trouver plus de publications taguées avec

Accepted answers

PaulKroseman

Just as an experiment, I created a 1 way replica between SDE database from 10.0 SP3 to 10.1 (child version is greater) and from 10.1 SDE to 10.0 SP3 (child version is lesser).
When child version is greater everything works normally.
When child version is lesser you must synchronize using 10.1 desktop client. Trying to synchronize using ArcCatalog 10.0 with the parent replica in 10.1 SDE gives error "Cannot open replica workspace <servername-servicename-dbname>. Please specify a valid workspace connection." I could successfully edit and synchronize using 10.1 desktop and view and edit using 10.0 desktop.

If your child replica is in a later release geodatabase (for instance, your child replica is in a 10 geodatabase, but your parent replica is in a 9.3 geodatabase), be sure you do not add data or make any edits that introduce functionality to the child replica that is not supported in the parent replica's geodatabase.

This is probably the most important part of the article. Nothing stopped me from creating the replica with 10.1 parent to 10.0 child because there is no 10.1 specific functionality on that feature class.

My test was quick with just create replica (1 way only), edit, and synchronize. I couldn't say that all replication features will work.

All comments

GaryMacDougall

Brad

Here is a link that describes replication and backward compatibility.

thanks
Gary

http://resources.arcgis.com/en/help/main/10.1/#/Replication_and_geodatabase_releases/003n000000z3000000/

Anonymous User

Gary,

Thanks for info re gdb rep. While the link highlights 'the child replica geodatabase must be the same geodatabase release as or a later release than the parent replica geodatabase', my question now is does this apply to the 10 releases. I have a 10 environment with 1-way replication on both sides (hence both are parents & both are children). If i apply 10.1 to one of these gdb's, based on the above statement, this scenario is not supported. Hence, are you able to confirm same rules apply for the 10 dot releases?

Regards

Brad

PaulKroseman

If your child replica is in a later release geodatabase (for instance, your child replica is in a 10 geodatabase, but your parent replica is in a 9.3 geodatabase), be sure you do not add data or make any edits that introduce functionality to the child replica that is not supported in the parent replica's geodatabase.

Anonymous User

Thanks for the insight - appreciate it.

Brad

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Se connecter
S'inscrire

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.