Open topic with navigation
This page describes how to prepare your database for running the NuoDB Check utility. To run NuoDB Check, you must do the following:
nuodb [domain] >
show domain summaryHosts: [broker] * ec2-54-149-94-33.us-west-2.compute.amazonaws.com/220.127.116.11:48004 (us-west-2) [broker] ip-172-31-5-193/18.104.22.168:48004 (us-west-2) Database: test, (unmanaged), processes [2 TE, 2 SM], ACTIVE [SM] ip-172-31-2-230/22.214.171.124:48005 (us-west-2) [ pid = 27068 ] [ nodeId = 1 ] RUNNING [TE] ip-172-31-2-230/126.96.36.199:48006 (us-west-2) [ pid = 27090 ] [ nodeId = 4 ] RUNNING [TE] ip-172-31-5-193/188.8.131.52:48005 (us-west-2) [ pid = 24596 ] [ nodeId = 2 ] RUNNING [SM] ip-172-31-5-193/184.108.40.206:48006 (us-west-2) [ pid = 24613 ] [ nodeId = 3 ] RUNNING nuodb [domain] >
disable enforcer database testnuodb [domain] >
yesShutdown even if database would become non-durable (optional): Timeout (ms/s/m/h/d/w) (optional): Remote process shutdown timeout (ms/s/m/h/d/w) (optional): Process shutdown cleanly
Note: Disabling of enforcement is only required if running Managed databases, a feature that was deprecated in v3.0. See Disabling Enforcement for instructions on how to do this.