• State Suggested Answer
  • Replies 26 replies
  • Answers 2 answers
  • Subscribers 7 subscribers
  • Views 11443 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Hi, I have the message below starting the engines. Collabo

vsebastiao
Hi,

I have the message below starting the engines.

Collaboration Statistics 1/1 FATAL! No gateway is active.
Inconsistent DBID on GW1
Server Database ID: 3673, Gateway Database ID: 0N

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

Process-Exec00 1/1 FATAL! No gateway is active.
Inconsistent DBID on GW1
Server Database ID: 3293, Gateway Database ID: 0N

What can I do?

Thanks.

OriginalPostID-215548

OriginalPostID-215548

  Discussion posts and replies are publicly visible

  • 0
    for each engine there is a specified database ID. Go to respective engine folder (eg:%appian%\server\process\exec\02\*.kdb) delete all the kdb files after server database ID . After deleting it, start the appian server, it will create new checkpoint which should cause creating of new KDB file. Test it for one engine if it works then do it for all the engine.
  • 0
    A Score Level 2
     in reply to Rama Thummala
    @sonamg - Can you please check the kdb files available in all the folders in new Appian installation. Ideally there should be only one kdb file after upgrade steps are finished. For e.g. If old Appian kdb number is 15 then there must not be a kdb in new installation with version number 1. We had faced this kind of issue previously. We reinstalled Appian and upgraded before starting Appian engines. Hope this helps.
  • 0 in reply to sagarl511
    we have 3 KDBs files in each folder after installing the server again and starting the checkengine but we want to transfer old kdb files from previous version for recovering the data. After transferring old KDB files Engines stop working.
  • 0
    A Score Level 2
     in reply to sonamg
    Have you performed following steps -
    1) Install fresh Appian and do not start Appian engines yet
    2) Copy the latest kdb from each folder as mentioned in Migration procedure.
    3) Now start Appian engines and see if it is working.

    Another diagnostic if above does not work.
    1) See the latest version number of kdbs in folder in old installation
    2) Perform checkpoint on old Appian version and now see if version number is increased. If not increased then there is issue with your old server.
  • 0 in reply to sonamg

    in your engine gateway folders there will be a kdb file with incremental number , and when you run checkengine.bat for each engine,it will provide a number  which has last successful kdb recorded in primary table. if you delete the kdb with higher number , it should be able to map with correct kdb.

    for example: consider personalisation, if  engine fails and it will throw "Inconsistent DBID on GW1

    Server Database ID: 200 . Goto respective engine gateway folder. there should be something like ag1.kdb, check for kdb file with maximum number or recently created. for example ag202.kdb , delete the kdb files after 200 which is ag201.kdb and ag202.kdb , where the maximum kdb should be same as value available in transition table. if the recent kdb created is less than transition table number then rename the last working kdb with that number present transition . 

© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.