Kbase P95750: Progress 9.1D crashes when emptying static temp-tables
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  1/6/2009 |
|
Status: Verified
SYMPTOM(s):
9.1D06
Multiple static temp-tables are populated and emptied in a loop
Temp-tables are defined LIKE database tables
Temp-tables are defined as new tables
Temp-tables are not emptied within a transaction
Same behaviour defining Temp-Tables as UNDO and NO-UNDO
No corruption found in database after DBRPR
Multiple, various error messages received before Progress cores depending on method used to empty temp-table
FOR EACH <temp-table>:
DELETE <temp-table>.
END.
Results in a session hang
EMPTY TEMP-TABLE <temp-table> can result in errors 210, 16 then the session crashes
SYSTEM ERROR: Attempt to read block <number> which does not exist. (210)
SYSTEM ERROR: bffld: nxtfld: scan past last field. (16)
<hTT>:EMPTY-TEMP-TABLE can result in errors 1700, 3181, 274, 257, 1410, 49
Identifier was left blank or is more than <maximum> characters. (1700)
Cannot create widget of type <type>. (3181)
** The character <character> is not permitted in name <name>. (274)
** The first character of <name> must be alphabetic. (257)
** The first character of T�ÿÿÿ must be alphabetic. (257)
Error code <number> returned from fdfnd. (1410)
SYSTEM ERROR: Memory violation. (49)
Multiple, various protrace results depending on method used to empty temp-table
Stack trace from _progres using DELETE <temp-table> reads:
latnap
cxGetRootAndArea
cxLocateValidBlock
cxSearchTree
cxPositionToNext
cxNextPrevious
cxFind
Stack trace from _progress using EMPTY TEMP-TABLE <temp-table> reads:
msgnCB
msgCB
dsmFatalMsgnCallBack
bmLockBuffer
cxKillKids
cxKill
dsmObjectDelete
Stack trace from _progres using <temp-table>:EMPTY-TEMP-TABLE reads:
profldx
kmfldx
kmWordsStash
kmkfu
profldu
prottnew
FACT(s) (Environment):
Progress 9.1D
UNIX
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
Upgrade to Service Pack 9 for Progress 9.1D