CAST AIP Troubleshooting Guides
Page tree
Skip to end of metadata
Go to start of metadata
Description

Assuming you are performing the following step by step scenario:

  1. Create fresh triplet. Let's call central schema = CB (Dashboard Service database), Knowledge Base schema = KB (Analysis Service database)., management schema = MNGT (Management Service database)
  2. Take a backup of the KB or CB.
  3. Perform analysis and snapshot for version V1.

  4. Restore the KB or CB with the same identification id. 

  5. Synchronize the restored schema to have a connected triplet.
  6. Perform analysis and snapshot for version V2.

This is a bad practice that creates inconsistencies between module IDs stored in the management base and central schema or knowledge base. Therefore modules cannot be correctly located during synchronization. The consequences of this bad practices are irreversible. we propose partial remediation that will help you to avoid the impacts that you will come across after the future generation of snapshots. Please note that:

  1. If the problem is due to the restored central schema, you will lose all the results of your previous snapshots, you will preserve only the configuration and the current analysis results
  2. If the problem is due to the restored knowledge base, you will lose all the results of your analysis as well as your previous snapshots, only configuration will be preserved.

In the following sections we expose the Symptoms of the bad practices,Partial remediation for this irreversible bad practice, and Impacts of the partial remediation.

Symptoms

Case 1: If the restored schema is the Central schema

Some violations may appear on objects belonging to another technology (or on different objects belonging to the same technology).

Case 2: If the restored schema is the Knowledge base schema

If the restored schema is the KB  this will lead to the following symptoms:

  1. Inconsistency between IFPUG module IDs in central and local databases. Therefore, the IFPUG module cannot be correctly located in the KB, and the transfer of associated transaction / data functions objects and links fails.

    As an example it can be seen that the AFP calculation will reflect "NoCalib" while there is calibration done on TCC.




  2. Ghost objects may be created, please refer to the following page that explain how to check if a given object is a ghost object: SQL Queries - CAST Knowledge Base - Queries on objects - Identify and clean up all the ghost objects and ghost projects in your knowledge base
  3. Some user defined modules may be inconsistent (most often empty, but also incomplete)

Partial remediation

Case 1: If the restored schema is the Central schema

As Partial remediation, you can perform the following steps:

  1. In Cast-MS remove the restored central schema from the application. For this go to the "Execute" tab and you will be able to see the Dashboard Service option.

  2. Close Cast-MS

  3. Identify the central ID of the restored Central schema in the management base by running the following query:

    SELECT object_id 
FROM <MNGT>.cms_inf_css_centraldb 
WHERE object_name = '<YourCentralschema>'

      For example:

    SELECT object_id 
FROM cb_ps_abe_mngt.cms_inf_css_centraldb 
WHERE object_name = 'cb_ps_abe_central'
-- 13622


  4. Delete the central ID of the restored central schema in the management base by running the following query:

    DELETE FROM <MNGT>.cms_inf_css_centraldb 
WHERE object_id = <result OF the previous query>

     For example:

    DELETE FROM cb_ps_abe_mngt.cms_inf_css_centraldb 
WHERE object_id = 13622


  5. Create a new central schema using ServMan, for this please refer to Server Manager - Install Database

  6. Open Cast-MS and discover the created central schema from Cast-MS

  7. Add the discovered central schema and synchronyze the triplet.
 

Case 2: If the restored schema is the knowledge base schema

As Partial remediation, you can perform the following steps:
  1. In Cast-MS remove the restored knowledge base from the application. For this go to the "Execute" tab and you will be able to see the Analysis Service option,

     
     
  2. In Cast-MS remove the restored central schema from the application. For this go to the "Execute" tab and you will be able to see the Dashboard Service option.

  3. Close Cast-MS

  4. Identify the local ID of the knowledge base in the management base by running the following query:
     

    SELECT object_id 
FROM <MNGT>.cms_inf_css_LocalDB
WHERE object_name = '<Yourknowledgebase>'

    For example:

    SELECT object_id
FROM cb_ps_abe_mngt.cms_inf_css_LocalDB
WHERE object_name = 'cb_ps_abe_local'
--13622

  5. Delete the local ID of the restored knowledge base in the management base by running the following query:

    DELETE FROM <MNGT>.cms_inf_css_LocalDB
WHERE object_id = <result OF the previous query>

      For example:

    DELETE FROM cb_ps_abe_mngt.cms_inf_css_LocalDB 
WHERE object_id = 13622

  6. Identify the central ID of the restored central schema in the management base by running the following query:

    SELECT object_id 
FROM <MNGT>.cms_inf_css_centraldb 
WHERE object_name = 'CB'

    for example:

    SELECT object_id 
FROM cb_ps_abe_mngt.cms_inf_css_centraldb 
WHERE object_name = 'cb_ps_abe_central'
-- 13622

  7. Delete the central ID of the restored central schema in the management base by running the following query:

    DELETE FROM <MNGT>.cms_inf_css_centraldb 
WHERE object_id = <result OF the previous query>

    For example:

    DELETE FROM cb_ps_abe_mngt.cms_inf_css_centraldb 
WHERE object_id = 13622

  8. Create a new knowledge base and central schema using ServMan, for this please refer to Server Manager - Install Database

  9. Open Cast-MS and discover the created knowledge base and central schema from Cast-MS

  10. Add the discovered central schema and knowledge base, then synchronyze the triplet.

     



 

Impacts

The impacts of the partial remediation are as follow:

  1. If the problem is due to the restored central schema, you will lose all the results of your previous snapshots, you will preserve only the configuration and the current analysis results
  2. If the problem is due to the restored knowledge base, you will lose all the results of your analysis as well as your previous snapshots, only configuration will be preserved.
  • No labels