- 3 minutes to read

Orphaned DTA Service Instances

Info
Receive instant alerts and take action when the number of Orphaned DTA Service Instances exceeds your user-defined monitoring threshold.

When the DTA Archive and Purge SQL Server Agent job archives and deletes tracking data from the BizTalk Server Tracking database (BizTalkDTADb), orphaned rows can accumulate in the dta_ServiceInstanceExceptions table. This issue often occurs when a message instance is resumed and then fails again, generating multiple rows with the same uidServiceInstanceId and uidActivityId. If these orphaned DTA service instances are not removed by the DTA Purge and Archive job, the BizTalkDTADb database can grow excessively large.

Example of a problem with Orphaned DTA Service Instances.

Category Name = "Health Check"
Resource Name = "Orphaned DTA Service Instances"

What's evaluated for Orphaned DTA Service Instances?

Nodinite evaluates the state of the Resource Orphaned DTA Service Instances based on your user-defined thresholds:

State	Status	Description	Actions
Unavailable	Resource not available	Evaluation of the 'BizTalk Orphaned DTA Service Instances' is not possible due to network or security issues	Review prerequisites
Error	Too many instances exist	Number of instances exceeds the configured threshold	Details
Warning	Too many instances exist	Number of instances exceeds the configured threshold	Details
OK	Not too many instances exist	Number of instances is below configured thresholds	Details

Tip
You can reconfigure the evaluated state using the Expected State feature on every Resource within Nodinite.

What remote actions are available?

Details – Show the number of instances and remove orphaned instances.
Edit – Manage thresholds (not yet implemented on Resource level).
Metrics chart – View statistics for the number of rows over time.

Example of available Remote Actions.

Details

Click the Actions button, then select Details to view the current row count.

Example of the Details menu item.

Details about the Spool Count and Monitoring thresholds.

When Orphaned DTA Service Instances exist, click the Actions button and select Remove to set the dtEndTime values for orphaned instances. This enables the DTA Purge and Archive job (SQL Agent job) to clean these rows on the next run.

Example with the Actions button.