> Hi! Thanks in advance for any guidance. Should the databases be "In
> Recovery" for so many hours?
[quoted text clipped - 30 lines]
> *
> *******************************************************************************
Thanks for the feedback, Linchi.
The databases are still "In Recovery". Looking at task manager, it appears
that no work is being done by SQL 2005.
Every 5 minutes this message appears in the SQL 2005 log:
Timeout occurred while waiting for latch: class
'SERVICE_BROKER_MAP_MANAGER', id 056A4BF0, type 4, Task
0x00BD47A8 : 0, waittime 57300, flags 0x98, owning task 0x00000000.
Continuing to wait.
Every minute, two messages like these appear:
Process 31:0:0 (0xde4) Worker 0x05E7C0E8 appears to be non-yielding on
Scheduler 2. Thread creation time: 12850930401031. Approx Thread CPU Used:
kernel 0 ms, user 406 ms. Process Utilization 0%. System Idle 98%. Interval:
81687633 ms.
Process 20:0:0 (0xc0c) Worker 0x057980E8 appears to be non-yielding on
Scheduler 1. Thread creation time: 12850930399359. Approx Thread CPU Used:
kernel 0 ms, user 468 ms. Process Utilization 0%. System Idle 98%. Interval:
81687633 ms.
Any ideas, anyone?
>> The time stamp counter of CPU on scheduler id 2 is not synchronized with
>> other CPUs.
[quoted text clipped - 44 lines]
>> *
>> *******************************************************************************