Dropping a dbspace

We are using IDS 7.31. There are a couple of dbspaces that we don't use and do not reference. We would like to drop them, but an message tells us that the spaces are not empty and will not let us drop them. Any Solutions would be appreciated. Also, what is the best path using the onstat commands to determine a particular thread is causing a problem, not necessarly with locking but when the system load takes off and you need to determine which thread is hurting the system?

On Thu, 6 Jul 2000 23:31:17 -0400, "Calvin Shoults" <jcsatlcom.net@mindspring.com> wrote: >We are using IDS 7.31. There are a couple of dbspaces that we don't use and >do not reference. We would like to drop them, but an message tells us that >the spaces are not empty and will not let us drop them. >Any Solutions would be appreciated. drop any tables that are utilizing these dbspaces...but back them up first so that you may relocate them. > Mike South The BEST in adult Video www.mikesouth.com

Perform an "oncheck -pe > oncheckpe" and review the contents of the oncheckpe file. Each chunk/dbspace is listed within. Using this, you will be able to see what is preventing your drop. Take care. Clifton "Calvin Shoults" <jcsatlcom.net@mindspring.com> wrote in message news:8k3j7b$t42$1@slb6.atl.mindspring.net... > We are using IDS 7.31. There are a couple of dbspaces that we don't use and > do not reference. We would like to drop them, but an message tells us that > the spaces are not empty and will not let us drop them. > Any Solutions would be appreciated. > Also, what is the best path using the onstat commands to determine a > particular thread is causing a problem, not necessarly with locking but when > the system load takes off and you need to determine which thread is hurting > the system? > >