This page provide you the definition of ghost objects, how to identify them and how to clean them. The following graph represent the simpliffied parenthood morphology of the objects in the knowledge base (Analysis Service database).On one hand each object in the knowledge base have one and only one project parent that have one and only one Analisis unit parent, in the other hand each analysis unit may have one or several Projects child, and each Project have one or several objects child. Fore some reason (As an example of root cause you can refer to Urgent Notice - CAST AIP - Risk and impacts of synchronization when restoring only knowledge base or central schema instead of the entire triplet - 4th November 2016), this parent to child relationship can be broken. We differentiate 2 different cases:
This act will result in ghost objects, In order to identify and clean up the list of ghost objects, please refer to Ghost objects
After cleaning up any ghost objects and projects, run a new analysis and snapshot to update all the information in the CAST databases. |
|
|
Ghost ProjectsThe following query will work on CSS and oracle and when run on a knowledge base will list the set of ghost projects that are the result of broken links between analysis unit and project:
As an example you can find:
In order to clean up the list of Ghost Projects, please execute the following query on you knowledge base. Note that this clean up is irreversible for that, we advice you to take a backup of your local (Analysis Service database), central (Dashboard Service database) and management base (Management Service database) even if the cleanup is done on only the knowledge base. Query for CSS:
Query for Oracle - for each project_id identified in the query above run the following on the KB:
|
Ghost ObjectsThe following query run on the KB on Oracle or CSS will list the set of ghost objects that are the result of broken links between project and object:
As an example you can find:
In order to clean up the list of Ghost objects, please execute the following query on you knowledge base. Note that this clean up is irreversible for that, we advice you to take a backup of your local, central and management base (even if the cleanup is done on only the knowledge base): For CSS:
For Oracle:
After cleaning up any ghost objects and projects, run a new analysis and snapshot to update all the information in the CAST databases. |
Impacts - Data Functions and Transactions Functions will be reduced if the removed ghost object was part of this list |
|