Stopping the Database
There are many occasions when you must stop a database, for example, before an upgrade or performing various maintenance tasks. You can stop a running database through one of the following:
You cannot stop a running database if any users are connected or Database Designer is building or deploying a database design.
If the Tuple Mover is doing a Moveout operation then the database cannot stop until the Moveout is complete. If the database is not stopping after you issue a stop command then you can verify a Moveout operation is preventing the database from stopping by looking at the Vertica log file. See Monitoring Log Files for details on locating and viewing the Vertica log. Tuple Mover operations that are in progress display an INFO message:
[Session] <INFO> closeAndWaitAllSessions: waiting for session to end. The database will stop after the Moveout completes, you do not need to take additional action other than waiting.
To stop a running database with admintools:
- Verify that all cluster nodes are up. If any nodes are down, identify and restart them.
- Close all user sessions:
- Identify all users with active sessions by querying the
SESSIONSsystem table. Notify users of the impending shutdown and request them to shut down their sessions.
- Prevent users from starting new sessions by temporarily resetting configuration parameter MaxClientSessions to 0:
=> ALTER DATABASE mydb SET MaxClientSessions = 0;
- Close all remaining user sessions with Vertica functions
You can also force a database shutdown and block new sessions with the function
- Select Stop Database
- Click OK
You can stop a database with the command line tool
$ /opt/vertica/bin/admintools -t stop_db -d db-name [-p password] [-F]
Use the option
--force) to override all user connections and force a shutdown.