At 03:11 PM 16/08/2004 +1200, you wrote:

>Hi All
>
>I am doing a DROP Table xxxx; SQL which is failing because the table is in
>use, assumably somewhere else in my application. What's the easiest way
>of identifying the culprit ?

You can't. If you're in a multi-user environment, perform and complete a
database shutdown before you start messing with metadata. If it's just
you, look around the tools you are using and close any windows that are
querying tables, e.g. the data browser in IB_SQL.

If you're trying to drop a table that was used by a stored procedure,
you'll need to log everyone out, including the sysdba, because the server
caches SPs.

Helen