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:
Broken links between analysis unit and project(s):
This act will result in Ghost project, therefore ghost objects, In order to identify and clean up the list of ghost projects and ghost objects, please refer to Ghost Projects
- Broken links between project and object(s):
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.