Kbase 18190: Errors 6081 And 6092 -- AI Corruption In Version 7.3
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/09/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 7.3C
SYMPTOM(s):
User dies with an MTX latch held.
bkioWrite: lseek error <error number> on file <file> at <address>, file <file-name>. (6081)
<function>:Unknown O/S error during <system call>, errno <error number>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6092)
CAUSE:
Progress Consulting identified a bug in Version 7.3C that had to do with having more than 255 extents. The bug showed up by cycling around and reusing other extents. It would go and corrupt that extent. And a user was also hung holding an MTX latch open. Watchdog cleaned up the user but it also shut down the database, which would then not come up until the extent was fixed.
This error condition can indicate corruption.
FIX:
If the extent is an empty one and you have other empty extents, you can copy a good extent to the same name. For example, if it was extent 5 that was corrupt, copy .a6 to .a5 if they were both empty.
If it contained data, back up the good ai extents, disable ai, remove all the extents and recreate them.
Of course, avoiding the problem would be the preferred method. Users might want to reconsider the use of that many extents.