Unable to register subset

by ·Comments Off on Unable to register subset

Product:

Planning Analytics 2.1.11
Microsoft Windows 2022 server

Issue:

You get random Unable to register subset when you run the Tm1 TI process, can be that the subset is not correct deleted, and therefor already exist when the TI process try to create it.

Error contain: Unable to register subset

Suggested solution:

Instead of using the TI process name, create a random subset name with a code similar to below:

#--------------------------------------------------
# Create names
#--------------------------------------------------

SourceView= pFromCube | 'TempSource' | getProcessName() | '_' | timSt(now, '\Y\m\d\h\i\s') | '_' | NumberToString (Rand()*1000000000);
TargetView= pToCube | 'tempClear' | getProcessName() | '_' | timSt(now, '\Y\m\d\h\i\s') | '_' | NumberToString (Rand()*1000000000);

#--------------------------------------------------
# Create views
#--------------------------------------------------

#Source
if(ViewExists(pFromCube, SourceView)=0);
viewCreate(pFromCube, SourceView,1);
endif;
#target
if(ViewExists(pToCube, TargetView)=0);
viewCreate(pToCube, TargetView,1);
endif;

ViewCreate (cubetouse, viewnametouse, a 1 here make the view only exist in this process section..)

ViewCreate(Cube, ViewName, <AsTemporary>);

Argument

Description
Cube The parent cube of the view you are creating.
ViewName The name you want to assign to the view.
AsTemporary This is an optional argument that specifies whether the view being created is temporary. 1 indicates a temporary view, 0 indicates a permanent view.

If this argument is omitted, the view is permanent.

More Information:

ViewCreate – IBM Documentation

For TM1® Server version 11.2.0 and earlier, temporary views were visible and usable only by the process that created it and any of its child processes. Temporary views were not visible to the ancestor and sibling processes. You could create same-named views in sibling child processes with the same parent process.

For TM1 Server version 11.3.0 and later, these temporary views are visible to the ancestor and sibling processes. If a parent TurboIntegrator process A invokes two child TurboIntegrator processes A1 and A2, and the child TurboIntegrator process A1 creates a temporary view S, the temporary view S exists for the duration of the parent TurboIntegrator process A. You cannot create a temporary view with the same name S in the sibling TurboIntegrator process A2 since the view is visible and usable by siblings A1 and A2.

Create a very large dimension in Cognos TM1 using Turbo Integrator (TI) – Ever Analytics

Wim‘s Excel, TM1 & soccer site

What’s new in IBM Planning Analytics – IBM Documentation

  • Planning Analytics 2.0.7 – April 29, 2019
    IBM Planning Analytics Local version 2.0.7 and the cloud release of IBM Planning Analytics version 2.0.7 includes updates and new features for IBM TM1 Server version 11.5.0.
  • Planning Analytics 2.0.6 – October 11, 2018
    IBM Planning Analytics Local version 2.0.6 and the cloud release of IBM Planning Analytics version 2.0.6 includes updates and new features for IBM TM1 Server version 11.4.0.
  • Planning Analytics 2.0.5 – June 25, 2018
    IBM Planning Analytics Local version 2.0.5 and the cloud release of IBM Planning Analytics version 2.0.5 includes updates and new features for IBM TM1 Server version 11.3.0.
  • Planning Analytics 2.0.4 – February 16, 2018
    IBM Planning Analytics Local version 2.0.4 and the cloud release of IBM Planning Analytics version 2.0.4 includes updates and new features for IBM TM1 Server version 11.2.0.