Hello I got the fg error while attaching the db guide me to solve

Question

0.00/5 (No votes)

See more:

SQL-server-2000

SQL

SQL-Server

ERROR 9003: THE LSN (371:4902:1) PASSED TO LOG SCAN IN DATABASE IN SQL 2000

Posted 24-Feb-12 21:45pm

Member 8676301

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Aniket Yadav · Answer 1 · 2012-02-24T21:53:00

It seems your db is using the full recovery model with no log maintenance routines in place. Either put the routines in place, or switch your db to the simple recovery model and truncate and shrink your log.

To Shrink Log:
backup log databasename with truncate_only
dbcc shrinkfile(logdevicename, NewSizeInMB)
ie dbcc shrinkfile(securitymaster_log, 2048)

you can obtain the log file name via select name from sysfiles for the current database, or via Enterprise Manager.

switch your db to simple recovery model if you do not need recovery outside of the last full backup, or put jobs in place to backup the database log periodically.

Rakesh Meel · Answer 2 · 2012-02-24T21:53:00

much better Solution...

According to MS documentation, 9003 error should mean that your mdf and ldf files are out of syn. And the solution is usually attaching single file using sp_attach_db or sp_attach_single_file_db Sps to let SQL Server create a new log file for you. But you've said it didn't work. If it's not possible to put db into emergency mode, I guess there's corruption somewhere in data file header (just my opinion) and you have only two options left: go back to your last good backups or try to contact MS Support with uncertain results.
mojza

just for the sake of completness if you run dbcc dbrecover ('your_db')
command, the result is probably the same as during server startup?

OriginalGriff · Answer 3 · 2012-02-24T21:56:00

Never had this problem, but it seems others have: google was pretty full when I did a search on "ERROR 9003"
It looks like it is a corrupt DB, or a disk space problem, or similar - have a look at this blog which forces a currup DB to attach, it may help. http://www.sqlskills.com/blogs/paul/post/TechEd-Demo-Creating-detaching-re-attaching-and-fixing-a-suspect-database.aspx[^]

A thought does occur though - SQL 2000 is pretty old. Does it support the version of the DB you are trying to attach?

Hello I got the fg error while attaching the db guide me to solve

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0