RE: Unix Administrator stikes again

onbar -r dbspaceX should recover the "down" dbspace to a "current" state.This appears to be what you want! The "Point in time" restore refers to an arbitrary date/time, such as noon yesterday. The onbar utility will not allow you to restore some, but not all, dbspaces, to a specific date/time. Such a restore requires that all dbspaces be restored in order to maintain consistency and integrity. I.E. You would NOT most dbspaces to be current as of today and others to contain yesterday's version. This could cause insconsistencies. Gor that reason a "point in time" restore (to yesterday's version of the database) is only supported for a restore of all dbspaces. I hope this clarifies your options. -----Original Message----- From: Geoffrey Poole To: informix-list@iiug.org Sent: 1/29/00 3:26 AM Subject: Unix Administrator stikes again The Unix administator has just ruined my Saturday (familiar story ?). We were replacing 4GB disks with 18GB, I marked the chunks on the disks to be removed as DOWN, relying on the mirror to recover later. But one wrong disk was removed and now I have 2 chunks on the same dbspace with both primary and mirror (which failed sanity checks) marked as DOWN. I know Informix can log on and "fix" the chunk state, but this is the weekend .. I intend running "onbar -r dbspaceX" to restore just the effected dbspace. The manual states that you can not restore an indiviual dbspace to a point in time, so my question is what of data consistency ? There was very little if no database activity since the last Level 0 but I can not be sure. Is a full level 0 my only "safe" action ? Hardware: Sun E450 x 4CPUs OpSys: Solaris 2.6 (SunOS 5.6) Informix Products: Universal Server 9.14.UC2 + WebBlade 3.31.UC2 ------------------ Geoff Poole Informix Database Administrator geoffrey.poole@ogs.co.uk Oxford GlycoSciences (U.K) Ltd,