G
George Potemkin
Guest
294912 = 0x48000 327681 = 0x50001 360450 = 0x58002 393219 = 0x60003 425988 = 0x68004 458757 = 0x70005 I guess Remote Client Servers get the semid's from db shared memory. When one of servers corrupts this information in shared memory then the other ones begin to report the 10839's. "Mad" server "updates" semid's for its clients. If it served more than one client it may corrupt more than one semid. Can you use the -Ma 1 as a workaround? BTW, the first semset (the one with 7 semaphores) is used only during db startup and during logins/logouts of self-serviced clients. I guess you will not see the last byte of this semid in the 10839's
Continue reading...
Continue reading...