Kbase P134123: Client crash with DBI errors on Windows when many processes share the same temporary directory
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/05/2011 |
|
Status: Unverified
SYMPTOM(s):
Client crash with DBI errors on Windows when many processes share the same temporary directory
<function>:Unknown O/S error during <system call>, errno <error number>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9451)
bkioRead:Unknown O/S error during Read, errno 2, fd <file descriptor>, len <bytes>, offset <bytes>, file DBIXXXXX. (9451)
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)
bkioRead:Insufficient disk space during Read, fd <file descriptor>, len <bytes>, offset <bytes>, file DBIXXXXX. (9450)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file> found <dbkey>, expected <dbkey>, retrying. area <number> (9445)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file DBIXXXXX found <dbkey>, expected <dbkey>, retrying. area 6 (9445)
Corrupt block detected when reading from database. (4229)
bkRead: Error occurred in area 6, block number: <num>, extent: . (10560)
SYSTEM ERROR: Wrong dbkey in block. Found <dbkey>, should be <dbkey2> in area 6. (1124)
bkioread:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file DBIXXXXX. (6091)
Many processes have been run on the system up to the point of the failure (including processes already terminated)
Insufficient disk space or Write access denied (291)
FACT(s) (Environment):
Error messages refer only to DBI files, not database extents
Anti-virus properly configured to skip Progress temporary files
No other software configured to access Progress temporary files at the same time (backup, etc.)
Many client processes or AppServer agents are set to use the same temporary directory
Progress 9.x
OpenEdge 10.x
Windows
OpenEdge Category: Database
CAUSE:
Bug# OE00173045
CAUSE:
Under very rare circumstances on Windows, the DBI file name generation algorithm allows two processes running on the same system to compete for the same DBI file. This causes a crash of either process, or both.
FIX:
Fixed in 10.1C02 and higher
Fixed in 10.2A and higher.
To work around the issue, ensure that all clients started on the same system use a different temporary directory (different -T setting for each client).
For example a unique temporary directory based on time stamp could be created for each new process.