Kbase P102288: Getting "buffer stack overflow" on truncate bi, probkup off line and other single user process.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/5/2009 |
|
Status: Verified
SYMPTOM(s):
Getting "buffer stack overflow" on truncate bi, probkup off line and other single user process.
proutil <db> -C truncate bi
Begin Physical Redo Phase at <current address>. (5326)
Physical Redo Phase Completed at blk off upd . (7161)
Begin Physical Undo transactions at block offset (7163)
Physical Undo Phase Completed at <bi address>. (5331)
Begin Logical Undo Phase, incomplete transactions are being backed out. (7162)
buffer stack overflow
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
When Progress starts the database, does an off line backup or truncation of the bi file, or any other single user operation the default value of the -B is only 10. The truncation process is requiring more than 10 buffers to complete the process but do not have them and fails. The message said "buffer stack overflow message" but should have said: there weren't "enough buffers". In newer releases of OpenEdge this default -B has been resized to a larger value.
FIX:
Run the process with a larger value for -B.
All of the following would allow the bi file to be truncated successfully.
ie:
proutil <dbname> -C truncate bi -B 5000
pro <dbname> -B 5000
proserve <dbname> -B 5000