Re: Hanging processes after database startup

Lou, I missed your original post so please bear with me. Have you used "onstat -u" to see what everyone is waiting on? The flags column should tell you the type of wait. If it's a latch or lock wait, the wait column might help trace down the specific problem. (That's according to my 5.0 admin guide. I believe 6 and 7 are a bit different/better.) Also, is there anything odd in the bottom of your online.log file? Try keeping a "tail -f online.log" on it when the database is brought up. Watch the timing of the messages. Finally, please re-send a copy of the original posting to me. I'll see if I can come up with more ideas. --Craig (craig@chemistry.utah.edu) > > [bulk of the message deleted] > > So what seems to be happening is that these hanging processes > seem to be waiting for a latch that never appears. The logical thing to > assume is that there is a shared memory problem. The shared memory > tunables seem to be set properly, however. Also, we have a OnLine 5.02 > UC2 database, much larger than the UC7 databases, that runs fine, without > ever having any hanging processes. And finally, the pattern of hanging > processes is truly baffling to me. Right after the database is brought > up, 50-75% of database processes hang. The number decreases the second > day, trickles to just one or two by the third day, and then ceases for > the rest of the week, only to restart when the machine is rebooted and > the database restarted. Does this seem logical to anyone? >