D
dbeavon
Guest
Thanks gus, Is this type of a problem specific to client-server connections? We've only recently started using "client-server" connections recently (from PASOE) and I'm very suspicious of the "remote servers". I don't recall running out of free shared memory from a "shared-memory" client ... regardless of whether any rollbacks were underway or not. Also, I'm wondering if the client-server connections are using the same pool of locks (-L). We never reached that limit before the crash occurred. I hoped that disconnecting "client-server" connections would be much safer than this. In one of the KB's which explained this message ("user died holding shared memory locks"), there was also a statement saying that a fix is to migrate over to "client-server" rather than "self-service": Progress KB - Why a Database shuts down with the message User died holding shared memory lock? For sites where this occurs frequently, a way to prevent an abnormal database shutdown is to run clients as remote clients as opposed to self-service. Given the crash points to running out of shared memory, should we be changing the default value of -Mxs? Is that common? Is it more common for customers as they migrate to "client-server" connections?
Continue reading...
Continue reading...