Hi,
using Cognos TM1 v9.5 I am regularly having problems with single cube. All of the processes for recreating dimensions are correctly build, but the process of updating cube returns error.
Error: Prolog procedure line (3): Cube "MY_CUBE" Not Found
All of the processes are run every day at night and I have found out that this problem ONLY appears every day AFTER end-of weekend (each Monday) and every day AFTER some national holiday. It is possible that this error appears because there is no NEW data stored in warehouse at "error day".
It looks like a cube is being DELETED despite I have no delete command (like recreate) in my process. In the process of loading data I use the following in Turbo Integrator:
1. Datasource Type: ODBC (this is DB2 database).
2. On Variables tab I have Contents=Element for every dimension and Data for data field.
3.1. Maps | Cube | Cube Action=Update Cube
3.2. I have checked "Zero Out Portion" in "Edit View" button I have left all of the settings default and just saved the view - I want to delete all the data from cube (or mark it with zeros).
4. Maps | Cube | Data Action=Store Values
5. on Maps | Dimensions there is nothing special just mapping dimensions on Dimensions tab and data elements on Data tab.
6. on Advance tab I haven't changed anything - all default.
I am wondering why every MONDAY I have a problem with this process. At the moment I have 10 cubes in production and one single process that I am having problems with it every Monday. Any idea what is wrong? Is this some kind of bug? Or am I doing something wrong?
P.S. Work-around: I have created special purpose process that I am executing at the "error day", process is the same as described above except on Maps | Cube |Cube Action=Create Cube; then I have to manually run this process; because cube was deleted in the night I need to create rules and views.
Regards
tomok, sorry, I don't understand you question. I don't get any error in TM1 Architect and process is running without any error for a week, but every Monday I get this "Cube does not exist" error.
I have attached print-screens of MY_CUBE process. Please see attachment. Am I doing something wrong?
It looks like the cube PROD_MARZE gets deleted outside of your process, so that when it gets executed it cannot find it and falls over on the first line of code. Are you aware of any other process in your environment that would be deleting this cube periodically?
My thoughts are the same. Namely that if this process is running daily OK except for Monday and it is failing on Monday because the cube has been deleted then the problem is not in this process but in another process/chore that is running sometime between when this process runs on Sunday and when it runs on Monday.
Also if this is supposed to be a production system then I would advise against using any wizard generated code period.
On this cube there are running the following processes:
1. processes to recreate dimensions - all of them having "recreate dimension" option
2. above process that loads data into cube
The error "Cube Not Found" is appearing every Monday and every day after national holiday! All of the jobs running from chore are daily jobs. This are days that no data are refreshed in warehouse database. So it looks to me that some of operation is deleting too much, I am suspecting deleting from zero out view (Prolog command: VIEWZEROOUT command). Is there any other way to all data from cube except using ZeroOut option and using view? I am just trying to do something different to see if error still appears.
Error: Prolog procedure line (3): Cube "MY_CUBE" Not Found
Is telling me that TM1 is looking for a cube that is literally named "MY_CUBE". According to the screen shots of your TI code, the cube in questions is named "PROD_MARZE" so right there I know there is something missing here. I know TM1 can do some crazy things but there is no way that it can turn "PROD_MARZE" into "MY_CUBE" unless you have some statements programmed into your TI that does that. Go back through your processes and check all the ones that work against this cube. Better yet, do a text search of your data directory for the string "MY_CUBE" and let us know what you find.
tomok, in my first post I just tried to simplify the sample and have just written MY_CUBE and *manually* replaced PROD_MARZE string with MY_CUBE everywhere it was written just for purpose of simplifying a sample for this forum. So instead MY_CUBE there is actually real name PROD_MARZE. So there is no MY_CUBE in production.
Sorry for confusing, I was trying to simplify, but I see I created bigger mess.
How many active chores do you have in your model? Is it possible for you to go through them and list all the processes involved? If there aren't too many, you could post the code in the Prolog, Metadata, Data and Epilog tabs of these processes so that we can help you pinpoint which other process deletes the cube, as this is what it looks like is happening with what we know right now.
qml, I have 7 chores in production this core is the first chore that is run every single day and all other chores are also run every single day. By the way, today in the morning the same problem reappeared and today is not a Monday and it is also not a fist day after a holiday - so my theory is broken. Yesterday everything was OK, so all the chores that run after THE chore are not effecting the problem. Bellow are the processes inside THE chore in the order of executing. Sections are: Prolog, Metadata, Data, Epilog.
I can't see any code that would remove / rebuild the cube, so it must be something else. Maybe you can go through your other chores/processes and search for anything like
