CMS Snapshot Analysis - Compute Snapshot - Fatal Error - Inconsistent Local Site

This page provides assistance for resolving the following error during the compute snapshot step.

Inconsistent local site: central contains objects which do not already exist on this local. This local site has certainly been reloaded from an old backup. Cannot compute snapshot.

This is also shown in the screenshot below:

1. Run Analyzer
2. Run Snapshot

Perform the below actions

1. Possible Solutions for this issue
   1. Backup the Managment / Local / Central schema
   2. This issue can be caused by just a KB (local database or knowledge base) dump being restored without restoring the central and management or an older KB dump being used instead of the most recent one. Restoring the proper dump/dumps can resolve this issue.
   3. Drop analysis results and run analysis+snapshot again has resolved this issue in some cases.
   4. Perform the following steps to create a new KB. Note that doing this will cause added/deleted objects on the first snapshot with the new KB.
      1. Drop the schema from postgres (drop schema <local KB> cascade;)
      2. Create a new general type KB in server manager with the same name
      3. Rediscover in CAST-MS
      4. Run full analysis and snapshot

   5. Modify the sequence or Parms table, depending on the database. X in the below mentioned queries have to be replaced by a number which is higher than the number obtained for Last Object_id in KB while getting the input from the user. For example, If the result is 10379217, then X can be 10379220 and X-1 would be 10379219.

      For Oracle: Modify the sequence IdKey_Generator 

      
              a. drop sequence IdKey_Generator
              b. create sequence IdKey_Generator start with X increment by 1 nomaxvalue cache 50 order
              c. insert into DSS_KeysExtra values ( X-1, 'dummy', 0, 0 )
      
         For SQL Server: Modify a value in the Parms table

      
             a. update Parms set IntVal = X where Lib = 'Id'
             b. insert into DSS_KeysExtra values ( X-1, 'dummy', 0, 0 )
      
       For CSS: Modify the sequence IdKey_Generator

      
              a. drop sequence IdKey_Generator
              b.create sequence idkey_generator increment 1 no minvalue no maxvalue start X cache 50
              c. insert into DSS_KeysExtra values ( X-1, 'dummy', 0, 0 )

2. Get Customer’s Input to confirm whether the local site is obsolete or the local is from an old dump. For this follow the below steps.

   1. Backup the Managment / Local / Central schema

   2. Ask the customer which local and central site they are pointing to.

   3. Ask the customer to execute the following queries and provide you with the result.

      1. Run the following queries on the CB:

         SELECT   SITE_ID,
                  MAX(SITE_OBJECT_ID)
         FROM     DSS_TRANSLATION_TABLE
         GROUP BY SITE_ID;

         SELECT *
         FROM   DSS_SITES;

      2. Run the following queries on the KB and provide the results:

         SELECT MAX(IdKey)
         FROM   Keys;

         SELECT MAX(Object_ID)
         FROM   DSS_KeysExtra;

         For Oracle: select idKey_Generator.nextval from dual
         For SQL Server: select IntVal from Parms where Lib = 'Id'
         For CSS: select nextval ('idKey_Generator')

   4. Extract the following information from the above queries
      1. Last site_object_id in CB: the value in the query above for Max(site_object_id) for the KB being used
      2. Last Object_Id in KB: The result of “select max(Object_ID) from KeysExtra” is the last Object_ID in KB.
         
      3. Next ID in sequence in KB - value from the nextval and/or intval query above
   5. If the next ID in sequence in KB is less than the last object site_object_id in the CB, then it confirms that the KB is from an old dump. The next ID in sequence in KB should also be greater than the last object_id in KB for internally consistency on the KB.

3. If the above steps do not solve your issue contact CAST Technical Support. with the following Relevant input for CAST Technical Support to  investigate

Relevant input

• Sherlock (CAST Support Tool (CST) - alias Sherlock) : Option to select are Export Logs, Export CAST bases and Export Configuration Files. Source code is not required since the application is already analyzed.

Ticket # 16851, 11764