Kbase P142358: proutil dbname -C truncate command terminates with a buffer stack overflow error when going through
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
SYMPTOM(s):
proutil dbname -C truncate command terminates with a buffer stack overflow error when going through logical undo
Database performed an emergency shutdown when bi threshold was reached.
Begin Logical Undo Phase, <number> incomplete transactions are being backed out. (7162)
Logical Undo Phase begin at Block <blknum> Offset <offset>. (11231)
buffer stack overflow
** Save file named core for analysis by Progress Software Corporation. (439)
<time><Multi/Single> session end. (334)
Truncate bi session end. (334)
No message indicating that Logical Undo Phase has completed.
Stack trace from _proutil reads:
bmLocateBuffer2
bkAcAddToEnd
cxRemoveFromDeleteChain
cxPut
FACT(s) (Environment):
Fearing bi file was too close to 2 GB, a new bi extent was added to the database after the proutil dbname -C truncate command terminated.
JFS filesystem where the bi file resides does not support large files.
Database does not have after imaging enabled.
IBM AIX
OpenEdge 10.1B03 Service Pack
CAUSE:
Bug# OE00181827
CAUSE:
BI corruption as a result of an emergency shutdown that occurred when the -bithold parameter was reached.
FIX:
Workaround:
Use the -bistall parameter on the database to prevent the database from performing an emergency shutting down if the -bithold parameter is reached.
To address BI corruption issue:
Go to backup and roll forward AI (After Imaging) files.
If AI was not being used and the last backup is not good or too old to revert to, then take an Operating System backup of the database. Then force into the database with the command proutil dbname -C truncate bi -F. Once you have gained access to the database make use of idxfix and dbtool or proutil dbname -C dbrpr to see if there is any corruption in the database. See solution: P129563, "What tools / utilities can I run to check the integrity of a database or check for corruption?" for additional information on tools within 10.1B and later that can assist with validating database integrity in a production and non-production environment.