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; } } }

__ATTACH tables break replication in ArcGIS 10?

MichaelWolfe

I originally posted this question on gis.stackexchange.com.

I'm trying to get one-way replication working in ESRI ArcGIS 10. Here's a quick summary of the steps I followed:

Open map in ArcMap with the relevant data layers I want to replicate
Choose Create Replica from distribution toolbar
Choose One-Way Replica, Parent-to-Child
Use Simple Model (as opposed to Full Model)

This works for me with one problem. Several of the featuresets that the data layers are based off of have __ATTACH tables. When I perform the replication, the __ATTACH tables get replicated but the base tables do not.

For example, there is a layer based on a featureset called Parcels that may have attachments stored in a SQL Server table called Parcels_ATTACH. In the replicated copy of the geodatabase, there is a Parcels_ATTACH table but no Parcels table.

If it makes any difference, the Parent Geodatabase is stored in SQL Server 2008 R2 and the replicated child is stored in SQL Server Express 2008 R2.

タグ付けされた投稿をもっと見る

Accepted answers

JakeSkinner

You can replicate between SQL Server and SQL Server Express. I believe the problem is with the data. As a test, try the following:

1. Create a new feature class in SQL Server
2. Register the feature class as versioned
3. Add Global IDs
4. Enable Attachments
5. Add the feature class to ArcMap and create the replica to the SQL Server Express database using the Create Replica wizard
[INDENT]a. Be sure to select Advanced and select Full Model
b. Specify 'All records' for the attachments table
[/INDENT]
6. Complete the wizard

Is the attachments table replicated successfully?

All comments

NanaDei

🙂 - I was checking whether the parcel data being replicated was a 'parcel fabric', as replicating parcel fabrics is not supported pre-10.1. Since the replica creation succeeded at version 10.0, I don't think a parcel fabric was involved. Thanks for the information.

MichaelWolfe

ESRI ArcMap 10.0 (Build 3600)
ArcGIS Desktop 10 Service Pack 3 (Build 3600)
License Type: ArcInfo

I hope that helps. I'm not really a GIS guy. I'm a software developer that occasionally has to help maintain an existing system set up by someone who has since been let go and not replaced. I know just enough to be dangerous

DSC_1400.JPG

NanaDei

Since you've been able to create the replica, this suggests that all feature classes/tables in the parent geodatabase has GlobalIDs and they are registered as versioned. Layers that are not versioned and/or do not have Globalids are not included in the replica.

I also wanted to check if the data being replicated is a Cadastral (Parcel) Fabric and which version of ArcGIS Desktop version (10.0 or 10.1) is being used to create the replica.

Thanks

MichaelWolfe

I think you're right. I tried creating a Full Model replica with a subset of the data I need and it seemed to go through OK. Now I just have to systematically add in the features I need and see what is specifically causing the "application not licensed" error.

Thanks for your help.

JakeSkinner

MichaelWolfe

If I choose Full Model with the personal geodatabase I still receive an error similar to the one I received before:

The application is not licensed to create or modify schema for this type of data

I believe this is because our source geodatabase uses SDE schemas (on a full version of SQL Server). The source geodatabase should have all necessary licenses to do just about anything. However, the target geodatabase will need to run on laptops that only have ArcMap viewing licenses and no full-copy of SQL Server (only express).

JakeSkinner

Try replicating to a personal geodatabase using Full Model. You should not be receiving that error when you choose 'Full Model'.

MichaelWolfe

This is still an issue for me. I tried replicating to a personal geodatabase instead of SQL Server Express. I get the same problem with the __ATTACH tables. Is there any way to explicitly specify what layers should be included in the replica?

MichaelWolfe

If I try to run the Full Model I receive the following error message:

---------------------------
Source Data Error
---------------------------
The application is not licensed to create or modify schema for this type of data
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
A network source with the specified name does not exist.
Version not found [DBO.AssessMap06_92]
---------------------------
OK
---------------------------

I believe this is the relevant line from the above error message: "The application is not licensed to create or modify schema for this type of data "

The parent geodatabase is on a full SQL Server installation and it uses SDE schemas. I assumed that a Full replica maintains the SDE schema, which is apparently incompatible with SQL Server Express. I figured this meant the Simple replica was my only option because SQL Server Express is a hard req't on the destination/child geodatabase machine.

JakeSkinner

I'm not sure why the feature class is being dropped, but is there a reason you are choosing 'Simple Model' rather than 'Full Model'? For example, do you need the child replica not to be versioned in the SQL Server Express instance?

If you choose 'Full Model' both the feature class, attachments table, and the associated relationship class will be replicated. Here is more information on feature information models for replicas.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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