Re: Marking a DBspace as down

JP Wrote: }>From ilist@rmy.emory.edu Wed Aug 13 11:06:55 1997 }>Received: from rmy.rmy.emory.edu (rmy.rmy.emory.edu [170.140.97.4]) }> by hobbes.dbintellect.com (8.8.6/8.8.6) with ESMTP id LAA00428 }> for <settler@dbintellect.com>; Wed, 13 Aug 1997 11:06:54 -0600 (MDT) }>Received: (from ilist@localhost) by rmy.rmy.emory.edu (8.7.1/8.7.1) id JAA01608 for informix-list-out; Wed, 13 Aug 1997 09:10:01 -0400 (EDT) }>From: viegasjp@panasonic.com (Viegas, John Paul) }>To: informix-list@rmy.emory.edu ('Informix-List') }>Message-Id: <1997Aug13.090847.1486.1101557@mecamail.panasonic.com> }>X-Mailer: Microsoft Mail via PostalUnion/SMTP for Windows NT }>Mime-Version: 1.0 }>Content-Type: text/plain; charset="US-ASCII" }>Date: Wed, 13 Aug 1997 09:09:43 -0400 }>Subject: Marking a DBspace as down }>Sender: informix-list-owner@rmy.emory.edu }>Reply-To: viegasjp@panasonic.com (Viegas, John Paul) }>X-Informix-List-Id: <list.15932> }> }> }>Hello, }> We are trying to test a single dbspace restore with ONBAR, but we are }>having trouble marking that dbspace as down. We are using raw }> partitions, or else we would just delete the dbspace file in the }>appropriate file system. If anyone has been successful in bringing a }>DBspace down your help would be greatly appreciated. }> }>Thanks }>JP }> I had a similar problem, so I opened a tech support case with Informix. In my case, I had a table fragmented round-robin across eight dbspaces. Each dbspace had a single, non-mirrored chunk. One of the chunks went down, and since it was the Primary chunk for the dbspace (in fact, the only chunk), I expected Informix to mark the dbspace as down. When it did not, I contacted Informix. They indicated that with 7.2 ODS release, the dbspace is left on-line even though the chunk is marked down. They established this behavior at the request of various customers. This behavior cannot be influenced by any setting of the ONDBSPACEDOWN setting, since the dbspace doesn't come down. They suggested I write a script to monitor for "down" dbspaces (I will look for down chunks), and stop the instance if any are found. Does anyone else have any creative ideas around this problem. ------------------------------------------------------------------- Jeff Craig | dbINTELLECT Technologies, Inc. Senior Consultant | Golden, CO | (303) 275-6954 ext. 8008 | email: settler@dbintellect.com | fax: (303) 275-2134 -------------------------------------------------------------------