Version Differences for Workflows Stuck on the AHP Server

Revision as of 12 October 2012 13:44 (/* There are problems that can occur/present themselves which cause workflows to be stuck in various statuses on the AnthillPro server. Sometimes the only way to resolve this issue is through database) ← Previous diff

Revision as of 30 October 2012 15:36 Next diff →

Line 2:
-	* Set all running workflows to "aborted" status	+	==== Set all running workflows to "aborted" status ====
-	::<pre> UPDATE WORKFLOW_CASE SET STATUS='Aborted' WHERE STATUS = 'Running';</pre>	+	<pre> UPDATE WORKFLOW_CASE SET STATUS='Aborted' WHERE STATUS = 'Running';</pre>
-	* Set a specific build life id to "aborted" status - substitute 50 for your BL ID	+	==== Set a specific build life id to "aborted" status ====
-	::<pre> UPDATE WORKFLOW_CASE SET STATUS='Aborted' WHERE BUILD_LIFE_ID = 50;</pre>	+	''substitute 50 for your BL ID''
		+	<pre> UPDATE WORKFLOW_CASE SET STATUS='Aborted' WHERE BUILD_LIFE_ID = 50;</pre>
		+	==== Delete all locks present (requires server restart) ====
		+	<pre>DELETE FROM LOCK_HOLDER_LOCK_RES;
		+	DELETE FROM LOCK_HOLDER;
		+	UPDATE JOB_TRACE SET STATUS = 'Failed' WHERE STATUS IN ('Running','Waiting on Agents','Restarting','Aborting');
		+	UPDATE WORKFLOW_CASE SET STATUS = 'Failed' WHERE STATUS IN ('Running','Waiting on Agents','Restarting','Aborting');
		+	UPDATE JOB_STEP_TRACE SET STATUS = 'Failed' WHERE STATUS IN ('Running','Waiting on Agents','Restarting','Aborting');
		+	UPDATE JOB_STEP_CMD_TRACE SET STATUS = 'Failed' WHERE STATUS IN ('Running','Waiting on Agents','Restarting','Aborting');
		+	</pre>