System tables

_______________________________________________________________ This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. Thank you. _______________________________________________________________ Somehow I already know what the answer is going to be... We have a dbspace made up of 4 chunks, totaling about 7 gig. Most of it is empty now, and we'd like to reclaim some space, taking a couple of those chunks back. The problem is, the system tables are fragmented all over all 4 chunks. Is there any way to correct this?

"Colleen M. Morrow" wrote: > > _______________________________________________________________ > > This message and any attachments are intended for the individual or entity > named above. If you are not the intended recipient, please do not read, > copy, use or disclose this communication to others; also please notify the > sender by replying to this message, and then delete it from your system. > Thank you. > _______________________________________________________________ > > Somehow I already know what the answer is going to be... > > We have a dbspace made up of 4 chunks, totaling about 7 gig. Most of it is > empty now, and we'd like to reclaim some space, taking a couple of those > chunks back. The problem is, the system tables are fragmented all over all > 4 chunks. Is there any way to correct this? I'm presuming a single database . . . . There's no way possible unless you drop and recreate the database, then reload the data. Depending on the extent severity of the 'normal' tables, you might buy some extent concatenation by dumping the data and the table schema, resizing the extent sizes, then reloading the data. -- John Carlson Informix DBA WHSmith USA #include std_disclaimer.h /* These are my opinions, not my company's opinion */