Kbase P9996: Memory violation error 49 running Veritas Cluster Server.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/21/2008 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
Progress 9.x
SYMPTOM(s):
Client attempting to connect to database in multi-user mode.
SYSTEM ERROR: Memory Violation Error (49)
Running After Imaging.
PROGRESS stack trace
Command line arguments are /usr/dlc/bin/_progres -b -db /wrk/live -p ./app/app1
uttrace() +0x100 from: /titan/dlc9/bin/_progres
utcore() +0xec from: /titan/dlc9/bin/_progres
drexit() +0x548 from: /titan/dlc9/bin/_progres
msgout() +0x304 from: /titan/dlc9/bin/_progres
msgnCB() +0xc8 from: /titan/dlc9/bin/_progres
msgCB() +0x14 from: /titan/dlc9/bin/_progres
dsmFatalMsgnCallBack() +0x68 from: /titan/dlc9/bin/_progres
dbenvout() +0x214 from: /titan/dlc9/bin/_progres
dsmUserDisconnect() +0xec from: /titan/dlc9/bin/_progres
proend() +0x388 from: /titan/dlc9/bin/_progres
fdend() +0x194 from: /titan/dlc9/bin/_progres
drexit() +0x4b4 from: /titan/dlc9/bin/_progres
drExitOnTerm() +0x284 from: /titan/dlc9/bin/_progres
_getfp() +0x220 from: /usr/lib/libthread.so.1
_fork() +0x864 from: /usr/lib/libthread.so.1
??() +0x13e853c from: ??
stVacate() +0x1e0 from: /titan/dlc9/bin/_progres
fillstr() +0x80 from: /titan/dlc9/bin/_progres
dsmUserSetName() +0xcc from: /titan/dlc9/bin/_progres
dbuid() +0x58 from: /titan/dlc9/bin/_progres
prodftuid() +0x174 from: /titan/dlc9/bin/_progres
procon() +0x8c8 from: /titan/dlc9/bin/_progres
fdcon() +0x44c from: /titan/dlc9/bin/_progres
scconx() +0x50c from: /titan/dlc9/bin/_progres
sccon() +0x588 from: /titan/dlc9/bin/_progres
drcon() +0x94 from: /titan/dlc9/bin/_progres
main() +0x1d0 from: /titan/dlc9/bin/_progres
_start() +0xb8 from: /titan/dlc9/bin/_progres
CAUSE:
Bug# 20020124-012.
CAUSE:
Enabling after imaging may cause client processes to core dump with Memory Violation (49) and cause the database to shutdown abnormally.
FIX:
Migrate to 9.1D02 or higher.