Open topic with navigation
This is a NuoDB Manager command. See NuoDB Manager.
Restart a database based on a captured database configuration file. (See Capture Database.)
Note: To stop and restart a database, simply use the NuoDB Manager
shutdown database and
restart database commands.
Note: Even when a TE process host is unreachable, it will be skipped and the Restart command will still restart the database as long as all SM processes specified in the capture file are reachable.
See the following:
restart database dbFile
file_name[timeout timeout_value] [incremental false]
Amount of time to wait for the
restart database command to complete. A value of 0 means NuoDB Manager does not wait. The default timeout is the value of the NuoDB Manager property,
restartTimeout. Specify a timeout value in milliseconds, seconds, minutes, hours, days or weeks and append the appropriate suffix:
These are the incremental restart option values. The default is false. When incremental is specified the operation will add missing engines specified in a capture file. Starting these engines follows storage group ordering. SMs are uniquely identified by their host and archive path. Transaction engines are identified by the full set of options. No engines are ever shut down when incremental is specified.
test based on a capture file called
mydb.cfg. This database has 1 TE and 1 SM.
nuodb [domain/test15] >
restart databaseDatabase Description File:
mydb.cfgTimeout (ms/s/m/h/d/w) (optional): Re-starting database: test Started: [SM] ip-172-31-14-171/220.127.116.11:48007 (us-west-2) [ pid = 4720 ] [ db = test15 ] [ nodeId = 1 ] ACTIVE Started: [TE] ip-172-31-14-171/18.104.22.168:48008 (us-west-2) [ pid = 4740 ] [ db = test15 ] [ nodeId = 2 ] ACTIVE
restart database command can be executed with
--command as follows:
password\ --command "restart database dbFile mydb.cfg"
database test \ host localhost \ options '--dba-user dba --dba-password goalie'"