Consultor Eletrônico

Emergency Shutdown with proshut dbname -by -F

WHY YOU NEED TO KNOE THIS:
=========================
You may want to issue an emergency batch shutdown before doing
progress backup of a database to insure that all processes attached to
it are killed, shared-memory segments, semaphores and .lk files are
deleted. You could also issue emergency shutdown in situation where
the proshut command seems to be hanging for whatever reason.

SUMMARY:
=======

The -F option in proshut is entirely different from the -F option
in other modules. F used with other modules causes crash recovery to
be skipped and this might damage the database.

This is what happens when you do an Unconditional batch shutdown -by:

If there are any processes left after:
30 Secs. - wake up clients waiting for locks.
60 Secs. - wake up clients waiting for locks.
90 Secs. - wake up clients waiting on screen input.
5 Minutes - Resend the shutdown signal to remaining clients.
10 Minutes - Send a terminate (SIGTERM) signal to remaining clients.

If you do an Emergency Shutdown with -by -F:

Proshut sets the emergency shutdown flag in shared memory.
Proshut kills the broker (kill -9)
Proshut sends the shutdown signal to all connected processes and waits
10 seconds.
Proshut kills all remaining clients (kill -9).
Proshut removes shared memory, marks the database as crashed, and remo
ves the dbname.lk file.

Progress performs normal crash recovery when you restart your
database after the emergency shutdown and backs out any active transac
tions.

KDA 05/10/1999

REFERENCES TO WRITTEN DOCUMENTATION:
====================================

Progress System Administration Guide & Reference