Page tree
Skip to end of metadata
Go to start of metadata

Summary: This documentation explains what to do when CAST Management Studio detects (on launch) an inconsistency between the schemas within a combined installation (otherwise known as a "triplet") and how to avoid this situation from occurring.

Introduction

When CAST Management Studio is launched and a connection is opened to a Management schema, a series of checks are run to ensure that the associated Analysis and Dashboard schemas are consistent with what is recorded in the Management schema. If any inconsistencies are detected, then an error will be displayed during the connection process in the CAST Management Studio and the connection will be cancelled, for example:

ERR: 2020-05-27 16:21:05:	cast.pmc.startup.wrongconsistencydata
ERR: 2020-05-27 16:21:05:	Incorrect data consistency between databases. Check CAST-MS log file for more details. CAST-MS could not be launched.
							com.castsoftware.java.ExternalException:Incorrect data consistency between databases. Check CAST-MS log file for more details. CAST-MS could not be launched.

Preventing a connection to a "triplet" which contains inconsistencies is expected behaviour since using the triplet in an inconsistent state can lead to:

  • a crash when saving the results of an analysis in the Analysis schema
  • loss of data in the Analysis schema (objects, modules, links)
  • objects changing types and technology in the Dashboard schema

Technical explanation

Inconsistencies usually occur when manual operations are actioned with regard to the individual schemas, for example:

  • tweaking the Management schema
  • restoring only a single schema (for example just the Dashboard schema)

These inconsistencies are due to the way synchronization is achieved between the various "triplet" schemas, by using ID translation tables:

  • With regard to the Management schema, the CMS_Sync_Translation table holds the IDs of objects belonging to the Analysis schema, or to the Dashboard schema: if the Analysis schema or the Dashboard schema is restored in an older state, when less objects have been created, then, for all the objects created again, but sharing the IDs of the already created objects, inconsistencies will occur in the Analysis schema/Dashboard schema.
  • With regard to the Analysis schema, the DSS_KeysExtra, DSS_Transaction, DSS_DataFunction, etc. tables hold the IDs of objects belonging to the Management schema: if the Management schema is restored in an older state, when less objects have been created, then, for all the objects created again, but sharing the IDs of the already created objects, inconsistencies will occur in the Management schema.
  • With regard to the Dashboard schema, the DSS_TRANSLATION_TABLE table holds the IDs of objects belonging to the Analysis schema: if the Analysis schema is restored in an older state, when less objects have been created, then, for all the objects created again, but sharing the IDs of the already created objects, inconsistencies will occur in the in the Dashboard schema.

Common scenarios and what you should do

Single schema is restored in a state incompatible with the state of the other schemas

Restoring a single schema is not supported by CAST. You should always restore the triplet as a whole (i.e. all three schemas).

Need to install a new Analysis schema in an existing triplet for your Application

If you need to install a new Analysis schema in an existing triplet, replacing the existing Analysis schema, please use these steps:

  • In the CAST Management Studio, unregister both the Analysis and Dashboard schemas from the Application:
Unregister Analysis schema

Click to enlarge

Unregister Dashboard schema

Click to enlarge

  • Close CAST Management Studio
  • Drop the Analysis schema in CAST Server Manager or PGAdmin
  • Create and install the new Analysis schema with CAST Server Manager using the Additional Knowledge Base option
  • Open CAST Management Studio
  • Register the new Analysis schema, and the existing Dashboard schema, into the same Application:
Register the new Analysis schema

Click to enlarge

Register the new Dashboard schema

Click to enlarge

Need to install a new Dashboard schema in an existing triplet

If you need to install a new Dashboard schema in an existing triplet, replacing the existing Dashboard schema, please use these steps:

  • In the CAST Management Studio, unregister the Dashboard schema from the application
Unregister Dashboard schema

Click to enlarge

  • Close CAST Management Studio
  • Drop the Dashboard schema in CAST Server Manager or PGAdmin
  • Create and install the new Dashboard schema with CAST Server Manager using the Additional Central Base option
  • Open CAST Management Studio
  • Register the the new Dashboard schema, into the same Application
Register the new Dashboard schema

Click to enlarge

Need to install both a new Analysis schema and a new Dashboard schema in an existing triplet

If you need to install both a new Analysis schema and a new Dashboard schema in an existing triplet, replacing the existing schemas, please use these steps:

  • In the CAST Management Studio, unregister both the Analysis and Dashboard schemas from the Application:

Unregister Analysis schema

Click to enlarge

Unregister Dashboard schema

Click to enlarge

  • Close CAST Management Studio
  • Drop the Analysis schema in CAST Server Manager or PGAdmin
  • Drop the Dashboard schema in CAST Server Manager or PGAdmin
  • Create and install the new Analysis schema with CAST Server Manager using the Additional Knowledge Base option
  • Create and install the new Dashboard schema with CAST Server Manager using the Additional Central Base option
  • Open CAST Management Studio
  • Register the the new Dashboard schema, and the new Analysis schema into the same Application
Register the new Analysis schema

Click to enlarge

Register the new Dashboard schema

Click to enlarge

  • No labels