Hi Frank,

By default, ingstop will detect that users are still connected to
the DBMS Server and pause, wait a bit, then if they are still connected
will fail gracefully.

You can specify some options to the ingstop to make it get very
brutal and force the shutdown. I presume these are reasonably safe.
ingstop -f is reasonably brutal.
ingstop -force
ingstop -immediate

Check the manual for what they can do.

The remove sid command should work. There have been some
problems in the past. But if the session persists it may have gone into a
rollback and you will just have to wait for it all to be cleaned up by the
recovery process. You can do a format sid and see what the process
status is to find out.

Also check the recovery process itself and see if its doing
anything.

If you are not prepared to wait and need to get the system
down immediately, you can also use the 'STOP SERVER' command in
iimonitor. On startup, the recovery process will do what it needs to do -
and probably faster.

Martin Bowes
--
Random Farscape Quote #3:
John - If this is part of some sick experiment, I'm going to bill them for
the therapy.