RE: ALTER FRAG.. INIT IN (was: Art -- clarification pls)

And while we're on the subject, Art, here's a couple more questions: (1) Does this statement require an exclusive lock on the table (I assume that it *does*)? (2) Does it use as much log space as the unload/drop/re-create/load method? (3) Is it done in one transaction (i.e., do we have to watch for long transaction w/ large table)? TIA ================================ Paul A. Mosser, Open Systems DBA Informix Certified DBSA Wells Fargo & Co. Tempe, Arizona paul.mosser@wellsfargo.com ================================ -----Original Message----- From: Russ_Evans@doh.state.fl.us [mailto:Russ_Evans@doh.state.fl.us] Sent: Thursday, February 04, 1999 4:28 PM To: informix-list@iiug.org Subject: Art -- clarification pls Art; You have mentioned in a previous message that the statement ALTER FRAGMENT ON TABLE tablename INIT IN dbspace is a good way to consolidate the extents on a table. Before I try that though, I wanted to make sure that it would work in a specific case. In a table defined as follows (in a database created in dbspace): create table tbl( a integer,b text in blobspace ); Will the ALTER FRAGMENT statement above work well here? It won't transfer all of my blobs from the blobspace to the dbspace will it? Russ Evans Division of Information Resource Management The Alexander Building 2020 Capital Circle SE, Room 2407 Tallahassee, FL 32399-1733 (850)413-8490 S/C 293-8490