I have a TI process that ZERO out a view and then import new values to it.
The view and TI process has been used for ages and suddenly someone complained to me the other day the view no longer being zero out.
I tested it and turned out it wasn't.
I checked all my settings, cube wasn't locked, dimension wasn't locked, nothing got lock.
To resolve the issue, I re-create a new view and a new TI process and discard the one I have used for ages.
The new one I set up works as expected.
Has anyone had experience the similar scenario or can anyone share some lights at the end of the tunnel?
By the way, Happy Easter!
TI zero Out view -
- Chengooi
- Posts: 64
- Joined: Tue Jan 13, 2009 7:46 am
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 2003
- Location: Auckland, New Zealand
- Contact:
TI zero Out view -
The most wasted of all days is one without laughter.
e e cummings (1894-1962)
e e cummings (1894-1962)
- Steve Rowe
- Site Admin
- Posts: 2417
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: TI zero Out view -
I'm guessing your old view had been changed "somehow", maybe one of your users playing an April Fool on you? Other than a problem with a view I'm not sure, VZO doesn't really go wrong, although in some versions of 9.0 the user running the TI requires write access for it to work properly.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
- Alan Kirk
- Site Admin
- Posts: 6606
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: TI zero Out view -
Could also have been an issue with the dimension subsets which were defining the view; if they no longer included all of the elements that they should have, or were from MDX which no longer returned the correct elements, stemming from changes to the dimension structures. In any case I agree that the most likely cause was something related to the view definition and not to the VZO function. Impossible to know without seeing the original .vue file, the revised one and possibly the dims as well.Steve Rowe wrote:I'm guessing your old view had been changed "somehow", maybe one of your users playing an April Fool on you? Other than a problem with a view I'm not sure, VZO doesn't really go wrong, although in some versions of 9.0 the user running the TI requires write access for it to work properly.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
- Chengooi
- Posts: 64
- Joined: Tue Jan 13, 2009 7:46 am
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 2003
- Location: Auckland, New Zealand
- Contact:
Re: TI zero Out view -
I wish it was an April fool prank, but it wasn't.
I am the one and only in the whole wide world knew how to fix the vue. But it's just leave me with lots of doubts why suddenly it did not work and I knew it's got to be due to change but what excatly has changed! I like to "blame" it on something but blame what?
Anyway, just one of those mystery moments!
Thanks guys!
I am the one and only in the whole wide world knew how to fix the vue. But it's just leave me with lots of doubts why suddenly it did not work and I knew it's got to be due to change but what excatly has changed! I like to "blame" it on something but blame what?
Anyway, just one of those mystery moments!
Thanks guys!
The most wasted of all days is one without laughter.
e e cummings (1894-1962)
e e cummings (1894-1962)
-
- MVP
- Posts: 3654
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: TI zero Out view -
I've seen this happen a number of times. The reason that a "zero out view" or "processing view" invariably stops working is that a public subset used by the view has been overwritten from the intended element set. Invariably also the root cause of this is having inept or inexperienced users with admin access who either don't realise that the subset has been changed or don't realise the consequences. For this reason views and subsets used by TI processes should never be permanent but should always be created and destroyed within the process that they are used.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Posts: 68
- Joined: Wed Feb 25, 2009 2:26 am
- OLAP Product: TM1, Cognos Express
- Version: 9.5 9.4 9.1 9.0 8.4
- Excel Version: 2007 2003
Re: TI zero Out view -
I have seen this in different instances, however it normally produces a erro log detailing the 'view could not be zero'd out' or something similar....
- Chengooi
- Posts: 64
- Joined: Tue Jan 13, 2009 7:46 am
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 2003
- Location: Auckland, New Zealand
- Contact:
Re: TI zero Out view -
I truely believe it was due to a change of some sort, I spent quite a bit of time tried to evaluate which subset has changed but to no avail.
Anyway, Belair22 's suggestion was great, how did you manage to get an alert for view not being zero out.
Mine has not been able until a user complaint to me the vue has not zero out.
Can share me your trick? I will be very thankful to you!
Anyway, Belair22 's suggestion was great, how did you manage to get an alert for view not being zero out.
Mine has not been able until a user complaint to me the vue has not zero out.
Can share me your trick? I will be very thankful to you!
The most wasted of all days is one without laughter.
e e cummings (1894-1962)
e e cummings (1894-1962)
- Pim van Putten
- Posts: 8
- Joined: Thu Nov 13, 2008 4:30 pm
Re: TI zero Out view -
Hi Chengooi,
It is always better to rewrite the TI process, using a dynamic view as ZeroOutView. Steps would be
1) Throwing away the temp view
2) Creating the temp view
3) ZeroOut the temp wiew
4) Throwing away the Temp view again to clean up.
This way you can easily parameterize your view as well..
As an example (code should be in the PROLOG normally):
## Dynamic ZeroOut
# STEP 1
ViewDestroy('MyStockCube','_MyDynamicZeroOutView');
SubsetDestroy('Scenario','_MyDynamicSubset');
SubsetDestroy('StockYear','_MyDynamicSubset');
SubsetDestroy('Type','_MyDynamicSubset');
SubsetDestroy('Year','_MyDynamicSubset');
SubsetDestroy('Period','_MyDynamicSubset');
SubsetDestroy('Stock_measures','_MyDynamicSubset');
# STEP 2
SubsetCreate('Scenario','_MyDynamicSubset');
SubsetElementInsert('Scenario','_MyDynamicSubset','Actual',1);
SubsetCreate('StockYear','_MyDynamicSubset');
SubsetElementInsert('StockYear','_MyDynamicSubset','2008',1);
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Type] )} ) }, 0)}');
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Year] )} ) }, 0)}');
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Period] )} ) }, 0)}');
SubsetCreate('Stock_measures','_MyDynamicSubset');
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Quantity',1);
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Price',2);
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Value',3);
ViewCreate('MyStockCube','_MyDynamicZeroOutView');
# STEP 3
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Scenario','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','StockYear','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Type','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Year','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Period','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Stock_measures','_MyDynamicSubset');
# STEP 4
ViewZeroOut('MyStockCube','_MyDynamicZeroOutView');
# STEP 5
ViewDestroy('MyStockCube','_MyDynamicZeroOutView');
SubsetDestroy('Scenario','_MyDynamicSubset');
SubsetDestroy('StockYear','_MyDynamicSubset');
SubsetDestroy('Type','_MyDynamicSubset');
SubsetDestroy('Year','_MyDynamicSubset');
SubsetDestroy('Period','_MyDynamicSubset');
SubsetDestroy('Stock_measures','_MyDynamicSubset');
# Greetings Pim
It is always better to rewrite the TI process, using a dynamic view as ZeroOutView. Steps would be
1) Throwing away the temp view
2) Creating the temp view
3) ZeroOut the temp wiew
4) Throwing away the Temp view again to clean up.
This way you can easily parameterize your view as well..
As an example (code should be in the PROLOG normally):
## Dynamic ZeroOut
# STEP 1
ViewDestroy('MyStockCube','_MyDynamicZeroOutView');
SubsetDestroy('Scenario','_MyDynamicSubset');
SubsetDestroy('StockYear','_MyDynamicSubset');
SubsetDestroy('Type','_MyDynamicSubset');
SubsetDestroy('Year','_MyDynamicSubset');
SubsetDestroy('Period','_MyDynamicSubset');
SubsetDestroy('Stock_measures','_MyDynamicSubset');
# STEP 2
SubsetCreate('Scenario','_MyDynamicSubset');
SubsetElementInsert('Scenario','_MyDynamicSubset','Actual',1);
SubsetCreate('StockYear','_MyDynamicSubset');
SubsetElementInsert('StockYear','_MyDynamicSubset','2008',1);
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Type] )} ) }, 0)}');
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Year] )} ) }, 0)}');
SubsetCreateByMDX('_MyDynamicSubset','{TM1FILTERBYLEVEL( { HIERARCHIZE( {TM1SUBSETALL( [Period] )} ) }, 0)}');
SubsetCreate('Stock_measures','_MyDynamicSubset');
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Quantity',1);
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Price',2);
SubsetElementInsert('Stock_measures','_MyDynamicSubset','Value',3);
ViewCreate('MyStockCube','_MyDynamicZeroOutView');
# STEP 3
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Scenario','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','StockYear','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Type','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Year','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Period','_MyDynamicSubset');
ViewSubsetAssign('MyStockCube','_MyDynamicZeroOutView','Stock_measures','_MyDynamicSubset');
# STEP 4
ViewZeroOut('MyStockCube','_MyDynamicZeroOutView');
# STEP 5
ViewDestroy('MyStockCube','_MyDynamicZeroOutView');
SubsetDestroy('Scenario','_MyDynamicSubset');
SubsetDestroy('StockYear','_MyDynamicSubset');
SubsetDestroy('Type','_MyDynamicSubset');
SubsetDestroy('Year','_MyDynamicSubset');
SubsetDestroy('Period','_MyDynamicSubset');
SubsetDestroy('Stock_measures','_MyDynamicSubset');
# Greetings Pim
- Chengooi
- Posts: 64
- Joined: Tue Jan 13, 2009 7:46 am
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 2003
- Location: Auckland, New Zealand
- Contact:
Re: TI zero Out view -
great thanks!
The most wasted of all days is one without laughter.
e e cummings (1894-1962)
e e cummings (1894-1962)