Spotfire Ideas Portal
The following procedure does not create additional tables for multiple tables when migrating with the Deployment Manager.
The plan is running with the following options
Cache for New Objects : Create Cache Tables
Caches for Existing Objects : Re-create Cache Tables
(1) Set the number of tables to two in the multi-table cache and run the plan to migrate to the target site.
->xxx0, xxx1 are created in the source and target databases.
(2) Change the number of cache tables to 3 on the source and create cache tables.
->Table xxx2 is created in the source database
(3) Execute the plan again.
(4) The number of tables will be set to 3 on the cache tab of the view, even at the target site.
->But xxx2 is not created in the target database
I checked with TIBCO support and the Deployment Manager tries to create a multi-table cache in a single statement.
However, an error occurs because two tables already exist, and the newly added third table is not created.
Therefore, if the number of multi-table caches is to be increased on the source side, the multi-table cache that already exists at the target site must be deleted and the plan must be executed with "Cache for New Objects" set to "Create Cache Tables".
However, this specification is not documented and is difficult for users to understand while working with Deployment Manager.
Furthermore, this procedure requires a direct operation on the database, and I believe the operation should be completed in the Deployment Manager.
When changing the number of multi-table caches and performing the migration with the Deployment Manager, I would like to see an improvement to either of the following two operations.
(1) An alert appears saying "You need to delete the target table and create a new one.
(2) The cache table is automatically recreated by "CREATE OR REPLACE".
At that time, an alert is displayed stating that the target cache table will be deleted.