KB34026: Some tables that are used in the project do not appear in the list of tables being used by the project of the Warehouse Catalog in MicroStrategy Developer 9.x.

SYMPTOM:
When trying to update the structure of one or more tables in the Warehouse Catalog in Strategy Developer 9.x, users notice that some or all of these tables do not show up in the list of tables being used by the project. However, checking the Schema Objects -> Tables folder confirms that these tables are indeed being used in the project.
 
CAUSE:
This issue is caused because the physical table object (DBTable) has become a managed object, and is therefore not visible in the Warehouse Catalog. It is not yet completely understood what triggers this, however, it is believed that performing multiple actions in one Warehouse Catalog session along with HDA (Heterogenous Data Access -- changing the database instance) is the probable action that leads to this issue.
 
ACTION:
 
ScanMD can now be used to resolve this issue.  In particular the ScanMD common test "Warehouse Tables Verification" has the ability to move DBTables to the correct System Objects\Warehouse Tables location if it finds DBTables which do not exist there.
 
Please contact the Technical Support for further assistance and obtain the following information from the customer:

• Any information as to what actions have taken place that may affect the tables that present the issue.
• The metadata and change journal. Actions are recorded through Change Journal, if the customer has it enabled then the metadata could be obtained for further investigation and a reproduction scenario construction.
• DSSErrors log from the Desktop machines where the warehouse catalog was used.  This log should contain the Source Manipulator entries which will record what objects were created/deleted along with any possible errors.

Once it has been confirmed by Technical Support that the physical table is a managed object and its DSSTable object is a non-managed object, the following SQL can be issued to resolve the issue:
 
Sql
update dssmdobjinfo set parent_id = '<GUID of Warehouse Tables folder>', object_state = 0 where object_id =  '<GUID of managed physical table>' and project_id = '<GUID of project>';