Kbase P20738: How is the Progress Database shut down?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/3/2008 |
|
Status: Verified
GOAL:
How Progress shuts down the database
GOAL:
About shutting down Progress databases
GOAL:
How does the _mproshut process execute shutdown of the database?
GOAL:
What happens when proshut is issued against the database?
FACT(s) (Environment):
UNIX
FIX:
When the database is shut down - 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 or waiting on locks held by other processes. Please refer to Solution P3222, "What happens during proshut -by and proshut -F?"
Once the shutdown has begun, the broker waits patiently for all the connected processes to finish backing out before disconnecting from the database. Once this is completed, the broker:
+ flushes any memory-resident before-image, after-image, and database buffers to disc,
+ 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.