I have multiple processes that should access different resources (different names) in the same file geodatabase. When running the code, I obtain the following error message:
Cannot acquire a lock. [The table GDB_SystemCatalog is being written by another process.]
Does anybody know if there is a limitation to one "editor" (for the geodatabase, not for resources) at a time for file geodatabases and how it is managed by users who don't want to use SDE?
As these processes are not continuously created and running (but created once each time I have to perform a specific heavy computation that I am slicing and distributing on my eight cores), it is not a big deal for me to dynamically create as many file geodatabases as there are processes, but I would be happy to have more information before going this way.
Does anybody know if there is a limitation to one "editor" (for the geodatabase, not for resources) at a time for file geodatabases and how it is managed by users who don't want to use SDE?
A File Geodatabase is not limited to one editor per file geodatabase. It's limited to one editor per dataset (feature class, table, feature dataset). If any files in a feature dataset are being edited, all files in the feature dataset are locked.
