SYSERR3930 on validation

Question

Hi,

I've just look into the SQL Server log or our test MDS Server and found this very helpful errors, excuse the irony.

Message
The activated proc '[mdm].[udpValidationQueueActivate]' running on queue 'FOMMDR.mdm.microsoft/mdm/queue/validation' output the following:  'SYSERR3930|The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.'

followed by

Message
The activated proc '[mdm].[udpValidationQueueActivate]' running on queue 'FOMMDR.mdm.microsoft/mdm/queue/validation' output the following:  'The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.'

Any ideas on how to troubleshoot the validation queue are more than welcome.

Kind regards,

M

Answer 1

Hi,

I am not a 100% sure about this but this appears to be caused by a full tempdb transaction log (caused in turn by a full disk). Hopefully somebody from the MDS team can answer the few simple questions at the end of this message.

The last occurrence of that error was followed by the following messages in this order

Message - Error: 17053, Severity: 16, State: 1.

Message - C:\Program Files\Microsoft SQL Server\MSSQL11.SQL2012\MSSQL\DATA\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.

Message - The activated proc '[mdm].[udpValidationQueueActivate]' running on queue 'FOMMDR.mdm.microsoft/mdm/queue/validation' output the following:  'The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'. '

Message - Error: 9002, Severity: 17, State: 4.

Message - The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'.

Message - Error: 3998, Severity: 16, State: 1.

Message - Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.

Questions

1) Does MDS use tempdb  for its validation?

2) Is there a way to control this? The tempdb log on the server was 60GB big, a little too big for my taste and unless a maintenance job is in place it does not release any used space.

3) What happened with the data affected by the transaction rolled back? Was there any data loss?

Kind regards,

M