Prior to migrating a Planning Analytics
version 11 database, you must perform some environment and database maintenance to ensure a clean
migration.
About this task
The TM1® to Planning
Analytics Engine Database Migration Utility must be run
on the machine that hosts the Planning Analytics version
11 database.
Procedure
-
Ensure that cube, rule, and feeder filename stems are identical in case. (For example, if your
database includes
Cube1.cub and cube1.rux, change the rule
filename to Cube1.rux.
- Ensure that process data source files are accessible on the machine where you will run
the migration tool.
Processes are migrated even if the data source files are not accessible to the migration tool,
but if the data source file is inaccessible, the process does not run during migration. A warning is
issued if this occurs. After the migrated database is loaded into Planning Analytics Engine, you can modify the process to run
successfully using either of these options:
- Upload the data source file via the REST API to
~/Contents('Files')/Contents),
and modify the process data source location accordingly
- Modify the process to use a valid URL to the data source file's remote location
- Delete or repair views that refer to elements that no longer exist.
- Load the database into a recent Planning Analytics version 11 server and explicitly save data to
ensure that feeders are written out in the latest format.
- If a dimension with multiple hierarchies has the same leaf element defined with
conflicting element types in different hierarchies, resolve the conflicts so that the element type
is consistent in all hierarchies.
If the conflicts are not resolved, the dimension is not be migrated and the migration tool stops
after the first such dimension is encountered.
Here's an example of an error that occurs where an element is encountered twice in a dimension,
once as a Consolidated type and once as a Numeric type.
info 2022-05-27T18:16:20.676Z Loading dimension TestDim:TestHier1 service, tm1-i-0-d-0-0 version, 12.0.0-alpha.5 TM1.Migration
error 2022-05-27T18:16:20.677Z New element's type conflicts with existing element. dimension, TestDim:TestHier1 existing element, Consolidation1 existing type, N new element, Consolidation1 new type, C service, tm1-i-0-d-0-0 version, 12.0.0-alpha.5 TM1.Migration