Re: Marking a DBspace as down

Carlos (and anyone else who's intersted) Here's the procedure for performing a warm restore of a DBSpace using ON-Bar. It works - I have used it extensively in testing. 1. Corrupt the raw or cooked file space (I used dd - note you have to use an input file to dd that is at least 10k in size to ensure you overwite enough of the raw space) - for testing only, obviously not in real life. 2. export ARCHIVE_TEST=true 3. onstat -d to determine the chunk number(s) that correspond to the DBSpace you wish to mark as down. 4. onmode -o <chunk number> - for each chunk that is to be marked as down. 5. onmode -O to override down dbspaces blocking checkpoints - answer YES to the message "This will render any dbspaces which have incurred disabling IO errors unusable and require them to be restored from an archive. Do you wish to continue (y/n)?" 6. onbar -r <dbspace name> Mail me or post if you have any more questions, Danny - remove the # from my e-mail address if you wish to use it - Carlos Oliveira wrote: > > Try onmode -o > > Undocumented but noted in the ONbar training manual. This will > bring a chunk offline. > > -dlw > Viegas, John Paul wrote: > > > 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 --