![]() |
Geodatabase releases and geodatabase replication (ArcInfo and ArcEditor only) |
|
| Release 9.3 | ![]() ![]() ![]() |
NOTE: When editing the child replica, make sure you don't introduce edits that aren't supported in the parent replica's geodatabase. For example, annotation classes were introduced in version 9 and, therefore, are not supported in 8.3.
NOTE: If you upgrade the parent replica's geodatabase, you will also need to upgrade the child replica's geodatabase before synchronizing. For example, consider the case where you create a checkout replica using an 9.2 geodatabase to host both the parent and the child. If you then upgrade the parent's geodatabase to 9.3, you will need to upgrade the child's geodatabase before synchronizing. If synchronizing using a delta file, you will need to upgrade the child's geodatabase and then reexport the delta file.
NOTE: There is one exception to these rules. If the parent replica's data is stored in high precision in a 9.2 or greater geodatabase, you can't create a checkout replica using a low-precision 9.2 or greater geodatabase for the child.
Additional requirements for two-way and one-way replicas Two-way and one-way replicas were introduced with ArcGIS 9.2 and require a 9.2 or greater geodatabase for both the parent and child replicas although, as stated above, the child replica geodatabase must have the same geodatabase release or greater than the parent replica geodatabase. If you have ArcGIS 9.3 or ArcGIS 9.2 SP5, you can create two-way and one-way replicas as long as the geodatabases are 9.2 or greater.