Kbase 10161: Proshut can be used with -F option Emergency Shutdown 6.3+
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Proshut can be used with -F option Emergency Shutdown 6.3+
891207-dah06For situations where "proshut <dbname> -by" hangs, we have implemented
an emergency shutdown option that will bring down the broker and clean
up shared memory for you.
The emergency shutdown option should be used for versions 6.3 and
higher instead of the newshut script that is provided by Progress
Technical Support. For version 6.2 and earlier, the shutdown scripts
are the only alternative to doing this manually.
One thing to remember about shutting down databases: proshut
** requests ** a shutdown by asking connected processes to disconnect
themselves from the database. Any active transactions are backed out
BEFORE the disconnect occurs. This may take some time, depending on
how many transactions there are, and how much work has to be undone.
Consequently, shutdown is not usually instantaneous. With many users,
it may take a few minutes, maybe as long as 15 or more if the
transactions are long.
Once the shutdown has begun, the broker patiently waits for all the
connected processes to finish backing out the disconnecting from the
database. Once this is completed, the broker flushes any memory-
resident before-image, after-image, and database buffers, writes
the "Multi-user session end" message to the log file, closes the
database, deletes shared memory and semaphores, and deletes the lock
(.lk) file. Then it finally exits.
In version 6.3, we added an "Emergency Shutdown" option to the
proshut shutdown menu. This option is accessible from the command
line in versions 6.3E and higher. For versions prior to 6.3E the
emergency shutdown can be accessed from the command line by
redirecting the input it is requesting. The syntax is as follows:
Versions prior to 6.3E: (echo 3 ; echo y) | proshut <dbname>
Versions 6.3E+: proshut <dbname> -F (will prompt for confirmation)
proshut <dbname> -F -by (won't prompt for confirmation
It marks shared memory as suspect and signals all connected processes
to disconnect. Then it will begin to kill the broker process,
beginning by sending a kill -15, and if that still fails, it will
send a kill -9. Once the broker is down, the emergency shutdown
option then cleans up shared memory. At this point, the database is in
a crashed state so that you will need to go through bi crash recovery.
If you are running the shutdown from a script with the intention of
starting a backup and this process is unattended, you can issue the
command to truncate the bi file before starting the backup.
Truncating the bi file will begin by performing crash recovery
and rolling out any incomplete transactions. This will leave the
database in a clean state for backup.
NOTE THAT THE -F OPTION IN PROSHUT IS ENTIRELY DIFFERENT FROM THE -F
OPTION IN OTHER MODULES (and has been for some time). "-F" used with
other modules will cause crash recovery to be skipped and this may
damage the database.
Progress Software Technical Support Note # 10161