Version Differences for Workflows Stuck on the AHP Server

Revision as of 13 May 2013 09:10 (Combined into one massive section & put appropriate selectors) ← Previous diff

Revision as of 13 May 2013 09:11 Next diff →

Line 122:
	</tr>		</tr>
	</table>		</table>
-	== Job Step Traces ==
-	More rare than the previous two, the step itself can still have a leftover status.
-	<table border=2 cellspacing=2 cellpadding=2 align=center>
-	<tr>
-	<th bgcolor=#000000><font color=white>Type</font></th>
-	<th bgcolor=#000000><font color=white>SQL</font></th>
-	</tr>
-	<tr>
-	<td align=center bgcolor=#808080><font color=white>set all running step traces to a status</font></td>
-	<td><font face=monospace>UPDATE JOB_STEP_TRACE SET STATUS = 'XX' WHERE STATUS = 'YY'</font></td>
-	</tr>
-	</table>
-	== Command Traces ==
-	Usually hidden behind the scenes, these might also need updated if any of the prior failed.
-	<table border=2 cellspacing=2 cellpadding=2 align=center>
-	<tr>
-	<th bgcolor=#000000><font color=white>Type</font></th>
-	<th bgcolor=#000000><font color=white>SQL</font></th>
-	</tr>
-	<tr>
-	<td align=center bgcolor=#808080><font color=white>set all running command traces to a status</font></td>
-	<td><font face=monospace>UPDATE JOB_STEP_CMD_TRACE SET STATUS = 'XX' WHERE STATUS = 'YY'</font></td>
-	</tr>
-	</table>
	== Lockable Resources & Lock Holders ==		== Lockable Resources & Lock Holders ==
	Lockable resources, whether defined or scripted, as well as any resource acquired & holding a lock, should be present in the locking tables of anthillpro. If the locks need cleared, and cannot be revoked manually (or there are simply too many to revoke) it is possible to clean these up via SQL.		Lockable resources, whether defined or scripted, as well as any resource acquired & holding a lock, should be present in the locking tables of anthillpro. If the locks need cleared, and cannot be revoked manually (or there are simply too many to revoke) it is possible to clean these up via SQL.