Re: How to mark dbspace "down"

}>From ilist@rmy.emory.edu Sun May 18 20:35:07 1997 }>Received: from rmy.rmy.emory.edu by hobbes.dbintellect.com via ESMTP (950413.SGI.8.6.12/930416.SGI.AUTO) }> for <settler@dbintellect.com> id UAA25785; Sun, 18 May 1997 20:34:11 -0600 }>Received: (from ilist@localhost) by rmy.rmy.emory.edu (8.7.1/8.7.1) id UAA09114 for informix-list-out; Sun, 18 May 1997 20:45:00 -0400 (EDT) }>From: David Williams <djw@smooth1.demon.co.uk> }>Message-Id: <3MT8oEAA94fzEwqg@smooth1.demon.co.uk> }>Subject: Re: How to mark dbspace "down" }>Date: Mon, 19 May 1997 00:22:40 +0100 }>Reply-To: David Williams <djw@smooth1.demon.co.uk> }>Organization: not applicable }>Sender: informix-list-owner@rmy.emory.edu }>To: informix-list@rmy.emory.edu }>X-Informix-List-Id: <news.38050> }> }>In article <5lh487$bjo@drn.zippo.com>, ibogorad@lhr-sys.dhl.com writes }>> }>>Hi folks, }>> }>>I am evaluating OnBar in Online 7.22, generally it seems OK - as easy as ontape }>>to use and in most cases it works. }>>However , if a non-critical dbspace is not down, it does not allow to do warm }>>restore - says - " Excuse moi, the dbspace is up and I am not going to run }>>restore }>>on it" }>> }>>Now , I have a non-critical dbspace (i.e dbspace which is not rootdbs and does }>>not contain logical or phys logs). It consists of one chunk, which is cooked }>>file }>>for simplicity. Mirroring is disabled in this instance. }>> }>>I create some dummy database in this dbspace, populate with some data and then }>>create level 0 archive ( onbar -b -w ). }>> }>>Then I do something nasty : say delete this chunk on Unix level ( yeap, just rm) }>>or corrupt it : banner " I'll be back.Schwarz"> /my/poor/chunk . }>> }>>After that I do all sort of things to assure Online that something bad has just }>>happened: force checkpoints, run onchecks, bring the instance down and up, etc. }>>Online marks the chunk down, but it thinks that the dbspace is perfectly well, }>>though this bleeding dbspace consists of only one chunk,which is terminally ill. }>> }>>Therefore I stiil cannot do warm restore for this dbspace, only full (cold) }>>restore }>>is possible. }>> }>>Are there any sure ways to tell Online that a dbspace is down? }>> }> Online 7.22? Run }> }> onspaces -- }> }> you should see the -O option to flag a dbspace as up (online) and the }> -D option to flag a dbspace as down. }> }>>All ideas will be appreciated. }>> }>>Cheers }>>Ilya }>> }>> }> }>-- }>David Williams }> That's good advice for how to see if a dbspace is down, but I think the point was that Informix is extremely tolerant of dbspace "problems". I have played with this too, trashing my dbspace by doing cat /dev/null >dbspacename, and Informix just runs merrily along. I have tried numerous things to get it to recognize that the dbspace is trashed, including onstat, selecting from a table in the dbspace, etc. The only thing that forced it to acknowledge that there was a problem was to shut down and start up -- makes testing a bit difficult. ------------------------------------------------------------------- Jeff Craig | dbINTELLECT Technologies, Inc. Senior Consultant | Golden, CO | (303) 275-6954 ext. 8008 | email: settler@dbintellect.com | fax: (303) 275-2134 -------------------------------------------------------------------