KB-1419 Negative KDB numbering

Jordan Horwat — Mon, 23 Jul 2018 13:03:13 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 1:03:13 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the names of actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Check that all KDB file names look normal - i.e. no remaining negative numbers or manually introduced KDBs such as pe.kdb.
Start the engine and confirm that KDB numbering is positive once 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 self-managed versions of Appian.

Last Reviewed: November 2017

Tags: engines, infrastructure

KB-1419 Negative KDB numbering

Parmida Borhani — Wed, 15 Nov 2017 06:10:36 GMT

Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 6:10:36 AM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the names of actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Check that all KDB file names look normal - i.e. no remaining negative numbers or manually introduced KDBs such as pe.kdb.
Start the engine and confirm that KDB numbering is positive once 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 on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1419 Negative KDB numbering

Tom Ryan — Wed, 15 Nov 2017 00:54:52 GMT

Revision 17 posted to Appian Knowledge Base by Tom Ryan on 11/15/2017 12:54:52 AM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the names of actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Check that all KDB file names look normal - i.e. no remaining negative numbers or manually introduced KDBs such as pe.kdb.
Start the engine and confirm that KDB numbering is positive once 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 on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1419 Negative KDB numbering

Tom Ryan — Wed, 15 Nov 2017 00:54:29 GMT

Revision 16 posted to Appian Knowledge Base by Tom Ryan on 11/15/2017 12:54:29 AM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the filenames of actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Check that all KDB file names look normal - i.e. no remaining negative numbers or manually introduced KDBs such as pe.kdb.
Start the engine and confirm that KDB numbering is positive once 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 on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1419 Negative KDB numbering

Parmida Borhani — Wed, 15 Nov 2017 00:29:42 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 11/15/2017 12:29:42 AM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Check that all KDB file names look normal - i.e. no remaining negative numbers or manually introduced KDBs such as pe.kdb.
Start the engine and confirm that KDB numbering is positive once 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 on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1419 Negative KDB numbering

Parmida Borhani — Tue, 14 Nov 2017 17:58:25 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 11/14/2017 5:58:25 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Start the engine and confirm that KDB numbering is positive once again.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

This article applies to all on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Nick Vigilante — Tue, 14 Nov 2017 08:34:31 GMT

Revision 13 posted to Appian Knowledge Base by Nick Vigilante on 11/14/2017 8:34:31 AM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_*.log
the DB ID referenced in the corresponding db_*.log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001*.log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001*.log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Start the engine and confirm that KDB numbering is positive once again.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

This article applies to all on-premise versions of Appian.

Last Reviewed: November 2017

Tags: engines

KB-XXXX KDB numbering goes negative

Parmida Borhani — Tue, 14 Nov 2017 01:16:39 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 11/14/2017 1:16:39 AM

To correct it, I think shutting down the engine and then renaming the kdbs to positive numbers (making sure the most recent is highest of course) is sufficient.

Also, if you're currently running on a negative numbered kdb, you should immediately make sure that there are no positive numbered kdbs in the gw directory. The usual "highest number kdb" rules still apply, so we want to make sure any restart would select the kdb you're currently writing to.

I believe this issue can occur after improperly resetting a particular engine's KDBs.

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:22:03 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:22:03 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_ log
the DB ID referenced in the corresponding db_ log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001 log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001 log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename any negative KDBs to positive numbers, ensuring that the most recent KDB has the highest number.
Start the engine and confirm that KDB numbering is positive once again.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:21:13 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:21:13 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_ log
the DB ID referenced in the corresponding db_ log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001 log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001 log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename the negative KDB to a positive number, ensuring that the most recent KDB has the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:20:27 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:20:27 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_ log
the DB ID referenced in the corresponding db_ log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001 log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001 log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename the negative KDB to a positive numbers, ensuring that the most recent KDB has the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:19:56 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:19:56 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_ log
the DB ID referenced in the corresponding db_ log

For example, if the process execution01 engine is the one in question, you may notice the following:

A negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/: pe-2147483646.kdb.
A reference in the gw_PX001 log: [PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646".
A reference in the db_PX001 log: [PX001] {pe-2147483646.kdb ,4405}.

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename the negative KDB to a positive numbers, ensuring that the most recent KDB has the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:16:46 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:16:46 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk
the checkpointing messages in the corresponding gw_ log
the DB ID referenced db_ log

For example, if the process execution01 engine is the one in question, you would notice a negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/:

pe-2147483646.kdb

The gw_PX001 log will show something like this:

[PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646"

The db_PX001 log will show something like this:

[PX001] {pe-2147483646.kdb ,4405}

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename the negative KDB to a positive numbers, ensuring that the most recent KDB has the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 23:15:06 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 11:15:06 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may manifest in:

the actual .kdb files on disk (found in <APPIAN_HOME>/server/<ENGINE_NAME>/gw1/)
the checkpointing messages in the corresponding gw_ log (found in <APPIAN_HOME>/logs/)
the DB ID referenced db_ log (found in <APPIAN_HOME>/logs/)

For example, if the process execution01 engine is the engine in question, you will notice a negative .kdb file in <APPIAN_HOME>/server/process/exec/01/gw1/:

pe-2147483646.kdb

The gw_PX001 log will show something like this:

[PX001] INFO .a.gw.ssa "Server switchover to database ID -2147483646"

The db_PX001 log will show something like this:

[PX001] {pe-2147483646.kdb ,4405}

Cause

This issue can occur after improperly resetting a particular engine's KDBs or if extraneous KDB files are manually introduced.

Action

Shut down the engine with the negative KDB numbering.
Rename the negative KDB to a positive numbers, ensuring that the most recent KDB has the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 21:40:11 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 9:40:11 PM

Symptom

KDB file numbering for one or more engines moves into the negatives. This may show up in:

the actual .kdb files on disk
the corresponding db_ log
the corresponding gw log

For example, the .kdb file on disk is pe-2147483644.kdb and the negative DB ID is referenced in the corresponding db_ log.
In the gateway log we can see that the standard, positive integer numbering is being referenced and then in the next checkpoint, the negative numbering for the DB ID is called.

Cause

This issue can occur after improperly resetting a particular engine's KDBs. It can also happen if you introduce extraneous KDB files.

Action

Shut down the engine with the negative KDB numbering.
Rename the KDB to positive numbers, making sure the most recent is the highest number.

Note: If you are currently running on a negative numbered KDB, you should immediately make sure that there are no positive numbered KDBs in the gw directory. The usual "highest number kdb" rules still apply, so we want to make sure any restart would select the KDB you're currently writing to.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 21:36:00 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 9:36:00 PM

Symptom

KDB file numbering for one or more engines moves into the negatives.

Cause

This issue can occur after improperly resetting a particular engine's KDBs. It can also happen if you introduce extraneous KDB files.

Action

Shut down the engine with the negative KDB numbering.
Rename the KDB to positive numbers, making sure the most recent is the highest number.

Warning: Renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-1419 KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 20:25:15 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 8:25:15 PM

Symptom

KDB file numbering for one or more engines moves into the negatives.

Cause

I believe this issue can occur after improperly resetting a particular engine's KDBs.

Action

To correct it, I think shutting down the engine and then renaming the kdbs to positive numbers (making sure the most recent is highest of course) is sufficient.

We just need to add a boiler plate warning saying that renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-XXXX KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 20:23:52 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 8:23:52 PM

Symptom

KDB file numbering for one or more engines moves into the negatives.

Cause

I believe this issue can occur after improperly resetting a particular engine's KDBs.

Action

To correct it, I think shutting down the engine and then renaming the kdbs to positive numbers (making sure the most recent is highest of course) is sufficient.

We just need to add a boiler plate warning saying that renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines

KB-XXXX KDB numbering goes negative

Parmida Borhani — Mon, 13 Nov 2017 20:18:26 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 11/13/2017 8:18:26 PM

Symptom

Cause

I believe this issue can occur after improperly resetting a particular engine's KDBs.

Action

To correct it, I think shutting down the engine and then renaming the kdbs to positive numbers (making sure the most recent is highest of course) is sufficient.

We just need to add a boiler plate warning saying that renaming .kdb files is not supported beyond what is documented in this article.

Affected Versions

Last Reviewed: November 2017

Tags: engines