DETAILS When a batch job is running under master and that master times out for some reason then the batch job will stop (an interactive job prompts for retry). Master could time out because it has been interrupted by a user or if it is doing a very large difference file copy on a slow system. After the job has aborted, master still maintains a connection to the database and the user needs to be manually disconnected. The fix for this was to change the default batch master timeout from 5 seconds to 5 minutes and to add a setting to the prefferences dialog. EXAMPLE PROGRAM Start Master Run a long batch update through master Interrupt master and wait for the batch job to terminate Resume master now try to attach the database for stand alone write - it says it is used by another user. WORKAROUND Change the master.timeout value to minimise the chance of this happening. If it does happen the start an interactive session, connect to master, disconnect the user (in the master maintenance dialog).