Planning Analytics

Hi All

We recently upgraded to PA (we are now on 2.08) and to Security Mode 3 (from 2) to simplify user login are having some issues with some processes using TM1RunTI (which worked fine in the previous versions).  We created an admin user account with the name of the Server service account in order to get the RunTis to work.

The processes are to create static versions of a planning model and we use TM1RunTI to copy various years in parallel to speed up the process.

When run as is they now seem to either randomly just run for one year or run for all years but not in parallel.

I have looked to change the processes to use the RunProcess function in the new version.  I can get this to work for the first time run the process, but then in the second run I get errors - "Error: Prolog procedure line (0): Unable to open data source" and the cube name.  The third time I run the process I see "Execution rolling back due to lock exception" errors in the server log but the copy processes seem to re-run and the copy does happen correctly

Here is the logic I have:

Control Process with parameters (Years, Version from/to)

------------------------------
Peter Rameson
------------------------------

#PlanningAnalyticswithWatson

Hey Peter,
Lock contentions are always a challenge when running parallel threads. To get to the bottom of this you'll need to turn on Lock Exception logging to figure out what object the contention is happening on.
A few things stand out though,

• the prolog error typically occurs when when the view the process is trying to access does not exist or is malformed (has an empty subset for example). In more
• I would avoid using View Construct if you can, it typically does not provide any added benefit now that TI can leverage MTQ on it's own.
• I would also recommend not using materialized views that require deletion. Use temporary views with unique names instead.

Cheers.

------------------------------
Ryan Clapp
------------------------------

Original Message:
Sent: Wed February 05, 2020 07:02 AM
From: Peter Rameson
Subject: TM1RunTI / RunProcess issues

Hi All

We recently upgraded to PA (we are now on 2.08) and to Security Mode 3 (from 2) to simplify user login are having some issues with some processes using TM1RunTI (which worked fine in the previous versions).  We created an admin user account with the name of the Server service account in order to get the RunTis to work.

The processes are to create static versions of a planning model and we use TM1RunTI to copy various years in parallel to speed up the process.

When run as is they now seem to either randomly just run for one year or run for all years but not in parallel.

I have looked to change the processes to use the RunProcess function in the new version.  I can get this to work for the first time run the process, but then in the second run I get errors - "Error: Prolog procedure line (0): Unable to open data source" and the cube name.  The third time I run the process I see "Execution rolling back due to lock exception" errors in the server log but the copy processes seem to re-run and the copy does happen correctly

Here is the logic I have:

Control Process with parameters (Years, Version from/to)

Prolog - uses ExecuteProcess to call a create view process for each year specified  - a source view and a zero out view are created (using ViewConstruct) and the ZeroOut view is zeroed out.

Epilog - uses RunProcess to call a DataLoad process for each year and do the copy using the previously created views (and destroy the views in the Epilog (the source and the zeroout for that year).

Any help or advice would be greatly appreciated - I'm not sure what the best practice is now for parallel processing - should I be looking to use Batch processing / maybe looking to use something like RushTI or is there just some logic issue with my code?

Thanks
Peter

------------------------------
Peter Rameson
------------------------------

#PlanningAnalyticswithWatson

Hi Ryan

Many thanks for this.

I have resolved the issue now - many thanks also to  @Scott Brown for the help.

• I changed the ExecuteProcess calls to RunProces​​s calls (for the View Creates)
• I moved the Zero Out view creation to the Prolog tab of the Data Load process (I think this is the key to the lock contention) and changed it to a temporary view.
• I've also now removed the ViewConstruct - thanks @Ryan Clapp

Cheers,



------------------------------
Peter Rameson
------------------------------

Original Message:
Sent: Thu February 06, 2020 01:50 AM
From: Ryan Clapp
Subject: TM1RunTI / RunProcess issues

Hey Peter,
Lock contentions are always a challenge when running parallel threads. To get to the bottom of this you'll need to turn on Lock Exception logging to figure out what object the contention is happening on.
A few things stand out though,

• the prolog error typically occurs when when the view the process is trying to access does not exist or is malformed (has an empty subset for example). In more
• I would avoid using View Construct if you can, it typically does not provide any added benefit now that TI can leverage MTQ on it's own.
• I would also recommend not using materialized views that require deletion. Use temporary views with unique names instead.

Cheers.

------------------------------
Ryan Clapp

Original Message:
Sent: Wed February 05, 2020 07:02 AM
From: Peter Rameson
Subject: TM1RunTI / RunProcess issues

Hi All

We recently upgraded to PA (we are now on 2.08) and to Security Mode 3 (from 2) to simplify user login are having some issues with some processes using TM1RunTI (which worked fine in the previous versions).  We created an admin user account with the name of the Server service account in order to get the RunTis to work.

The processes are to create static versions of a planning model and we use TM1RunTI to copy various years in parallel to speed up the process.

When run as is they now seem to either randomly just run for one year or run for all years but not in parallel.

I have looked to change the processes to use the RunProcess function in the new version.  I can get this to work for the first time run the process, but then in the second run I get errors - "Error: Prolog procedure line (0): Unable to open data source" and the cube name.  The third time I run the process I see "Execution rolling back due to lock exception" errors in the server log but the copy processes seem to re-run and the copy does happen correctly

Here is the logic I have:

Control Process with parameters (Years, Version from/to)

Prolog - uses ExecuteProcess to call a create view process for each year specified  - a source view and a zero out view are created (using ViewConstruct) and the ZeroOut view is zeroed out.

Epilog - uses RunProcess to call a DataLoad process for each year and do the copy using the previously created views (and destroy the views in the Epilog (the source and the zeroout for that year).

Any help or advice would be greatly appreciated - I'm not sure what the best practice is now for parallel processing - should I be looking to use Batch processing / maybe looking to use something like RushTI or is there just some logic issue with my code?

Thanks
Peter

------------------------------
Peter Rameson
------------------------------

#PlanningAnalyticswithWatson