Page 1 of 1

Error while saving Activating existing chore

Posted: Wed Aug 10, 2016 10:39 am
by zodiacviv
Hi All,

Hope everyone is doing good!!.

Recently I have encountered strange error and I tried to find out details but was not able to look in correct direction.

I have a chore which has two process. First one is backup process for TM1 data folder and second one is version vopy process which copy data from one version to another for 5 cubes which woks on year and month parameter to copy.

So, when I try to schedule chore, this gives error in log file as below:

54604 [3af] ERROR 2016-08-10 11:19:30.992 TM1.Cube.VersionedTree.Versions CubeDataVersion::GenerateNewDepList: New dependency cube without a lock in commit.
54604 [3af] ERROR 2016-08-10 11:19:31.008 TM1.Cube.VersionedTree.Versions CubeDataVersion::GenerateNewDepList: New dependency cube without a lock in commit.
54604 [3af] ERROR 2016-08-10 11:19:31.008 TM1.Cube.VersionedTree.Versions CubeDataVersion::GenerateNewDepList: New dependency cube without a lock in commit.


When I tried creating new chores one for each process separately, they works fine. Also, I created one more new chore and added two process in same order and saved with same parameter as original chore. To my surprise, new chore got saved and activated and still old chore is giving same error after activating. Also, after error, Architect hangs out and I have to restart Architect.

I am not sure what exactly I am missing :(.

Regards,
Vivek

Re: Error while saving Activating existing chore

Posted: Thu Aug 11, 2016 6:22 pm
by Karthik1710
zodiacviv wrote:When I tried creating new chores one for each process separately, they works fine. Also, I created one more new chore and added two process in same order and saved with same parameter as original chore. To my surprise, new chore got saved and activated and still old chore is giving same error after activating. Also, after error, Architect hangs out and I have to restart Architect.
This is the most weird part of all.

Is there a AddCubeDependency statement in any of these processes?
Are you getting the error while Activating or during execution?
Does the new chore with both processes succeed on execution?