KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Nick Vigilante — Tue, 10 Apr 2018 11:14:25 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 4/10/2018 11:14:25 AM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected (since the repair script truncates invalid transactions), so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Warning: Renaming .kdb files is not supported beyond what is documented in Appian documentation, the Appian Playbook, and KB articles.

Affected Versions

This article applies to versions 17.2 and earlier.

Last Reviewed: April 2018

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Nick Vigilante — Tue, 10 Apr 2018 09:58:08 GMT

Revision 6 posted to Appian Knowledge Base by Nick Vigilante on 4/10/2018 9:58:08 AM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected (since the repair script truncates invalid transactions), so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Warning: Renaming .kdb files is not supported beyond what is documented in Appian documentation, the Appian Playbook, and KB articles.

Affected Versions

This article applies to versions 17.2 and earlier.

Last Reviewed: December 2017

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Parmida Borhani — Wed, 06 Dec 2017 17:51:25 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 12/6/2017 5:51:25 PM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected (since the repair script truncates invalid transactions), so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Warning: Renaming .kdb files is not supported beyond what is documented in Appian documentation, the Appian Playbook, and KB articles.

Affected Versions

This article applies to versions 17.2 and earlier.

Last Reviewed: December 2017

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Parmida Borhani — Wed, 15 Nov 2017 01:13:16 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 1:13:16 AM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected (since the repair script truncates invalid transactions), so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Warning: Renaming .kdb files is not supported beyond what is documented in Appian documentation, the Appian Playbook, and KB articles.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2017

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Nick Vigilante — Wed, 12 Jul 2017 08:44:35 GMT

Revision 3 posted to Appian Knowledge Base by Nick Vigilante on 7/12/2017 8:44:35 AM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected (since the repair script truncates invalid transactions), so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2017

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Nick Vigilante — Tue, 11 Jul 2017 10:42:49 GMT

Revision 2 posted to Appian Knowledge Base by Nick Vigilante on 7/11/2017 10:42:49 AM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped.
Rename the .repaired file to a higher numbered KDB. For instance, if the file is named pe445.kdb.repaired, you can rename it to pe446.kdb or pe500.kdb. Just ensure that the repaired KDB is the highest numbered KDB in the list for that engine. In most instances, the .repaired file will be missing data as expected, so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, engines, scripts

KB-1211 "Inconsistent DBID on GW1" error thrown in checkengine script

Nick Vigilante — Mon, 06 Mar 2017 20:47:12 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/6/2017 8:47:12 PM

Symptoms

One or more Appian engines fail to start. The output of checkengine.(bat|sh) shows the following:

Inconsistent DBID on GW1. Server Database ID: XXXX, Gateway Database ID: ON

Cause

If this is a migration, this error indicates the environment was not fully stopped before copying the engine database files *.kdb to the new Appian version.

For other scenarios where there’s no migration involved, the root cause is usually that Appian was shut down incorrectly or suddenly without completing the checkpoint.

Action

If this is not the result of a migration, perform the following:

Stop Appian per Starting and Stopping Appian.
REQUIRED: If running Appian 16.2 or 16.3, apply the latest hotfix.
Run the repair script located in <APPIAN_HOME>/server/_scripts/tools to fix the .kdb files for those engines with issues. Note: If the repair script successfully identifies that a KDB is in need of repair, it will create a .repaired file, which is the original file with some transactions dropped. It will not remove the original file. In most instances, the .repaired file will be missing data as expected, so the new KDB will need to be tested for integrity.
Start Appian. Run checkengine.(bat|sh) to ensure the engine starts up successfully.

For migrations, the solution is to fully stop the source environment with stop-suite.(bat|sh) and perform the migration again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: administration, engines, scripts