SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


corruption of writing log buffer


corruption of writing log buffer

Author
Message
Oracle_91
Oracle_91
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3358 Visits: 1742
Hi All,

What is this error ? any idea why do we see such kind of errors?

LogWriter: Operating system error 170(The requested resource is in use.) encountered.

Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 170(The requested resource is in use.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Database msdb was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.


Thanks in Advance.
Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)SSC Guru (98K reputation)

Group: General Forum Members
Points: 98368 Visits: 38996
Oracle_91 (8/14/2012)
Hi All,

What is this error ? any idea why do we see such kind of errors?

LogWriter: Operating system error 170(The requested resource is in use.) encountered.

Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 170(The requested resource is in use.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Database msdb was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.


Thanks in Advance.





And what error(s) are shown in the event log?

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Oracle_91
Oracle_91
Hall of Fame
Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)Hall of Fame (3.4K reputation)

Group: General Forum Members
Points: 3358 Visits: 1742
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] OnlineThread: Error 1 bringing resource online.
19019 Failover "[sqsrvres] OnlineThread: service stopped while waiting for QP.
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
19019 Failover "[sqsrvres] CheckServiceAlive: Service is dead
3449 Server SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
9001 Server The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server fcb::close-flush: Operating system error (null) encountered.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
9001 Server The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
9001 Server The log for database 'msdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
17053 Server fcb::close-flush: Operating system error (null) encountered.
17053 Server fcb::close-flush: Operating system error (null) encountered.
9001 Server The log for database 'BizTalkMsgBoxDb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
17053 Server LogWriter: Operating system error 170(The requested resource is in use.) encountered.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
4098 None Error Initializing TSM Api, unable to verify Registry Password, see dsierror.log.
nt options file)
kyleheath33
kyleheath33
Old Hand
Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)Old Hand (369 reputation)

Group: General Forum Members
Points: 369 Visits: 811
From the error posted looks like you have .ldf files for tempdb, msdb and BizTalkMsgBozDB. Is the drive which held these files still online?

Got backups off those databases?

The tempdb and msdb are system databases and worse case scenario can be rebuilt, however the BizTalk DB may need some extra work but a restore would be the quickest and safest way.
Dream Weaver
Dream Weaver
SSC Veteran
SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)

Group: General Forum Members
Points: 280 Visits: 315
I don't have a solution (still looking), but I do have some advice. Before you start anything as drastic as database restores, try simply restarting the server. When I've encountered this error, a restart has been sufficient--it clears whatever file handle was preventing SQL Server's access to the file.

I have not yet been able to figure out what was causing the error in the first place. Process Explorer seemed to be saying that SQL Server had the only handle to the file.



Simon Millar
Simon Millar
Grasshopper
Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)Grasshopper (20 reputation)

Group: General Forum Members
Points: 20 Visits: 83
Investigate your SAN performance. We have experienced this exact situation on a Virtualized SQL Server where it appeared that Data, Log, TempDb and Backups were on separate LUNs, but the associated virtual disks (VMDKs) had all been placed on a single VMWare DataStore, which was actually a single LUN presented from the SAN, due to usage of EMC Storage Pools. All IO was actually going thru 1 path at VMWare Host level. Every time we'd get the OS 170 Error, without associated Disk Errors in the System Event Log (suspect due to disk.sys timeout values Registry being increased by VMWare vSCSI drivers). Fix was Storage vMotion to faster Storage Pool on SAN. (Still not happy with single DataStore though!)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search