FIX: Full Process of a Remote Partition Unprocesses Other Remote Partitions in Same Server (297933)

MORE INFORMATION

The DSO method Process (ProcessFull) incorrectly sets the State property of the remote partitions to olapStateNeverProcess or zero. This is obviously incorrect and may cause problems if you are relying on the State property to be accurate in code.

Steps to Reproduce Behavior

1. In the Sales cube of the FoodMart 2000 database, add a new partition by right-clicking the Partitions folder, and then click New Partition....
2. In the Select a Data Slice page of the Partition Wizard, select the Time dimension, 1997, and Q2. Click Next.
3. Click the remote option, and then type the servername where the remote partition will reside. Click Next.
4. Save the new partition as Test1, and then select the Design aggregations later option. Click Finish.
5. Repeat steps 2 and 3 to create a second partition, and name this partition Test2.
6. In a Microsoft Visual Basic project run the following DSO code:

   Dim dsoServer As New DSO.Server
       dsoServer.Connect "LocalHost"
   Dim dsoDb As DSO.MDStore
       Set dsoDb = dsoServer.MDStores("Foodmart 2000")
   Dim dsoCube As DSO.MDStore
       Set dsoCube = dsoDb.MDStores("Sales")
   Dim dsoPart As DSO.MDStore
       For Each dsoPart In dsoCube.MDStores
           Debug.Print dsoPart.Name & " State = " & dsoPart.State
       Next dsoPart
       For Each dsoPart In dsoCube.MDStores
          Debug.Print "Processing " & dsoPart.Name
          dsoPart.Process processFull
       Next dsoPart
       For Each dsoPart In dsoCube.MDStores
           Debug.Print dsoPart.Name & " State = " & dsoPart.State
       Next dsoPart
   					

After you run the code in the Visual Basic Immediate Window, you see that the Test1 partition has a State of 0, which means it was never processed. The Test2 partition has a State of 4, which means that partition is current.