C
ChUIMonster
Guest
> There is no option to release shared memory segments from the server level. This problem has nothing to do with shared memory segments. You seem to think that "Memory violation" has sometime to do with "full shared memory segments". As if you think they are running out of space or something. Nothing like that is happening. It is completely and perfectly normal for your shared memory segments to look the way they do. When the db starts up it allocates and initializes shared memory to store -B and various other data structures. The OS may limit the size of any one chunk of shared memory - thus there can be multiple "segments". Ideally they will all be full. That way you are not wasting any. But depending on how much you have asked for there can be rounding of sizes and Progress reserves a bit extra for some things. So they are not all always completely full. But there is nothing wrong with any of the shared memory utilization data that you have shown. It is normal. You do not have a problem with full shared memory segments. A "memory violation" is not a capacity problem. It is an *access* problem. The db server attempted to access a memory location that it does not have permission to access. The location that it attempted to access *might* have been in shared memory. Or it might not have -- we don't know, the bogus address is not reported in the error message. As George points out there is a bad address in the corrupt block that is reported *later*. That may, or may not, be a useful clue. As Gus points out the SQL92 engine in v9 has many bugs of this sort. Your best course of action is to upgrade to a modern release. If the hardware and operating system are as old as v9 then you should also make sure that they get upgraded. Your worst course of action is to continue to think that "full shared memory segments" is in any way related to your db crash. As far as "root cause" goes -- it was probably either a hardware problem or one of those bugs that Gus refers to. If it is hardware then I would expect it to continue to happen and that errors will appear in the system logs. But it may not be obvious that they are related to this. If it is a Progress bug you are pretty much out of luck. Support for v9 mostly consists of sympathy for your predicament.
Continue reading...
Continue reading...