Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

time stamp counter... not synchronized

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jim - 25 Mar 2008 21:14 GMT
Hi!  Thanks in advance for any guidance.  Should the databases be "In
Recovery" for so many hours?

Windows Server 2003 SP1
SQL Server 2005 SP2

Attempted to restart SQL Server, as "Databases" were not shown in Mgmt
Studio.  Attempt to restart failed, so restarted machine. 7 of the 27
databases have been "In Recovery" for 5 hours since the restart of the
machine.

SQL log shows a few messages like this in the last hour:

The time stamp counter of CPU on scheduler id 2 is not synchronized with
other CPUs.

Every minute, there are two SQL log messages like this:

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 390 ms. Process Utilization 0%. System Idle 98%. Interval:
15866917 ms.

There is also a couple like this in the log:
*
*******************************************************************************
*
* Non-yielding Scheduler
*
*   03/25/08 09:54:52 spid 0
* BEGIN STACK DUMP:
*
*
*******************************************************************************
Linchi Shea - 26 Mar 2008 03:54 GMT
> The time stamp counter of CPU on scheduler id 2 is not synchronized with
> other CPUs.

This message should not have anything directly to do with your long recovery
time.

The worker non-yielding message however can potentially be related to the
long recovery time.

Linchi

> Hi!  Thanks in advance for any guidance.  Should the databases be "In
> Recovery" for so many hours?
[quoted text clipped - 30 lines]
> *
> *******************************************************************************
Jim - 26 Mar 2008 14:47 GMT
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]
>> *
>> *******************************************************************************
Rubén Garrigós - 26 Mar 2008 18:01 GMT
I have had similar log error entries about sync problems between schedulers
when you have dynamic frequency processors. Try setting "Always On" or "Max
Performance" power profile in Power Options in your Control Panel.

Signature

Rubén Garrigós
Solid Quality Mentors

> Hi!  Thanks in advance for any guidance.  Should the databases be "In
> Recovery" for so many hours?
[quoted text clipped - 30 lines]
> *
> *******************************************************************************
Jim - 26 Mar 2008 20:01 GMT
Thanks for the feedback, Ruben!

The "In Recovery" databases were deleted (after shutting down SQL Server,
and moving the data and log files).  Then the machine was restarted.  The
messages stopped.  Now we're restoring the databases from backups.

Once again, all seems fine!

>I have had similar log error entries about sync problems between schedulers
>when you have dynamic frequency processors. Try setting "Always On" or "Max
[quoted text clipped - 34 lines]
>> *
>> *******************************************************************************
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.