Removing connections from a geodatabase in Informix
This topic applies to ArcGIS for Desktop Standard and ArcGIS for Desktop Advanced only.
The geodatabase administrator can disconnect users from a geodatabase in Informix from the Connections tab on the Administer Geodatabase dialog box in ArcGIS for Desktop.
A user may need to be disconnected for a number of reasons. For example, he or she might be holding a lock on an object, preventing another editor from accessing it. In situations where there are a limited number of connections that can be made to a geodatabase, an administrator might also need to disconnect a user to free up a connection for another user.
To disconnect users from the geodatabase, the geodatabase administrator must be granted CONNECT privileges on the sysadmin database.
It is not recommended that you disconnect active connections. This is especially true if the connected user is in the process of editing.
Follow these steps to disconnect users from the geodatabase:
Start ArcMap or ArcCatalog and create a database connection to your geodatabase.
You must connect as the geodatabase administrator.
- Right-click the database connection in the Catalog tree, point to Administration, then click Administer Geodatabase.
- Click the Connections tab.
The user sessions that are currently connected to the geodatabase are listed. Your own connection appears in italics. Be aware that these are connected sessions; the same user can be connected from multiple clients and, therefore, can appear multiple times in the connected users list.
- Choose the user connection (or connections) you want to remove.
- Right-click the connections and click Disconnect.
An error message is returned if you do not have the privileges required to disconnect users. An error message is also returned if you attempt to remove your own connection.
The user session is dropped from the database. When the user attempts to use the session, an error message is returned indicating that the connection is inaccessible or that there is a network I/O problem.