Starting a Transaction Engine

Having created an archive, a database, and started a Storage Manager (SM), you may start a Transaction Engine (TE) using the start process command.

nuocmd start process --db-name <database name> --engine-type TE --server-id <server ID>
The start process command is used to explicitly start one or more TEs. You can also start one or more TEs implicitly using the start database command. For more information, see Restarting a Database. The start process command and the start database command are issued using NuoDB Command (nuocmd). For more information on NuoDB Command and other command line tools, see Command Line Tools.


This section describes parameters that can be provided when starting a TE.

Parameter Description Comments


The database name associated with the archive previously created.

For more information, see Creating an Archive.


The type of process to be started.

TE is case-sensitive.


The unique ID for the admin process on the host machine (where the archive exists).



Starts the database with the database options provided.

Separate options values and options using a space character. For more information about the available database options, see Database Options.


The following example shows how to start a TE on the same server as the SM.

nuocmd start process --db-name hockey --engine-type TE --server-id nuoadmin-0
Process(db_name=hockey, durable_state=REQUESTED, engine_state=UNKNOWN, engine_type=TE,
labels={}, options={log-over-conn: enable, verbose: error,warn, database: hockey,
region-name: Default, engine-type: TE, geo-region: 0, commit: safe}, region_name=Default, server_id=nuoadmin-0, start_id=2)

The start process command documented here specifies:
- The name of the database where the TE is to be started (hockey).
- The type of process to be started (TE).
- The NuoDB Admin server where the TE is to started (nuoadmin-0).

The command output includes a non-configurable option log-over-conn.