LUW/8.1.6

dropped a table at the behest of others. turned out it was
in use. the drop seemed to go normally, and the table
disappeared from the displays (control center and aqt), but
the CREATE hung. hmmm. i didn't know about in-use yet.

so i did a Database Restart. same thing.

so i RTFM, and found Quiesce. what the hell, why not? then
the CREATE went fine.

Question: why does Restart not disconnect? seems backasswards
in terms engine functionality hierarchy; Quiesce being less
drastic than Restart. one of those quirks i'm likely to
remember, but it is a puzzlement.

btdb

BobTheDatabaseBoy wrote:
> LUW/8.1.6
>
> dropped a table at the behest of others. turned out it was
> in use. the drop seemed to go normally, and the table
> disappeared from the displays (control center and aqt), but
> the CREATE hung. hmmm. i didn't know about in-use yet.
>
> so i did a Database Restart. same thing.
>
> so i RTFM, and found Quiesce. what the hell, why not? then
> the CREATE went fine.
>
> Question: why does Restart not disconnect? seems backasswards
> in terms engine functionality hierarchy; Quiesce being less
> drastic than Restart. one of those quirks i'm likely to
> remember, but it is a puzzlement.

RESTART DATABASE causes a database to perform crash recovery, and
has nothing to do with restarting the database instance. This can
be done while users are connected to the database (although any
in-flight transactions will be rolled back).

I can't be sure, but I suspect that one connection to the database
had a catalog lock which was holding up the CREATE TABLE.


Good luck,