Kbase P14089: Database crash on error 43 with errno 32
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/3/2005 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT 4.0
Progress 8.x
Progress 9.x
SYMPTOM(s):
Database crash on error 43 with errno 32
Database crash on error 6092 with errno 33
<function>:Unknown O/S error during <system call>, errno <error number>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6092)
bkioread:Unknown O/S error during read, errno 33, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6092)
lg file also shows 1124, 1152, 6086, 4229, 4232, 43 with errno = 32
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2> (1124)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file>
found <dbkey>, expected <dbkey>, retrying. (1152)
SYSTEM ERROR: <function>: Bad file descriptor was used during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6086)
Corrupt block detected when reading from database. (4229)
Corrupt block detected when attempting to release a buffer. (4232)
** Cannot find or open file <file-name>, errno = <number>. (43)
** Cannot find or open file <file-name>, errno = 32. (43)
Windows Event Viewer reports that os backup utility can't access Progress database-related files.
CAUSE:
A system backup (e.g. Veritas Backup Exec) being run while the database is running can cause this behaviour. This can lead to the errors reported. In this specific situation, the errors that normally indicate corruption (e.g. the 1124s) seem instead to be products of the database files being touched by the backup such that the database files can't be properly accessed.
The errnos with the error 43 and 6092 indicate that Progress is being blocked from accessing files:
32L ERROR_SHARING_VIOLATION The process cannot access the file because it is being used by another process.
33L ERROR_LOCK_VIOLATION The process cannot access the file because another process has locked a portion of the file.
FIX:
1. Check the Windows Event Viewer if it is reporting that the system backup utility is running at time of crashes. The Event Viewer might also report that the backup utility cannot access Progress database-related files.
2. Ensure that the database is shut down before a system backup utility is used.