Kbase 18261: SAVE CACHE Causes DB Crash
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/11/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress 8.2B
SYMPTOM(s):
SYSTEM ERROR: bkaddr called with negative blkaddr: <number> (762)
Corrupt block detected when attempting to release a buffer. (4232)
SYSTEM ERROR: wrong dbkey in block. Found <dbkey>, should be <dbkey2> (1124)
CAUSE:
Database crashes when the following code is run on the client:
FIND FIRST _Block.
SAVE CACHE CURRENT "ms" TO "ms.cache".
This will not fail with any other VST and saving the cache the same way.
This will also not fail if the save cache is not after "find first _Block".
That is, this exact combination needs to be used.
This does not fail with the sports Database.
Also note that running a full dbrpr (1 & 4) was not able to detect any problems with the database.
FIX:
Upgrade to 8.3B or later.
A possible workaround is that you connect to the database, run a "for each" on every table and then do a "save current", this way you will not query the _Block table.