[msmom] RE: Data Warehouse Error --> SQL - TimeOut Expired
Most of the time - when I see these - it comes down to either too much data coming in (too many alerts/perf date from agents) or poor disk I/O on the database servers.
Run perfmons on the DB server logical disks, collecting every 1 second, for avg disk sec/read and avg disk sec/write. If you are *sustained* above 15ms, you have poor disk I/O. It is normal to see short bursts that can be very high - but these bursts should recover quickly. It is also normal to see these be sustained high during specific periods, like DB maintenance, backups, grooming, etc....
If they don't recover in a few seconds, or are sustained high all the time - you need to improve disk I/O, or reduce data volume incoming, or both.
-----Original Message-----
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Schleicher, Bob
Sent: Wednesday, August 26, 2009 10:05 PM
To: msmom@lists.myitforum.com
Subject: [msmom] Data Warehouse Error --> SQL - TimeOut Expired
Last couple of weeks, have been getting these errors from our two mgmt servers:
performance data collection process unable to write data to the Data Warehouse. Data was written to the Data Warehouse staging area but processing failed on one of the subsequent operations. Exception 'SqlException': Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
Checked around and found this link:
http://relatedterms.com/ViewThread.aspx?t=1011243
2nd alert that seems to come along is related to getting Alert subscriptions
Alert subscription data source module encountered alert subscriptions that were waiting for a long time to receive an acknowledgement. Alert subscription ruleid, Alert subscription query low watermark, Alert subscription query high watermark: 70d72228-7c3a-6b56-23a7-de21c37733d2,08/25/2009 18:44:29, 08/25/2009 18:45:49
Are they related?? Other trouble shooting ideas??
Environment is OpsMgr 2007 SP1, patched per Kevin H's blog, running sql grooming based on localized txt rows clean up per Kevin H.'s blog.
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
While this communication may be used to promote or market a transaction
or an idea that is discussed in the publication, it is intended to provide
general information about the subject matter covered and is provided with
the understanding that The Principal is not rendering legal, accounting,
or tax advice. It is not a marketed opinion and may not be used to avoid
penalties under the Internal Revenue Code. You should consult with
appropriate counsel or other advisors on all matters pertaining to legal,
tax, or accounting obligations and requirements.
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/momlist/
Trackbacks
No Trackbacks
Comments
No Comments
