Consultor Eletrônico

How PROSHUT works in V6

When you shut down a database, the proshut utility prompts connected
processes to disconnect themselves from the database. Any active
transactions are backed out before the disconnect occurs. This might
take time depending on the number of transactions and the amount of
work that has to be undone. Even if it works correctly, shut down is
not instantaneous. If there are many users and the transactions are
long, it might take 15 minutes or more.

Once the shutdown begins, the broker waits for all the connected
processes to finish backing out and disconnecting from the database.
Then, the broker flushes any memory-resistant BI, AI, and database
buffers; writes the "Multi-user session end" message to the log file;
closes the database; and deletes shared memory, semaphores, and the
lock file. Finally, it exits.

In Release 6.3, there is an "Emergency Shutdown" option to the
proshut shutdown menu. Unfortunately, it is not accessible from
the command line. This option forces a crash. It marks shared memory
as suspect and signals all connected processes to disconnect. If any
processes are still connected after 10 seconds, it destroys them
(like kill -9 does). Then shared memory, semaphores, and the lock
file are deleted.

In Release 6.3D and later, the proshut utility is changed so that if
you use "proshut demo -F -by" , it forces a shutdown by invoking the
emergency shutdown option. "proshut demo -F" prompts you for
confirmation before doing shut down.

Note: 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 causes crash recovery to be
skipped and this might damage the database.

Progress Software Technical Support Note # 12378