Solved! Go to Solution.
Unable to delete �??file geodatabase�?�,
But originally, why do I need to create replica?
Jamal
From the ESRI online help: "Geodatabase replication is built on top of the versioning environment"
Normally, you create a replica to distribute changes in a versioned featureclass from one geodatabase to another. Is the data in your primary File Geodatabases versioned?
If you are going to delete your FGDB that is a replica, you should probably delete the replica that points to that FGDB first.
Many thanks Leo for the help,
Do I need to restart the machine to be able to delete a file geodatabase?
What else I need to delete/stop to be able to delete the file geodatabase without the need to restart the machine?Were you the only one connected to it at the time, after stopping the web service?
1. If feature class added to the enterprise geodatabase then it is not added to the replica when synchronize
2. If a field is added to a feature class in the enterprise geodatabase then this field is not added to its feature class in the replica
But originally, why do I need to create replica?
I publish the data from the replica (file geodatabase) but not from the enterprise geodatabase to gain some performance. If the data is published directly from the enterprise geodatabase then accessing the published data (services) gets quite slow.
No
Were you the only one connected to it at the time, after stopping the web service?
I remember it happened to me at one time. I just deleted the tables from the database, not within arcCatalog, and then you can delete the geodatabase.
That is correct: there is a way to add other features to an exisiting replica, but the method escpes me. Personally, I create individual replicas for each feature class I replicate. It keeps things separate if the process goes south.
Correct again: That's actually a pretty cool feature of replication. The parent/child feature class can have different attributes and only share a set of core attributes. I manage an enterprise database of streets: each of the clients (various cities) have thier own specific needs and uses for the data. I use it for 9-1-1 dispatch. So I don't care what type of paint a city uses to to stripe the roads, or when that paint was applied. On the other hand, they have no need for for dispatch zones etc that I use. But, we all need address ranges, names, prefixes suffixes, typest etc.
Beats me. What are you trying to accomplish? I like to use one way replication for what you mention below. I only edit the parent/SDE feature class and then replicatate to a FGDB which is tapped for publishing.
I suggest you DELETE the published service and then try to delete the FGDB associated with it.
Many thanks Leo.
Let�??s assume that others were using services (that are reading the data from the replica/file geodatabase) at the time when I stopped them. Don�??t we have then a robust way to disconnect whatever related to this replica (file geodatabase) to be able to delete it?