This page handle the case when object is part of the Generated Set though it is not part of the analysis

Step by Step scenario 

• Run analysis and take a snapshot

Action Plan

1. Check if the objects are part of the module - SQL Queries - CAST Knowledge Base - Queries on Module - Module content and properties
   
2. This issue can be due to ghost object or ghost project, in order to get the list of these Ghosts and cleanup them from the analysis results, please follow steps explained in the following page SQL Queries - CAST Knowledge Base - Queries on objects - Identify and clean up all the ghost objects and ghost projects in your knowledge base, you may refer to the section 243187384 in order to have an idea of the root causes of this behavior  
3. If this does not match your case then please contact CAST Technical Support, and provide the list given in 243187384

Relevant input

1. Sherlock export with the following options: Export Logs (feature checked by default), Export Configuration files (feature checked by default),Export CAST Bases

Root causes

Ghost objects can be due to the special case of migration from CAST AIP version ≤ 7.0.x to CAST AIP version >7.0.x. In fact the terminology of job has changed in the meantime. In Cast AIP version  ≤ 7.0.x we were talking about "job" while in CAST AIP version >7.0.x we talk about "Execution unit". In order to not have this issue the migration should be done as follows:

• Delete all job results
• Do the migration from version  ≤ 7.0.x to version  > 7.0.x
• Run analysis

 Ticket # 5542