Obtaining Database Status Information Using Automation Console

In the Automation Console, to obatin database status, click Databases on the left side. This displays whether the database availability status is ACTIVE or INACTIVE and if the process requirements are UNMET. You can determine that a database is quiesced, if there is an unquiesce button. Likewise, if there is a quiesce button then the database is unquiesced. For example:

Click a database to obtain details about that database. In the database details page, you can see the dominant database status, which is ACTIVE in the following figure. In the green and orange bar, green represents the processes that currently have RUNNING as their status and orange represents all other processes. For example:

To obtain the status for each process, click Processes where it indicates 4 Processes in the previous figure. NuoDB displays information about each of the database's processes. In the following example, the status of each process is RUNNING:

In Automation Console and the REST API, it is a known limitation that process group names do not appear in runtime information displays. This is relevant only when you add a process group to a built-in template. If you add a process group then use the NuoDB Manager show database processes command to view the process configuration. Specify the user-data field so that you can see the group that each process belongs to. For example:

nuodb [domain] > show database processes database nuodb_system inclOptions user-data
[SM] Nuodb-2.local/192.168.2:60614 (us-west) [ pid = 35063 ] [ db = nuodb_system ] 
     [ nodeId = 1 ] [ user-data = reqGroupName=SMs ] RUNNING
[TE] Nuodb-2.local/192.168.2:60616 (us-west) [ pid = 35064 ] [ db = nuodb_system ] 
     [ nodeId = 2 ] [ user-data = reqGroupName=TEs ] RUNNING
[SM] Nuodb-1.local/192.168.1.102:60762 (us-west) [ pid = 35073 ] [ db = nuodb_system ] 
     [ nodeId = 3 ] [ user-data = reqGroupName=SMs ] RUNNING
[TE] Nuodb-1.local/192.168.1.102:60766 (us-west) [ pid = 35074 ] [ db = nuodb_system ] 
     [ nodeId = 4 ] [ user-data = reqGroupName=TEs ] RUNNING