Inter-Cube feeder corrupts entire environment
Posted: Tue Apr 20, 2010 4:17 pm
Hi All,
I have a calculation which references a value calculated in another cube. I have setup a feeder in the source cube to feed the calculation:
Destination Cube:
['Calc'] = DB('SourceCube','Calc');
Source Cube:
['Calc'] => DB('DestinationCube','Calc');
which to me seems logical enough and has been working ok, the problem i have is that i shut down my TM1 server and when i restart it doesn't load and appear in my server explorer window. If i remove or comment out the Feeder the server loads properly and appears in my server explorer. The weird thing is I've since rebuilt the feeder using the DB button in the rules editor (just to check i had the dimensions in the right order) and it checks the syntax and saves fine, it's only when i go to restart the server that it breaks and stops the whole server, when i look at the message log I see:
FATAL tm1.lock IX Conflict Encountered during single threaded operation in CheckReadOnlyConflict
Does anyone know what is going on? As I say this was working up until today and TM1 allowed me to save the problem feeder
Cheers
Dubs
I have a calculation which references a value calculated in another cube. I have setup a feeder in the source cube to feed the calculation:
Destination Cube:
['Calc'] = DB('SourceCube','Calc');
Source Cube:
['Calc'] => DB('DestinationCube','Calc');
which to me seems logical enough and has been working ok, the problem i have is that i shut down my TM1 server and when i restart it doesn't load and appear in my server explorer window. If i remove or comment out the Feeder the server loads properly and appears in my server explorer. The weird thing is I've since rebuilt the feeder using the DB button in the rules editor (just to check i had the dimensions in the right order) and it checks the syntax and saves fine, it's only when i go to restart the server that it breaks and stops the whole server, when i look at the message log I see:
FATAL tm1.lock IX Conflict Encountered during single threaded operation in CheckReadOnlyConflict
Does anyone know what is going on? As I say this was working up until today and TM1 allowed me to save the problem feeder
Cheers
Dubs