Typically, you don't need to worry about lock files in the geobatabase. A file GDB can only have one person editing a dataset at a time – so there will be one of these per featureclass/table. lock files - If someone has started the ArcMap Editor there will be an edit. These can generally be deleted without consequence.
lock file per layer per computer per ArcMap session that has the layer open. Adding a layer to ArcMap will create one of these locks. lock files - These indicate someone is ‘reading’ the data. The name of the file identifies which geologists/computers are accessing the geodatabase: _gdb.sr.lock where PID is the process ID on the computer locking the dataset use Task Manager (on the named computer) to investigate. There is one schema lock for every computer accessing the GDB. This prevents the schema (featureclass and table definitions) from changing outside of your session. lock file - When someone is using the GDB, a schema lock is added. lock files in a file geodatabase that track different things. It does this by placing *.lock files in the file geodatabase folder each time a process accesses a dataset. Read more about this from Esri support: FAQ: Can multiple users edit a file geodatabase at the same time? However the way Player map documents are structured, as soon as one geologist starts editing the Player geodatabase, all others are locked out.ĪrcGIS ensures "data integrity" (only one editor) by preventing multiple processes from simultaneously accessing data in conflicting ways.
So one person could be editing a table, another person editing a feature class and the third the feature classes within a feature dataset without experiencing issues. Esri say “ a file geodatabase supports many readers or one writer per feature dataset, stand-alone feature class, or table ”. It is the standard container for Esri data (replacing shapefiles).įile geodatabases are essentially single user. GDB at the end of the name - that contains a collection of files that can store, query and manage spatial data (wells, field, CRS.) as well as nonspatial data (tables of rows and columns). The Player database is typically managed with an Esri file geodatabase. Modified on: Tue, 16 Jun, 2020 at 4:24 PMĪpplies to: Player 5.0 for ArcGIS Pro, Player 4.4 for ArcMap, Player 4.3 Solution home Helpdesk Supporting Player Lock files in an Esri file geodatabase