Unable to drop chunks

[howi...@gmail.com]

IBM Informix Dynamic Server Version 11.50.FC3
HP-UX B.11.11 U 9000/800 2262126760 unlimited-user license

I am unable to drop a number of chunks on a user instance due it not being empty.

Informix $ onspaces -d chunk1 -p /dev/vg_database_2/rlvol10 -o 0 -y
Chunk not dropped.
ISAM error: Chunk not empty

there is the following in the chunk...

inddbs:'informix'.TBLSpace 3 50
FREE 53 39788
inddbs:'informix'.TBLSpace 39841 50
FREE

would anyone know how to remove these tablespaces so I can continue to drop the chunks and eventually the unwanted dbspace?

Thanks in advance
H

[Art Kagel]

You will not be able to drop any individual chunks that contain TABLESPACE entries, but you can drop the entire dbspace!

Art

Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/

Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference.  Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

_______________________________________________
Informix-list mailing list
Inform...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

[Fernando Nunes]

Art's answer is correct (and no one needs me to say it, but I'll add some more info)
If your ultimate goal is to drop the dbspace, just clean up all user objects and drop it (all chunks at once).

The reason why this happened is simple and can/should be avoided:

- TBLSpace is a system partition where the partition headers are stored. It has a default initial and next extent of just 50KB (maybe I'm missing a few KB or maybe there's some differences dpending on the page size)

- The initial extent is created in the first chunk

- As you create tables and indexes on tha dbspace, the initial extent may not be enough. At that time it extends into another chunk if the first chunk is full

To avoid this:

1- Use TBLTBLFIRST and TBLTBLNEXT parameters in $ONCONFIG to define the initial and next size of ROOTDBS ONLY!

2- Whenever you create a new dbspace use the -ef and -en options.

I usually use 5000 (5MB). Don't ask me why, but it should be enough.... and it's small enough to be irrelevant in terms of space saving.

The idea is that you can keep all your partition headers in the initial extent (on the first chunk)

Regards

_______________________________________________
Informix-list mailing list
Inform...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

[howi...@gmail.com]

thanks all I have dropped the dbspace.....feel a bit daft but what's new eh?