Re: Changing Extent Sizes and DBSpace Questions...

In article <33D3AFA5.1EF5@berksiu.k12.pa.us>, Tony Marasco <tonmar@berksiu.k12.pa.us> writes >Since I am new to OnLine I have some questions regarding its setup. >I've been burned once (consultant did not give me enough logs or >logspace) and I don't want it to happen again... > >We are a service bureau managing several clients currently >migrating to an Informix system. Presently the system is set >to a DBSpace per client. Each client has their own database. >Is it necessary to maintain multiple DBSpaces? An obvious advantage >*not* to do this is adding 1 chunk of disk insted of many small >pieces. > Generally you should have one dbspace of one chunk per disk. Then you can control which disk is used by creating tables in the relevant dbspace. Also try to keep each database within one dbspace so that if one disk fails you can restore just that dbspace and still have a consistent database. >A pilot database has many extents. Can this be changed on the fly >or do I have to rebuild the entire database? I presume the latter >is the case... > It is usually simplest to dbexport the database, drop the database and then dbimport the database. >Thanks in advance, -- David Williams