An XDB client running on Windows or UNIX platforms can have several concurrent sessions. For example, a Windows user could open a window and start the SQLWizard. Next, the same user could open another window and start the XDB Migrate Utility, logging in to the XDB Server with the same AuthID and Node Name. The XDB Server will show two user sessions, both with the same AuthID and Node Name, but each running a different process, and each showing a different Session ID number. Likewise, a Windows client can start several sessions by clicking on multiple program icons. Again, the user's multiple sessions show up on the XDB Server, all having the same AuthID and Node Name but with unique Session ID numbers.
When a client session fails or otherwise aborts without logging out, the XDB Server automatically detects the aborted session and releases all resources and locks. Any in-process transactions are rolled back. If the user has other sessions running, they are not affected.