Hello,
I have my financial data load process to load data for one period at a time (for 2013 only) and keeping historical data in cube. I created a zero out view that had 12 months of 2013 and in my process i have a loop to keep historical data. Please see attached file for my prolog code. The process ran and loaded data without any issue for few days however couple days ago after updating Windows Server 2008 R2, I noticed that my cube started accumulating values every time when i run the process and if I open my Zero Out view, It does not hold 12 months elements that I added. The same process I have running in my development server with no issue at all but when I run this process in my production, It keeps accumulating data. it all started after updating windows in my production server and i looked into event viewer of windows and found following errors. I do not know if it is happening due to this error or something else is going on in server.
"Log Name: Application
Source: SideBySide
Event ID: 63
Description:
Activation context generation failed for "c:\program files (x86)\IBM\cognos express clients\xcelerator client\jre\bin\unpack200.exe".Error in manifest or policy file "c:\program files (x86)\IBM\cognos express clients\xcelerator client\jre\bin\unpack200.exe" on line 6. The value "6.0.0.6u9b39" of attribute "version" in element "assemblyIdentity" is invalid."
Here is what I want to do know and need your help in this regard.
Is there a way to setup or edit my data load process where process will scan value in the cell before loading it and if the value in the cell is equal to the loading value then skip it otherwise it will load the different value. (In other words I want to create some kind of validation process where I know ahead of time if the updated cube has correct value or not)?
TM1 Cube Values Doubled and Zero Out View not working
-
- Posts: 30
- Joined: Wed Jun 06, 2012 8:59 pm
- OLAP Product: TM1
- Version: TM1 9.5.2
- Excel Version: 2010
TM1 Cube Values Doubled and Zero Out View not working
- Attachments
-
- Prolog Process of finance cube.txt
- (4.52 KiB) Downloaded 276 times
- Martin Ryan
- Site Admin
- Posts: 1989
- Joined: Sat May 10, 2008 9:08 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
- Location: Wellington, New Zealand
- Contact:
Re: TM1 Cube Values Doubled and Zero Out View not working
My guess is that strCurrYr = CELLGETS ( 'bpmControls', 'Value', 'Current Actual Year' ); is returning nothing. Try using "ItemReject(strCurrYr);" to test that theory - or just check in the cube itself.
Can you screenshot what the view looks like after you've created it (right click on the view under the cube and go to export as ascii data, then screenshot that)? That might yield more clues.
Can you screenshot what the view looks like after you've created it (right click on the view under the cube and go to export as ascii data, then screenshot that)? That might yield more clues.
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers.
Jodi Ryan Family Lawyer
Jodi Ryan Family Lawyer
-
- Posts: 30
- Joined: Wed Jun 06, 2012 8:59 pm
- OLAP Product: TM1
- Version: TM1 9.5.2
- Excel Version: 2010
Re: TM1 Cube Values Doubled and Zero Out View not working
Martin, Thanks for your reply. I would really like to test it in production server, As i explained earlier that in development everything seems to be working fine. So please bear with me and I will test it in production after hours and post a shot. For now here is what I have done so far to make my production working.Martin Ryan wrote:My guess is that strCurrYr = CELLGETS ( 'bpmControls', 'Value', 'Current Actual Year' ); is returning nothing. Try using "ItemReject(strCurrYr);" to test that theory - or just check in the cube itself.
Can you screenshot what the view looks like after you've created it (right click on the view under the cube and go to export as ascii data, then screenshot that)? That might yield more clues.
After finding no issue in prolog process and the same process was working in development so i had no choice to restore my production server at the point where everything was working fine and then I re-ran all processes and it is working now. I do not know what went wrong after windows updates! Thanks