Re: Bad Chunk

From: Manoj Narayanankutty <mnarayan@crosskeys.com> > > When I am trying to initialize the shared memmory using oninit -s. I >get the following message in the online.log: > > >shmget: [EEXIST][17]: key 526a4801: shared memory already exists >00:11:21 mt_shm_init: can't create resident segment > >00:11:38 shmget: [EEXIST][17]: key 526a4801: shared memory already>exists >00:11:38 mt_shm_init: can't create resident segment This means that you still have some shared memory left behind (probably from a crash). You can try onmode -ky a couple of times to try and clear things up, or use ipcs to find the chunks and ipcrm to clear them up. Or reboot. >Also warnings for bad primary chunk for 2 dbspaces comes in my standard >output. Inspite of these I can bring the databse to online mode, but >could not >do any query operation to any of the databases residing on the >corrupted chunks.I don t remember doing anything, extraordinary to >corrupt the chunks. >I would appreciate if some one can give me a reason for this >occurence. Disk media failures are one of the most common reasons I've seen. And power surges. Also (very rarely) kill -9 on an oninit process. But there's any number of potential causes. Your best bet is to replace the disks, reinitialise your database (oninit -i), rebuild the dbspaces and restore from a backup. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com