Re: Further on "How to bring a dbspace down" and OnBar

All, I have just seen the discussions regarding the problems of doing a warm restore of a corrupted chunk using OnBar. I hope I am not duplicating any information that has already been posted, but I could not find a definitive procedure to follow. Myself and a helpful chap from Informix technical support came up with this procedure. I hope it is of use to you all: 1. Perform system backup:- onbar -b etc. 2. Corrupt chunk:- e.g. dd if=rubbish_file of=/dev/chunk1 bs=512 conv=sync 3. Take system offline:- onmode -ky 4. Bring system back online:- oninit (online log shouldindicate a chunk down) 5. Set environment variable:- export ARCHIVE_TEST=true 6. Find out the chunk number of the down chunk:- onstat -d (flags ND for dbspace and PD for chunk - note dbspace should not be flagged as down yet, just the chunk) 7. Foce related dbspace down:- onmode -o <chunk number> 8. Check that dbspace is now flagged as down:- onstat -d 9. Allow system to checkpoint with down dbspaces:- onmode -O10. Initiate warm recovery of dbspace:- onbar -r chunk1 11. Backup current logical log:- onbar -l -c (this is very important - do not skip - fake the backup if you are not backing up logical logs) Please note that this procedure is my own work and is not supported by my employer - use it at your own risk, although it works fine for me. Any questions, please e-mail me at danny@uk.ibm.com as I do not read this newsgroup - just found it when I was doing a web search. Dan -------------------==== Posted via Deja News ====----------------------- http://www.dejanews.com/ Search, Read, Post to Usenet