
Conductor Script Commands
The StartEngine command includes a number of start options that create new engine database tables:
Table
Option | Description |
|
|
newLog | New history log database tables are created during the primary |
| engine unit startup process. All history log information stored in |
| an existing database is lost. |
newState | New current state database tables are created during the primary |
| engine unit startup process. All current state information stored in |
| an existing database is lost. |
newRegistration | New registration database tables are created during the primary |
| engine unit startup process. All registration information stored in |
| an existing database is lost. You must also specify newState |
| when you specify the newRegistration option. |
cold | All new database tables (log, state, and registration) are created |
| during the primary engine unit startup process. The cold option |
| must always be used the first time an engine is started. If used in |
| subsequent engine starts, however, the cold option will cause |
| deletion of the existing engine database before the creation of the |
| new one. All current state information, history log data, and |
| registration information stored in an existing database is lost. |
|
|
The newLog, newState, and newRegistration options are independent, except that you cannot create new registration tables without also creating new state tables.
The ShowStatus Script command can be used to check that the engine has started up properly.
StartGovernor
The StartGovernor command starts the governor for the current engine.
StartGovernor
The StartGovernor command is available only when an engine is current, so you must first use the FindEngine Script command to set the current engine.