The second database is a Schema holder for the ODBC DataServer:
The application connects to a remote database via the schema holder.
The application connects via a DSN to an Access database then to a remote server DataSource (DSN) via linked tables using a second DSN.
It is this second communication which fails.
The Database log file repeats the Options message for the schema holder before the bkiowrite message and eventually abnormal shutdown:
(12699) Database <1st database> Options:
(12699) Database <2nd database> Options: which repeats many times followed by bkiowrite error
(9450) bkioWrite: Insufficient disk space during write, , fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>.
(3645) bkwrite: write to disk failed errno 0.
(2249) Begin ABNORMAL shutdown code 2
(334) Multi-user session end.
The database crash did not disconnect all running Progress processes.
Although connection problems have happened in the past, this is the first time it resulted in a crash.
Client sessions use Georgia Software terminal emulator (aggressively holds onto terminal connections).
Client sessions use RF controller to connect from RF handhelds (aggressively holds on to RF connections).