Error 5149 Status 1 Severity 25
Contents |
360 games PC games error: 1453, severity: 16, state: 1. Windows games Windows phone games Entertainment All Entertainment
Error: 1454, Severity: 16, State: 1.
Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
takes a licking but it keeps onticking! Posted on March 30, 2010 by Glenn Berry With apologies to Timex, I just wanted to relate a minor incident that happened with one of my mirrored databases last night. This database needed to grow its primary data file, and the autogrow amount was set to 5GB ( I have Windows Instant File Initialization enabled). Unfortunately, there was less than 5GB of available disk space on the drive array on the mirror where this data file lived. I know, bad DBA… The data file grew on the principal, but when database mirroring sent the file growth command to the mirror https://support.microsoft.com/en-us/kb/975681 side, it was not able to complete the operation, and mirroring was suspended for that database. I first noticed this when I saw that my log reuse wait description for that database was DATABASE_MIRRORING, and my transaction log was 71% full on the principal. I could also see that I had about 47GB of unsent log on the principal. The first thing I tried was resuming the mirror by issuing https://sqlserverperformance.wordpress.com/2010/03/30/sql-server-2008-database-mirroring-it-takes-a-licking-but-it-keeps-on-ticking/ this command: ALTER DATABASE ngfulltext1 SET PARTNER RESUME; This had no effect, so then I looked in the SQL Error Log on the Principal, and saw this error: TCP://SQLMIRROR01.xxx.xxxxxx.com:5022′, the remote mirroring partner for database ‘ngfulltext1', encountered error 5149, status 3, severity 16. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. Next, I looked in the SQL Error Log on the instance where the mirror was located, and saw these two errors: MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file ‘P:\SQLData\ngfulltext1.mdf'. P:\SQLData\ngfulltext1.mdf: Operating system error 112(There is not enough space on the disk.) encountered. So duh, I was out of disk space on the P: drive. Again, dumb DBA, but luckily this was easy to fix by deleting some old backup files. After I did this, I resumed the mirroring session, which worked this time. SQL Server started rapidly sending the unsent log from the principal to the mirror (at about 58MB/sec). The way database mirroring behaves in this situation is that it sends a pretty decent chunk of the unsent log to mirror and then stops the send
feel free to Contact me This Blog Home Contact About Syndication RSS http://sqlblogcasts.com/blogs/blakmk/archive/2008/06/26/mirroring-issues.aspx Atom Search Go Navigation HomeBlogsPhotosDownloads News Subscribe in a reader
http://mattsnotes.com/sql-server/why-is-the-sql-server-mirroring-suspended Tags 2008 always on AMD BI dashboard capacity planning Carbon Footprint Consolidation CPU Affinity CTP GDR1 SP2 Database Mirroring datasets DBA DBMIRROR_SEND Deadlock graph Developer DNS DR Extended events Fragmentation GUID Hardware Hyperthreading Intel java jdbc MDX mirroring Nehalem Network network encryption NUMA severity: 16, odbc PowerPivot Self Service reporting sla Sql Sql Server sql Server 2012 SSAS SSMS SSRS twitter UK WAN Windows 2008 Server Recent Posts Calculating estimated data loss with Always on SELECT * FROM Sql tweeters WHERE location = ‘UK’ Connecting to named Instances Using Port Number Transferring aliases from Sql Server Configuration manager between severity: 16, state: machines T-SQL Tuesday #12 – Why are DBA skills necessary? Archives December 2012 (1)December 2010 (2)November 2010 (2)October 2010 (2)August 2010 (2)July 2010 (3)June 2010 (2)April 2010 (3)January 2010 (2)December 2009 (1)June 2008 (3)May 2008 (2) Mirroring issues I recently came across this error message: the remote mirroring partner for database *********, encountered error 5149, status 1, severity 25. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. I hate undocumented error messages so I thought I’d add my resolution. It appears that the log file on the mirror site was unable to extend the log file. The network connection dropped for a time and the build up of unsent transactions caused the primary log file to extend, when the network connection was re-established the mirrored logfile was unable to exend by the same amount. The moral of the story is to always allow enofor mirroring to be suspended. Often you can just resume mirroring and it resolves itself. Check the logs From SQL Server Management Studio go to Management/SQL Server Logs and open the current log. 5149 Errors The primary error log contains the following error: 'TCP://STANDBY:10022', the remote mirroring partner for database 'MyDatabase', encountered error 5149, status 3, severity 25. Database mirroring has been suspended. Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance. Check the error log from the mirror server. For example: 09/16/2013 07:03:10,spid150s,Unknown,Bypassing recovery for database 'MyDatabase' because it is marked as a mirror database