While starting Appian Engines do we need to do checkpoint first before starting Appian Engines for the proper startup ?

If there was an unexpected shutdown, the Appian engines will replay transaction once you start the environment again. This increases the start-up time.

Once everything starts, and checkengine shows Okay for all engines, run a proper shutdown with stop-suite so mimic a checkpoint. This is better than just a checkpoint to get an accurate sense of the memory usage by booting engines without transactions to replay.

You can't do a checkpoint if the engines are not running.

Thanks for the quick response.

From the above mentioned scenario , once the server is back after shutdown.

While starting Appian Engines using start suite , some of the engines not coming up and it says checkpoint recommended.

But even after doing check point some of the engines not coming up with the message below .

---------------------------------------------------------------------------

Notifications Email Processor 0/1 * FATAL! No gateway is active.

Portal 1/1 FATAL! No gateway is active.
Checkpointing recommended
Inconsistent DBID on GW1. Server Database ID: 6705, Gateway Database ID: 0N

Process-Analytics0000 1/1 FATAL! No gateway is active.
Checkpointing recommended
Inconsistent DBID on GW1. Server Database ID: 17, Gateway Database ID: 0N

The relevant error will be:

Inconsistent DBID on GW1. Server Database

What you want to do is:

1. Takes notes on the engines showing FATAL
2. stop-suite
3. Make sure no k.exe process remains active. If one remains but is not using CPU, kill it
4. Use <APPIAN_HOME>\\server\\_scripts\          ools\\repair passing the full name with path included of the latest engine database file *.kdb for the engine to repair
5. Rename the .repaired file to be the highest numbered one

Alternatively if you are able to raise support cases on your customer's behalf, you can work with Appian Support on this.

Thanks Eduardo for you support.