KB294947: Dynamic sourcing does not work on a clustered environment after a schema update in MicroStrategy versions 9.4.1 and 10.x

SUMMARY
This issue has been classified as a defect by Strategy. The impact is limited to Strategy reports using the dynamic sourcing feature. A solution/code fix for this issue will be available in Strategy Secure Enterprise 10.4
SYMPTOM
In a Strategy Intelligence Server clustered environment, it is observed that dynamic sourcing does work against Intelligent Cubes available on a remote node, after updating the schema.
STEPS TO REPRODUCE
The following steps are based on the Strategy Tutorial project: 

1. Create three Intelligent Cubes on Node 1 and publish them. 

              Cube Test 1: Category, Cost, Profit
              Cube Test 2: Call Center, Category, Employee, Employee Age, Region, Profit, Revenue
              Cube Test 3: Call Center, Profit, 
 
  2. Create a normal report called “Dynamic sourcing test” with attribute “Call center” and metric “Profit”.
 
  3. Run the report “Dynamic sourcing test” and notice below that the Intelligent Cube is hit.

select [Call Center]@[CALL_CTR_ID],
 [Call Center]@[CENTER_NAME],
 [Profit] as [Profit]
from Cube Test3

  4.  Open Warehouse Catalog and add any Warehouse tables  -> and Save & Close.
  5.  Update schema.
  6.  Login to Node 2 and run report “Dynamic sourcing test” and notice it doesn't hit any Intelligent cube.

SQL Statements:
select a11.CALL_CTR_ID CALL_CTR_ID,
 max(a12.CENTER_NAME) CENTER_NAME,
 sum((a11.TOT_DOLLAR_SALES - a11.TOT_COST)) WJXBFS1
from CITY_CTR_SLS a11
 join LU_CALL_CTR a12
 on (a11.CALL_CTR_ID = a12.CALL_CTR_ID)
group by a11.CALL_CTR_ID

[Analytical engine calculation steps:
 1. Perform cross-tabbing
]
Dynamic Sourcing Logs:
Report Parse Log:
Report is eligible for Dynamic Sourcing
_______________________________________________________________
Mismatch Log:
The report parsed OK, but no cubes were found to match
_______________________________________________________________
Extended Mismatch Log:
The report parsed OK, but no cubes were found to match
_______________________________________________________________

 
CAUSE
This is a known issue with Strategy 9.x - 10.3. 
ACTION
This issue has been fixed in Strategy Secure Enterprise 10.4. Upgrade to this version to take advantage of the fix.