Error 5149 Status 1 Severity 16
Contents |
to transaction logs If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.
Error: 1453, Severity: 16, State: 1.
To start viewing messages, select the forum that you want to visit from the error: 1454, severity: 16, state: 1. selection below. Results 1 to 11 of 11 Thread: SQL 2008 Mirroring running out of disk space due to transaction logs Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-28-10,13:47 #1 Qik View Profile View Forum Posts Registered User Join Date Dec 2010 Posts 6 Unanswered: SQL 2008 Mirroring running out of disk space due to transaction logs Last month I mirrored a SQL 2008 db to another server running sql 2008. Everything was fine until last week. The backups went from 60GB to 220GB in about 1 weeks time. I checked the mirror and noticed it is in a suspended state. I then checked the folder holding the transaction log file for the principal db and noticed it was over 150gb in size but the actual db is only 2gb. On the mirror server I am seeing a 2GB file which matches the principal db but I am am also seeing a 48GB file which has the same name as the principal db with a "_1" after it. I have a second file which is only a few meg and it is being mirrored on the same servers with no issue. I am getting desperate and planning to drop the mirror before my prodcution servers comes to a halt. Suggestions? I see the followin on the Principal server: Log Name: Application Source: MSSQLSERVER Date: 12/28/2010 10:28:16 AM Event ID: 1453 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: DB.lp.local Description: 'TCP://SQLREPL.lp.local:5022', the remote mirroring partner for database 'UTOPIA', 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. and the following on the mirror server Log Name: Application Source: MSSQLSERVER Date: 12/28/2010 10:28:16 AM Event ID: 5149 Task Category: Server Level: Error Keywords: Classic User: N/A Computer: SQLREPL.lp.local Description: MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expan
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 side, it was not able http://www.dbforums.com/showthread.php?1663160-SQL-2008-Mirroring-running-out-of-disk-space-due-to-transaction-logs 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 this command: ALTER DATABASE ngfulltext1 SET PARTNER https://sqlserverperformance.wordpress.com/2010/03/30/sql-server-2008-database-mirroring-it-takes-a-licking-but-it-keeps-on-ticking/ 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. It can generally send the log much faster than it can be restored (dependi
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Mirroring has been stopped since long time, I https://social.msdn.microsoft.com/Forums/sqlserver/en-US/080d9a9c-a634-4742-8ac5-9e32befc1b11/mirroring-has-been-stopped-since-long-time-i-am-resuming-but-still-it-is-showing-as-suspended?forum=sqldatabasemirroring am resuming but still it is showing as suspended SQL Server > Database Mirroring Question 0 Sign in to vote I have 2 SQL servers. One principal and the other is used as Mirror. Currently both servers are up and also both databases. But the mirroring is shown as Suspended. I am trying it to resume by clicking on the severity: 16, resume button on the properties screen of the principal database, but again it is showing as Paused and status is still Suspended. It is in the production environment and highly critical. Please advise what to do? Monday, August 18, 2008 5:26 PM Reply | Quote Answers 0 Sign in to vote I would suggest please check , severity: 16, state: Right click > Task>Launch Database mirroring monitor>Select registered database (If not register then register it)>Check the Status tab > then next column called "Principal Log"&'Mirrored Log'. there check Unsent log /Unrestored Log and current send rate which will help to understand the Bottleneck. If the problem seems to be Network then take a diffrential backup of princial and restored on mirrored after removing mirroirng. If the network is bottleneck then it might get fail at reconfiguring. it will be syncronised when Network will be in normal state , i encountered in my scenerio. So i tried after some time it was success. Also follow as Vidhya Sagar Suggestion for using Witness if not using. BRPraveen Barath Tuesday, August 19, 2008 9:30 AM Reply | Quote Answerer 0 Sign in to vote Ok, The unsent log is 18605298 KB and restoring rate is 0, means there is problem where it is not able to restore might be heavy conjetion in network. I would suggest follow the steps; Remove mirroring. Truncate Log of p