I understand that enhancements have been made to V10 so that you can
control the tblspace tblspace and thereby reduce some of the situations
which lead to not being able to drop a chunk. But is that all
situations? What about if some extents of one of the system catalog
tables are in the chunk concerned?

I am wondering if a better solution to this problem would be to add a
FORCE option to dropping a chunk whereby any extents of tables
currently in the chunk would be relocated to another chunk of the
dbspace - if space is available.

Would this group support a feature request to change functionality in
this way.

regards

Malcolm