ARCHIVE_TEST 0/1 session

оПХ БЙКЧВЕММНЛ ЯНЯРНЪМХХ ОНГБНКЪЕР OnBar БНЯЯРЮМЮБКХБЮРЭ chunk ЙНРНПШИ МЕ ОНЛЕВЕМ down Б РЕОКНЛ (warm) ПЕФХЛЕ.

"To force onbar to restore dbspace(s) not Marked as "down", do the following :

1. Set environmental variable ARCHIVE_TEST = 1.
2. Type onmode -O {dbspace number}
3. You will see something similar to the following in the Informix Messages file :

15:02:46 Assert Failed: WARNING! WARNING! Chunk 2 is being taken OFFLINE for testing.
15:02:46 Who: Session(8, informix@ultra, 0, 170587664) Thread(28, onmode_mon, a28f0d8, 1)
15:02:46 Results: DBspace testdbs is disabled.
15:02:46 Action: Restore DBspace testdbs
15:02:46 See Also: /dev/null/af.1c0233

danny@uk.ibm.com (Daniel Williams) writes:-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.

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.

export ARCHIVE_TEST=true

onstat -d to determine the chunk number(s) that correspond to the DBSpace you wish to mark as down. onmode -o 'chunk number'; - for each chunk that is to be marked as down. 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)?
onbar -r 'dbspace name'; "