KB442436: Update Warehose table command fails with "The table warehouse_table_name was not found in the warehouse catalog" when using secondary DB

SYMPTOM:

In Command Manager when using the script:
UPDATE STRUCTURE COLMERGEOPTION (RECENT | MAXDENOMINATOR | NOMERGE) [FOR WHTABLE "<warehouse_table_name>"] FOR PROJECT "<project_name>";
 
The warehouse table must be a part of the primary database or the command will fail with the error:
The table "<warehouse_table_name>" was not found in the warehouse catalog. Therefore, the table structure cannot be read or updated.
 

CAUSE:

The table must be a part of the primary database because there is no method to determine which database to pull the table from. The command automatically assumes that the table does not exist instead of checking secondary databases for the table.

SOLUTION: 

The current workaround is to edit the Command Manager script to alternate which Database Instance is considered primary if there are multiple instances being used. The command to do so is: 
ALTER PROJECT CONFIGURATION WAREHOUSE "<warehouse>" IN PROJECT "project"; 
However if using this method be aware that the script automatically changes every DBI to the primary instance. Human interaction will be required in order to change the secondary Database Instances in the Warehouse Catalog.
There is an enhancement in the works to define the database instance that is used in the UPDATE STRUCTURE Command Manager Script. Strategy's internal technology team has confirmed that this enhancement is not scoped for the 2019 release, but it is still being researched for a proper resolution.