>The problem we run into is that some tables fail to import due to
>unavailability of large contigious extents. We try to create these
>tables after having droped them specifying storage parameters like (
>initial and next sizes) . But problem occurs with another table.
>
>Is there better way to achive out goal of providing backup copy of
>prodn. data ( also the flexibility of refreshing individual tables)
>
The best way requires interaction.
you should re-build the database from scratch by creating it and all it's
tablespaces, etc.
Or you could have the development database GIANT!!!
Dropping tables should put your free blocks back together again in 7.1.6,
but there must be some other fragmentation that is preventing this.
--
=========================================================
http://www.li.net/~gsa/index.html
This is my signature file, not part of this mail message.
Received on Fri Jan 10 1997 - 00:00:00 CST
