Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Rebuild/Repair corrupt LDF
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

jackyy
Starting Member

USA
4 Posts

Posted - 11/19/2008 :  16:47:53  Show Profile  Reply with Quote

New to the forum and found this in the SQL 2000 forum. Tried the steps and received this message:

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
Msg 259, Level 16, State 1, Line 4
Ad hoc updates to system catalogs are not allowed.
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.

Any thoughts?

The original thread is here:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=39820

nr
SQLTeam MVY

United Kingdom
12543 Posts

Posted - 11/19/2008 :  21:01:45  Show Profile  Visit nr's Homepage  Reply with Quote
The statements you actually ran rather than just the message would be nice.

Did you run reconfigure after changing the allow updates and before doing your system table update?
And did you run it as a separate batch?


==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

jackyy
Starting Member

USA
4 Posts

Posted - 11/19/2008 :  21:06:24  Show Profile  Reply with Quote
Statements re in the link at the bottom of my post. I can post them in here if you want but I thought it might be useful to see where I got the info from also.

Here is what I was trying to do from the original thread...now 4 yrs old I just realized!

Posted - 09/13/2004 : 16:27:41 Show Profile Reply with Quote
Solution:
LISTING 1: Undocumented DBCC Command REBUILD_LOG
EXEC sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO

BEGIN TRAN

UPDATE master..sysdatabases
SET status = status | 32768
WHERE name = 'MyDatabase'

IF @@ROWCOUNT = 1
BEGIN
COMMIT TRAN
RAISERROR('emergency mode set', 0, 1)
END
ELSE
BEGIN
ROLLBACK
RAISERROR('unable to set emergency mode', 16, 1)
END

GO

EXEC sp_configure 'allow updates', 0
RECONFIGURE WITH OVERRIDE
GO

-- Restart SQL Server at this point.

DBCC REBUILD_LOG('MyDatabase','C:\MyDatabase.ldf')


/*Perform physical and logical integrity checks at this point.
Bcp data out if your integrity checks demonstrate that problems exist.
*/

ALTER DATABASE MyDatabase SET MULTI_USER
GO

-- Set database options and recovery model as desired.
GO


---

Incidentally, I realize that "detatching" a database should be utilized before one should ever hope to be able to reliably follow with "attach db", but these were the cirumstances that I was given: Two files, mdf and ldf, and the ldf is corrupt so all attach methods were failing.

The above REBUILD_LOG works WONDERFULLY, although there are obviously data integrity caveats. It has, however, successfully taken the database out of 'suspect' and replaced the .ldf file nicely in this instance.
Go to Top of Page

jackyy
Starting Member

USA
4 Posts

Posted - 11/24/2008 :  15:31:40  Show Profile  Reply with Quote
Anyone have any suggestions of where to start on this or am I just screwed?
Go to Top of Page

darkdusky
Aged Yak Warrior

591 Posts

Posted - 11/25/2008 :  11:24:58  Show Profile  Reply with Quote
Is the original advice in the previous forum not helpful - i.e restore from backups - i.e the *.BAK and *.TRN files?
Go to Top of Page

celestia
Starting Member

United Kingdom
2 Posts

Posted - 11/26/2008 :  04:45:46  Show Profile  Reply with Quote
The answer is in the error: Ad hoc updates to system catalogs are not allowed.

In SS2K ad hoc changes to system tables weren't supported, in SS2K5 they are not allowed. As darkdusty said, there are documented (ie supported) ways of doing what you want.
Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

Sweden
30421 Posts

Posted - 11/26/2008 :  05:18:41  Show Profile  Visit SwePeso's Homepage  Reply with Quote
You can attach the database with recreating the LDF with

sp_attach_single_file

or, it you are using sql server 2005 and later, ALTER DATABASE ...



E 12°55'05.63"
N 56°04'39.26"
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 11/27/2008 :  06:24:14  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
In 2005 there's now a documented way to set a database into emergency mode and the hack updating sysdatabases is no longer needed.

ALTER DATABASE ... SET EMERGENCY

What's the situation of the DB, what have you tried?

--
Gail Shaw
SQL Server MVP
Go to Top of Page

yogeshbhoyar
Starting Member

India
1 Posts

Posted - 02/04/2009 :  04:42:54  Show Profile  Reply with Quote
I am working on SQL Server 2005 and our database log file (ldf) was deleted so i am tring to recover the ldf file and i was tried all these methods to recover missing LDF file but it does not execute properly when i execute the statement

EXEC sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO

it displays following message

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
Msg 259, Level 16, State 1, Line 4
Ad hoc updates to system catalogs are not allowed.
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.

please give me some idea to recover ldf file
thanks!!
Go to Top of Page

sodeep
Flowing Fount of Yak Knowledge

USA
7174 Posts

Posted - 02/04/2009 :  09:16:22  Show Profile  Reply with Quote
quote:
Originally posted by yogeshbhoyar

I am working on SQL Server 2005 and our database log file (ldf) was deleted so i am tring to recover the ldf file and i was tried all these methods to recover missing LDF file but it does not execute properly when i execute the statement

EXEC sp_configure 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO

it displays following message

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
Msg 259, Level 16, State 1, Line 4
Ad hoc updates to system catalogs are not allowed.
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.

please give me some idea to recover ldf file
thanks!!



Have you tried attaching mdf file with sp_attach_single_file?
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 02/04/2009 :  11:49:37  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
You can't change the system tables in SQL 2005.

Can you expand a bit on what happened? How did the log get deleted? Do you have a backup?

--
Gail Shaw
SQL Server MVP
Go to Top of Page

sourav_tech
Starting Member

India
1 Posts

Posted - 07/12/2009 :  07:03:02  Show Profile  Reply with Quote
Hello There

Can you suggest me the steps needed to follow up Rebuild the corrupt LDF file in SQL Server 2005\2008??

The dbcc rebuild_log() command doesn't work in SQL 2005\08!

Regards
Sourav
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 07/12/2009 :  11:15:38  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
Restore from backup if you have one.
If you don't (why not), try setting the DB into emergency mode and doing a repair.

ALTER DATABASE <DB name> SET EMERGENCY
DBCC CHECKDB ('<DB name>',REPAIR_ALLOW_DATA_LOSS)



--
Gail Shaw
SQL Server MVP
Go to Top of Page

dekj
Starting Member

USA
4 Posts

Posted - 02/01/2011 :  19:17:44  Show Profile  Reply with Quote

I found a way to recreate the log file. I tried many things, and eventually found myself with the database, which I will call POSProd throughout this example, offline and with no way to bring it online. Here is the step-by-step procedure I eventually followed.

1) Stop the SQL Server Management Studio. At a command prompt, enter

net stop "SQL Server (MSSQLSERVER)"

this ended up stopping the SQL Server and the SQL Server Agent.

2) Rename out the old MDF (and NDF) files. Copy them as well if you have space, so if you eventually corrupt the original files, you will still have something to work with. My files were over 2 TB long, and this took 6 hours

3) Restart the SQL Server and SQL Server Agent. . At a command prompt, enter

net start "SQL Server (MSSQLSERVER)"
net start "SQL Server Agent (MSSQLSERVER)"

This restarted these two services, which had been stopped previously.

4) In SQL Server Management Studio, right-click the POSProd database, and delete it.

5) Right-click Databases, and create a new POSProd database, with the same files as the old one. For me, this included the MDF file, the LDF file, and the NDF file.

6) Stop the SQL Server Management Studio. At a command prompt, enter

net stop "SQL Server (MSSQLSERVER)"

this ended up stopping the SQL Server and the SQL Server Agent.

7) Delete the new MDF (and NDF) files, but leave the LDF log file.

8) Rename the old MDF (and NDF) files back to their original names

9) Restart the SQL Server and SQL Server Agent. . At a command prompt, enter

net start "SQL Server (MSSQLSERVER)"
net start "SQL Server Agent (MSSQLSERVER)"

This restarted these two services, which had been stopped previously.

10) At this point, you will have a POSProd database pointing to the correct database files, but also to an LDF log file that is still not attached to them. It seems that they are all related with GUIDs or something, and the LDF GUID is still incorrect, so you will still not be able to act on the database. DON’T DO ANYTHING ELSE WITH THE DATABASE EXCEPT WHAT I HAVE DONE BELOW. I don’t know what effect that will have on the database.

11) Open a new query in SQL Server. Alter the POSProd database to emergency mode

alter database POSProd set emergency

12) Set the database to single user mode. Without this, the checkdb command won’t run.

ALTER DATABASE [POSProd] SET SINGLE_USER WITH NO_WAIT

13) Run dbcc checkdb

dbcc checkdb ('POSProd',repair_allow_data_loss)

Once again, because the database was about 2 TB, this ran for about 10 hours. Its listing showed many errors, but also noted that the LDF file was recreated for the original POSProd files. This looked very interesting.

14) Alter the database back to multi user mode

ALTER DATABASE [POSProd] SET MULTI_USER WITH NO_WAIT

15) Set the database online.

alter database POSProd set online

16) Now you still do not have a good database, because SQL Server still knows about the old database. So detach the database by right-clicking the POSProd database, and selecting Tasks / Detach.

17) Attach the database back by right-clicking Databases and selecting Attach. Browse to the MDF file and press OK.

Voila!! The database (in my case) was completely back. All the tables, every row of data.

Good luck if you need this, and remember, DO NOT EVERY DELETE THE LOG FILE. It is as important to SQL Server as the database files, even if (as in my case) there are no transaction boundaries involved in writing to the DB.



dekj
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2019 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.05 seconds. Powered By: Snitz Forums 2000