Deleting a chunk

Dear Jonathan, Art, and Informix list friends: I saw a recent post to the list regarding deleting a chunk. My situation is this. We decided not to use a certain table in a dbspace any more. The dbspace now requires much less space. How do I get rid of a chunk or two? or is there a better way to free up this space? The post I saw said to use the command: "onspaces -d dbspace -p path/to/chunk -o offset" I verified that nothing is in the last chunk using "onstat -d" (results at bottom) and the command I would then use would be: "onspaces -d web_data -p /export/data/chunk011" Any warnings, suggestions, etc? I have a years worth of information in this database and I don't want to mess it up. Also, we have not backed it up. Before I try anything, I want the database backed up, but there are so many methods that they confuse me. I have posted before and if you remember, I am no expert. I have merely a year of trial and error experience. Could you suggest a backup method? Thanks in advance for your time and suggestions. You guys have always been sooooo helpful. Sincerely, Kevin Carroll Kevin.Carroll@mobilnet.gte.com OUTPUT OF ONSTAT -D --> INFORMIX-Universal Server Version 9.13.UC3 -- On-Line -- Up 19 days 21:33:28 -- 106584 Kbytes Dbspaces address number flags fchunk nchunks flags owner name 110a2108 1 1 1 1 N informix web_root 110a3050 2 1 2 11 N informix web_data 110a30c8 3 1 12 3 N informix performance 110a3140 5 1 14 1 N informix uwc_space 110a31b8 6 8000 16 1 N S informix mysblobs 5 active, 2047 maximum Chunks address chk/dbs offset size free bpages flags pathname 110a2180 1 1 0 500000 297982 PO- /export/data/web_root 110a22d0 2 2 0 500000 2 PO- /export/data/chunk001 110a23a8 3 2 0 500000 9 PO- /export/data/chunk002 110a2480 4 2 0 500000 21 PO- /export/data/chunk003 110a2558 5 2 0 500000 109 PO- /export/data/chunk004 110a2630 6 2 0 500000 381 PO- /export/data/chunk005 110a2708 7 2 0 500000 765 PO- /export/data/chunk006 110a27e0 8 2 0 500000 58253 PO- /export/data/chunk007 110a28b8 9 2 0 500000 483389 PO- /export/data/chunk008 110a2990 10 2 0 500000 319773 PO- /export/data/chunk009 110a2a68 11 2 0 500000 483613 PO- /export/data/chunk010 110a2b40 12 3 0 1000 64 PO- /export/data/perf_chunk 110a2c18 14 5 0 25000 23823 PD- /export/data/uwc_chunk 110a2cf0 15 3 0 1000 915 PO- /export/data/perf_chunk2 110a2dc8 16 6 0 5000 3659 3697 POS /export/data/apb_blobspace 110a2ea0 17 3 0 5000 4997 PO- /export/data/perf_chunk3 110a2f78 18 2 0 500000 499997 PO- /export/data/chunk011 17 active, 2047 maximum

In your onconfig set TAPEDEV to a file or a tape device and run "ontape -s" for a whole system backup. can't get any easier...can it...;-) --Anil Karkera Carroll, Kevin wrote: > Dear Jonathan, Art, and Informix list friends: > > I saw a recent post to the list regarding deleting a chunk. My situation is > this. We decided not to use a certain table in a dbspace any more. The > dbspace now requires much less space. How do I get rid of a chunk or two? or > is there a better way to free up this space? > > The post I saw said to use the command: "onspaces -d dbspace -p > path/to/chunk -o offset" > > I verified that nothing is in the last chunk using "onstat -d" (results at > bottom) and the command I would then use would be: "onspaces -d web_data -p > /export/data/chunk011" > > Any warnings, suggestions, etc? I have a years worth of information in this > database and I don't want to mess it up. Also, we have not backed it up. > Before I try anything, I want the database backed up, but there are so many > methods that they confuse me. I have posted before and if you remember, I am > no expert. I have merely a year of trial and error experience. Could you > suggest a backup method? Thanks in advance for your time and suggestions. > You guys have always been sooooo helpful. > > Sincerely, > > Kevin Carroll > Kevin.Carroll@mobilnet.gte.com > > OUTPUT OF ONSTAT -D --> > > INFORMIX-Universal Server Version 9.13.UC3 -- On-Line -- Up 19 days > 21:33:28 -- 106584 Kbytes > > Dbspaces > address number flags fchunk nchunks flags owner name > 110a2108 1 1 1 1 N informix web_root > 110a3050 2 1 2 11 N informix web_data > 110a30c8 3 1 12 3 N informix performance > 110a3140 5 1 14 1 N informix uwc_space > 110a31b8 6 8000 16 1 N S informix mysblobs > 5 active, 2047 maximum > > Chunks > address chk/dbs offset size free bpages flags pathname > 110a2180 1 1 0 500000 297982 PO- > /export/data/web_root > 110a22d0 2 2 0 500000 2 PO- > /export/data/chunk001 > 110a23a8 3 2 0 500000 9 PO- > /export/data/chunk002 > 110a2480 4 2 0 500000 21 PO- > /export/data/chunk003 > 110a2558 5 2 0 500000 109 PO- > /export/data/chunk004 > 110a2630 6 2 0 500000 381 PO- > /export/data/chunk005 > 110a2708 7 2 0 500000 765 PO- > /export/data/chunk006 > 110a27e0 8 2 0 500000 58253 PO- > /export/data/chunk007 > 110a28b8 9 2 0 500000 483389 PO- > /export/data/chunk008 > 110a2990 10 2 0 500000 319773 PO- > /export/data/chunk009 > 110a2a68 11 2 0 500000 483613 PO- > /export/data/chunk010 > 110a2b40 12 3 0 1000 64 PO- > /export/data/perf_chunk > 110a2c18 14 5 0 25000 23823 PD- > /export/data/uwc_chunk > 110a2cf0 15 3 0 1000 915 PO- > /export/data/perf_chunk2 > 110a2dc8 16 6 0 5000 3659 3697 POS > /export/data/apb_blobspace > 110a2ea0 17 3 0 5000 4997 PO- > /export/data/perf_chunk3 > 110a2f78 18 2 0 500000 499997 PO- > /export/data/chunk011 > 17 active, 2047 maximum