Re: Online 5.0: using cooked UNIX files and raw disk slices

Don't do it! That is, don't do it unless you do not mind permanently and forever having the cooked chunk around. Even if you don't mind, use a symbolic link to the actual file, so that when you change your mind and want to use a device, you can. You'll need to use the same offset, of course (presumably zero) in the device. Don't forget, once it is part of the dbspace, you can't change the chunk and you can't drop it. You can only drop the whole dbspace. So, I strongly suggest that you do not add a cooked chunk to any OnLine system except in extremis, and even then only if you expect to rebuild the whole dbspace after the extreme situation is resolved. But, if you do decide to do it, use a symbolic link for the device or file name. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> >From: sur@hogpe.ho.att.com (-S.RAMASWAMY) >Date: Tue, 18 Jul 1995 22:51:08 GMT >X-Informix-List-Id: <news.15558> > >We are using Online 5.0 and I-SQL 4.11. We need to add a new dbspace >on a machine that's been running for a while. Instead of backing up the >entire machine, and reformatting the disk to add this dbspace, we are >thinking about using cooked UNIX files to store this dbspace. The data >in this dbspace is not too critical and the performance hit should also >not be a problem. > >Now, given this scenario, does anybody have any words of wisdom?? Are >there any "gotcha's" out there that we should be aware of?? Please reply >by email to sur@hogpa.ho.att.com > >TIA, > >Suresh >sur@hogpa.ho.att.com