One of the databases in our server is in recovery mode after a huge delete job (started as a job) did not complete ( I suspect due to lack of transaction log sapce.) the log file size is 120 GB.
Whenever the server restarted the recovery for this database starts.
After 20 hours, analysis done 100% and recovery done up to 76%. Then after €œthe percentage of recovery done€? went down to 16% and it is still running.
How can I get rid of this database without damaging the master database and other database in the same instance?
I don€™t mind to lose this database.
There are 4 user databases in this instance and msdb and the recovery mode database are not operational.(I cannot connect)
We have a requirement to build SQL environment which will give us local high availability and disaster recovery to second site. We have two sites- Site A & Site B. We are planning to have two nodes at Site A and 2 nodes at Site B. All four nodes will be part of same Windows failover cluster. We will build two SQL Cluster, InstanceA will be clustered between the nodes at Site A Server and InstanceB will be clustered between the nodes at Site B, we will enable Always On Between the InstanceA and InstanceB and will be primary owner where data will be written on InstanceA and will be replicated to InstaceB. URL....Now we want we will have instanceC on the Site B and data will be writen from the application available on Site B, will be replicated to the instance on the Site A as replica.
Pages on a full recovery model database corrupted, need to ensure data loss is minimal for restore operation am thinking about restoring the latest full backup.
in the process of migrating a big db from server 1 to server 2, we had to roll back the change. I started with taking a full db backup and restoring it on server 2 with norecovery, and then a couple logs with norecovery, and then the last log with recovery.
Is there some way to continue this chain now, I mean to change the db to norecovery, or other way to restore logs.Â
I dont want to do a new full backup.
If I try to do a log restore now i get the message:
Msg 3117, Level 16, State 4, Line 1
The log or differential backup cannot be restored because no files are ready to rollforward.
We have 3 replica AG setup. 2 replicas are in sync/automatic failover, the other(DR Server, different subnet) in asynchronous/manual mode…All these replicas were on sql server 2012, Recently we upgraded DR server to 2014. Since then we have a problem, the AG databases in 2014 instance went into ‘Synchronizing/ in recovery’ state…The SQL server error log has message, the recovery couldn’t start for the database ‘XYZ’…We tried to create a new database and add it to AG , it works for fine for other two 2012 replicas, but on 2014 we see the same issue
We have an issue with a 3 node SQL 2012 Always on availability group. Normal operation is node 1 (primary replica) with node 2 and node 3 as secondary replicas.After some patching, SQL wasn't running on node 1 hence the AG flipped over to node 2. This went unnoticed for some time and the transaction log for one of the AG databases became full on node 2 and node 3. (I think this is because it couldn't commit the transactions on node 1 so couldn't truncate it's t-log?) The DB is using synchronous replication btw.So I started SQL on node 1 and flipped the AG back to node 1 (with a data loss warning but I accepted this).Now the issue is that on node 2 and 3, the DB in question is stuck in a "Reverting / In Recovery" State. I've tried various commands such as ALTER DATABASE SET ONLINE, RESTORE DATABASE WITH RECOVERY etc but these fail stating unable to obtain a lock on the DB.
The weird thing is that on node 1 the state of the DB is "synchronised".how to resolve this issue on node 2 and 3? I've left them overnight (in case they were rolling back transactions, the DB is fairly large) but nothing seems to have happened. remove the DB from the AG in node 2 and 3 and add it back in again, ie recreate the replication?
If you are doing a disaster recovery of an entire SQL 2005 cluster, can you just install SQL server and restore the system database to get the configuration?
Hi my name is Rodrigo and Im from Brasil, so, sorry about my english.
I have a problem using MSSQL 2000. I´m using a client/server application, and sometimes (almost every day) the sql server start to use 100% of CPU and crash the system. I don´t know how and when but it hapens always. I never found a reason for it, but looking at the event viewer in windows 2000 i saw an error about www publishing (something like that). Maybe my sqlserver is trying to connect to internet to do something (i don´t know). Please if somebody can help me send me a mail. Thanks a lot.
Hi, I'm trying to install SQL Server 2000 Dev Edn. When I install client and server tools it will crash after I enter the administration password. But this only happens when I install it with server tools, its OK with just client tools. Thanks
My Sql server went down last night. Is there a way to find out what could have caused system to crash? Is there any way to notify the DBA when sql services have stopped running?
Recently my computer had a crash on which SQL Server was installed. And if that wasn't enough, the backup failed to. Now I've installed SQL Server again, but I have these *.mdf and *.ldf files, which contains my data and my tables etc. So my question is, how do I get this data into my newly installed SQL Server? Maybe it's quite simple, but I can't find it. Im using SQL Server Enterprise version 7.0 on Win2k Advanced Server.
Hi, My sql server stopped unexpectedly and restarted itself today, and I have no clue why. The NT Event Viewer provides this "insight":
The MSSQLService terminated unexpectedly.
The event id is 17052, which isn't documented in BOL. Does anyone have any explanation, and some suggestions on how to avoid this in the future? thanks, Jason
Does anyone have any input on why my SQL Server keeps crashing? I get the following errors: Error : 17805, Severity: 18, State: 0 00/03/21 09:06:06.42 ods Invalid buffer received from client. 00/03/21 09:09:51.56 kernel SQL Server terminating due to 'stop' request from Service Control Manager At other times, there were some STACK DUMP ERRORS. We are on service pack 4 (I have been pushing to apply 5a) Please help, Thank you.
I got the following message in the error log when SQL Server 6.5 crashed. ''Stored function 'xp_runwebtask' in the library 'xpsqlweb.dll' generated access violation; SQL Server is terminating process 60'' Source:spid 60 Anyone know what this means ? If you think you know of have come across it before, please inform me.
I need help. I am facing following problems since days here you have the errors messages:
Mesg 18264 : DATABASE dumped with following info: Database Name:IITMSDB, Creation Date and Time:Feb 12, 99(23:00), Pages dumped:3898618, Current Sequence:36201 19370307, Sort Order:52, Striped:NO, Number of Dump Devices:1, device info:(VOLID=SS0001 NAME=iitmsdb_dump TYPE=DISK FILE=1)
Mesg 17562 : Checking space allocation for database 6
My database is marked suspect/offline in the enterprise manager. i am using sql server 2000.i have tried resetstatus,DBCC CheckDB, alter database,sp_dboption and DBCC ALLOCDB ( 'dbname' ) but all to no avail.i have no backup of the database. And i really need to get back this data.Please, can you give me a detail step by step method of how to overcome this problem. i greatly anticipate your reply!!! Thanks
Hidue to big problems (basically since a couple of month iis service crashseveral times a day) i need to format a web server (win2k, sp4, iis5.0)where all our sites are hosted .To avoid downtime i would like to transfer them all on the new server.Do i have to recreate every single web (with a lot of virtual folders ) orthere is an automatic (semiautomatic) way to migrate them all?Many thanks in advanceMarco
Hi all, I have some trouble with SQLAgent...when I try to schedule a jobthat invokes a script (vbs, java, cmdshell,...), SQLAgent crashes at themoment of scheduled execution. If I try to execute it manually, all worksfine. This installation runs on a cluster Win2003 and the node initiate afailover if I don't delete the job and then restart Agent (I can't start theservice before deleting that job!!!). Event viewer logs something like:"LOG] Exception 5 caught at line 191 of file ..src efreshr.c.SQLServerAgent initiating self-termination".I've already tried to debug the service but my dump did not help me.Any suggestion?Thankscamau
From time to time, our production system crashes and reboots while running some data warehouse load packages. There is nothing in the logs; it just seems like the reset button is pushed. The situation occurs at different moments in the batch and not every night, but lets says once every two weeks or more frequent.
We are running Windows 2003 server and SQL Server 2005 SP1 incl. hotfixes.
Does anyone of you have this issue, or is this a hardware issue without any doubt? Could there be any chance it's in the SQL Server software?
I'm running on Windows Server 2000 datacenter with sp4 and SQL Server 2000 SP4 on 16 GB AWE and /PAE enabled. Apparently the SQL Server service stops intermittently.
Below is the error I got on the application log.
"SqlDumpExceptionHandler: Process 788 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process."
This file is generated by Microsoft SQL Server 8.00.2040 upon detection of fatal unexpected error. Please return this file, the query or program that produced the bugcheck, the database and the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE. Bios Version is Phoenix ROM BIOS PLUS Version 1.10 1.1.0 Phoenix ROM BIOS PLUS Version 1.10 1.1.0 Current time is 10:27:18 07/02/07. 4 Intel x86 level 6, 2992 Mhz processor(s). Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory MemoryLoad = 82% Total Physical = 7903 MB Available Physical = 1373 MB Total Page File = 11795 MB Available Page File = 5311 MB Total Virtual = 2047 MB Available Virtual = 296 MB
*Dump thread - spid = 72, PSS = 0x41d77260, EC = 0x41d77590 * * User initiated stack dump. This is not a server exception dump. * *Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDu mp0001.txt * ***************************************************************************** ** * * BEGIN STACK DUMP: * 07/02/07 10:27:18 spid 72 * * ex_raise2: Exception raised, major=79, minor=87, severity=22 * *
Hi, i am not familiar with MSSQL so maybe it's not as difficult to you as it is to me - in brief:
SQL version: Microsoft SQL Server 7.00 - 7.00.699 (Intel X86)
Errorlog shows: Starting up database 'CH2'. Opening file E:CH2DATA1CH2DATA1.mdf. Opening file E:CH2DATA2CH2DATA2.ndf. Opening file E:CH2DATA3CH2DATA3.ndf. File D:CH2LOG1CH2LOG1.ldf does not exist - unable to activate.
Enterprise Manager Shows database CH2 (suspect)
Executing script: sp_add_log_file_recover_suspect_db CH2, CH2LOG1, 'D:CH2LOG1CH2LOG1.ldf', 1000 Shows errormessage "The database 'CH2' does not exist."
How can i get a new logfile? What if i created a new db 'CH2' and then replaced the data files? What do i have to tell MSSQL to create a new logfile on startup? All scenarios shown in Books On Line only seem to solve problems if you do have a logfile and need more space.
-----Original Message----- From: Driggers, John To: 'SQL Discussions' Sent: 10/27/99 9:10 AM Subject: FW: Weekly server hang
I also see the one below prior to another crash....going through tech net now...but not seeing anything that reflects the messages below. The results from searching on "Exception_Access_Violation" I'm not sure apply in my case...also looks like I have at least two causes of crashes (how can one interpret the below statements???)
Thanks, John --------------------
99/10/24 10:38:00.06 spid10 EXCEPTION_ACCESS_VIOLATION raised, attempting to create symptom dump 99/10/24 10:38:00.06 spid10 Initializing symptom dump and stack dump facilities 99/10/24 10:38:02.61 spid10 ***BEGIN STACK TRACE*** 99/10/24 10:38:02.61 spid10 0x00404CD9 in SQLSERVR.EXE, rm_ods_handler() + 0x0329 99/10/24 10:38:02.64 spid10 0x00405571 in SQLSERVR.EXE, st_do_enlist() + 0x00C1 99/10/24 10:38:02.64 spid10 0x004071CA in SQLSERVR.EXE, CDTCState::init() + 0x033A 99/10/24 10:38:02.65 spid10 0x005A70A3 in SQLSERVR.EXE, lddb_fixdbosuid() + 0x0423 99/10/24 10:38:02.68 spid10 0x005A6CC2 in SQLSERVR.EXE, lddb_fixdbosuid() + 0x0042 99/10/24 10:38:02.68 spid10 0x005963CB in SQLSERVR.EXE, textalloc() + 0x04CB 99/10/24 10:38:02.71 spid10 0x00463F4B in SQLSERVR.EXE, agghaving() + 0x004B 99/10/24 10:38:02.71 spid10 0x00409829 in SQLSERVR.EXE, opencheck() + 0x0089 99/10/24 10:38:02.71 spid10 0x00427B09 in SQLSERVR.EXE, tbswritecheck() + 0x0969 99/10/24 10:38:02.71 spid10 0x00250FED in opends60.dll 99/10/24 10:38:02.71 spid10 0x0025055B in opends60.dll 99/10/24 10:38:02.71 spid10 0x002414D1 in opends60.dll 99/10/24 10:38:02.71 spid10 0x00241384 in opends60.dll 99/10/24 10:38:02.71 spid10 0x10219D84 in MSVCRT40.dll 99/10/24 10:38:02.71 spid10 0x77F04F3E in KERNEL32.dll 99/10/24 10:38:02.71 spid10 ***END STACK TRACE***
Cindy, nothing in the NT logs but found this in the SQL logs:
99/10/25 09:25:15.45 spid71 EXCEPTION_ACCESS_VIOLATION raised, attempting to create symptom dump 99/10/25 09:25:15.45 spid71 Initializing symptom dump and stack dump facilities 99/10/25 09:25:20.45 spid71 ***BEGIN STACK TRACE*** 99/10/25 09:25:20.46 spid71 0x00404CD9 in SQLSERVR.EXE, rm_ods_handler() + 0x0329 99/10/25 09:25:20.52 spid71 0x005725C1 in SQLSERVR.EXE, stuff() + 0x0241 99/10/25 09:25:20.54 spid71 0x0056D35F in SQLSERVR.EXE, ncrid_update() + 0x057F 99/10/25 09:25:20.57 spid71 0x0051DD35 in SQLSERVR.EXE, prRESOURCE() + 0x0055 99/10/25 09:25:20.57 spid71 0x00464C65 in SQLSERVR.EXE, genbuiltin() + 0x0445 99/10/25 09:25:20.59 spid71 0x00427B09 in SQLSERVR.EXE, tbswritecheck() + 0x0969 99/10/25 09:25:20.62 spid71 0x00250FED in opends60.dll 99/10/25 09:25:20.62 spid71 0x0025055B in opends60.dll 99/10/25 09:25:20.62 spid71 0x002414D1 in opends60.dll 99/10/25 09:25:20.62 spid71 0x00241384 in opends60.dll 99/10/25 09:25:20.62 spid71 0x10219D84 in MSVCRT40.dll 99/10/25 09:25:20.62 spid71 0x77F04F3E in KERNEL32.dll 99/10/25 09:25:20.62 spid71 ***END STACK TRACE***
This proceeds my 'crashes', which it looks scary enough to do the trick!
Any idea what could be causing this exception?
Thanks, John
ps. someone else mentioned backup software - we use BackupExec and I have a sched. task that dumps one of the databases to a network drive 2x day. But these are running throughout the week...looking over the logs I really don't see a correlation...(ie. these same processes run on days that no crash occurs and successfully later in the day that the crashes do occur (some hours earlier).
-----Original Message----- From: Gross, Cindy [mailto:CindyGross@hmhs.com] Sent: Monday, October 25, 1999 2:14 PM To: SQL 6.5 Discussions Subject: RE: Weekly server hang
Did you check the SQL Server errorlog (sometimes things are written here that don't go to the event viewer) and the NT event viewer (application and system)?
You could try turning on SQL Trace to see if you can capture a "bad" query but depending on how SQL goes down it may not be captured.
If you are auditing successful logons you could take a look to see if there is any pattern in who logs in just before SQL restarts.
Any chance someone is actually stopping it on purpose? Or maybe a program that is stopping it (maybe a backup system trying to backup the device files instead of the dumps)?
Cindy Gross SQL Server MCP Texas Health Resources http://members.tripod.com/cindygross/sqlsrvr.htm
> -----Original Message----- > From:Driggers, John [SMTP:John_Driggers@spspay.com] > Sent:Monday, October 25, 1999 12:26 PM > To: SQL 6.5 Discussions > Subject: Weekly server hang > > List-Unsubscribe: <mailto:leave-mssql-13928C@ls.swynk.com> > List-Software: Lyris Server version 3.0 > List-Subscribe: <mailto:subscribe-mssql@ls.swynk.com> > List-Owner: <mailto:owner-mssql@ls.swynk.com> > X-URL: <http://www.swynk.com/sysapps/sql.asp> > X-List-Host: swynk.com discussion lists <http://www.swynk.com> > Reply-To: "SQL 6.5 Discussions" <mssql@ls.swynk.com> > X-Message-Id: <06F417B00B8CD1119BA400008322DF6D03515E78@spsgex01> > Sender: bounce-mssql-14964@ls.swynk.com > Precedence: bulk > > This one is bugging the tar out of me. Running SQL 6.5 sp5a, NT4 sp4 on > the > server. Either on the weekend or Mon. mornings (happened all 3 days this > past week) the SQL service stops on the server. This is during low usage > times. The box is a DELL 4300 dual 450 w 512 RAM (250 dedicated to SQL). > All > other services on the server are ok, except for SQL. > > I'm thinking maybe a bad query hitting the server (I've seen this happen > before) but the programmers claim there is nothing special about these > time > periods that something "unique" would be happening. After I restart the > server it may not happen until the next week (this past weekend being an > exception). I thought maybe I had a memory leak but running perf. monitor > before a crash once revealed 99+% data cache, available proced. crash, low > CPU usage, low swapping....anything else I could check? > > Maybe reinstalling the sp5a? Any suggestions on things to try would be > most > appreciated... > > Thanks, John > > > ------ > FAQ: http://www.swynk.com/faq/sql/sqlserverfaq.asp > Please post SQL Server 7.0 questions to the SQL 7 list > http://ls.swynk.com for list server signup/maint options > You are subscribed as cindygross@hmhs.com > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to leave-mssql-13928C@ls.swynk.com
------ FAQ: http://www.swynk.com/faq/sql/sqlserverfaq.asp Please post SQL Server 7.0 questions to the SQL 7 list http://ls.swynk.com for list server signup/maint options You are subscribed as John_Driggers@spspay.com Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to leave-mssql-13928C@ls.swynk.com
Hi, What is the simplest way to crash a sql server? Somebody asked me that question, and I was unable to give the best answer. Please help me to find it. Thanks!! Joydeep
Hi all, I was wondering if you's could help me out. We run sql optimization on 2 of our databases and when they run they cause our server to crash - system log reports: unexpected shutdown. When we take these jobs out of action the server does not crash.
I'm not sure if this could be a CPU or memory related issue or if its a SQL configuration issue?
I am not sure if this is the right forum, but a sql crash might cause data corruption ?!
Anyway I have tried this on 2 different sql2005 sp1 installations. (Developer Edition) And in both cases the last piece of code causes the sql server to stop cold (crash).
script originally posted here(afaik): ### link removed ###
#################### I removed the script Didn't seem like a good idea to make this kind of thing public ####################
Hi All,Our SQL Server just crashed with the following messages:The Scheduler 5 appears to be hung. SPID 85, ECID 0, UMS Context 0x06C22478.Error: 17883, Severity: 1, State: 0We are running SP3 on cluster on a SAN.Any ideas?ThanksMichael
Importing DBase files I get to the screen titled "Select Source Tableand Views" And none appear in the list. (I can get the list displayedabout once in ten tries) From that screen anything causes a crash ofthe wizard and Enterprise Manager. This happens on my deveopmentinstallation of Enterprise Manager Version 8.0.Any Ideas/ PleaseJohn Cooper
