URGENT: SQL Error 9003   

Greetings!

Recently I detached database from SQL Server 2000 Enterprise Manager. When I 
try to attach it, I got a message: Error 9003: The LSN (8855:5583:1) passed 
to log scan in database 'contacts' is invalid. I have SQL Server 2000 with 
SP3 installed. All MDF and LDF files are present. Please help me to resolve 
this problem.

Thank you
Igor A. Chechet

date: Tue, 14 Jun 2005 12:32:29 +0600   author:   Igor A. Chechet

Re: URGENT: SQL Error 9003   

If you detached it first and have all the files then an attach should work. If it doesn't, you need 
to work with MS Support (especially if it is urgent) so they can try to hunt down why it doesn't 
work in your particular case.

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"Igor A. Chechet"  wrote in message news:Or$BpoKcFHA.2424@TK2MSFTNGP09.phx.gbl...
> Greetings!
>
> Recently I detached database from SQL Server 2000 Enterprise Manager. When I try to attach it, I 
> got a message: Error 9003: The LSN (8855:5583:1) passed to log scan in database 'contacts' is 
> invalid. I have SQL Server 2000 with SP3 installed. All MDF and LDF files are present. Please help 
> me to resolve this problem.
>
> Thank you
> Igor A. Chechet
>

date: Tue, 14 Jun 2005 11:22:17 +0200   author:   Tibor Karaszi

URGENT: SQL Error 9003 - Solution   

Solution:

1. Create Database with exact name and mdf-ldf files

2. Stop MSSQLSERVER service, replace created mdf file with original one

3. Start MSSQLSERVER service, the database will be in Suspend mode

4. From Query Analyzer (QA) execute script

use master

go

sp_configure 'allow updates', 1

reconfigure with override

go

5. From QA execute script

update sysdatabases set status= 32768 where name = '<db_name>'

6. Restart MSSQLSERVER service, the database will be in Emergency mode

7. Rebuild Log. From QA execute script

DBCC REBUILD_LOG('<db_name>', '<full name to new log file>'). You got a 
message - Warning: The log for database '<db_name>' has been rebuilt.


8. From QA execute script

Use master

go

sp_configure 'allow updates', 0

Go

9. Clear from Enterprise Manager on database properties options tab Restrict 
access checkbox

It works

Igor A. Chechet

date: Tue, 14 Jun 2005 16:14:45 +0600   author:   Igor A. Chechet

Re: URGENT: SQL Error 9003 - Solution   

DBCC REBUILD_LOG will try to create a tlog for you, but it doesn't care if you have an inconsistent 
database. If you can accept inconsistent data, or verify your existent data, this *might* be OK. But 
in most cases you prefer a consistent database from an earlier point in time to an inconsistent 
database.

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/


"Igor A. Chechet"  wrote in message news:OOU%233kMcFHA.3712@TK2MSFTNGP09.phx.gbl...
> Solution:
>
> 1. Create Database with exact name and mdf-ldf files
>
> 2. Stop MSSQLSERVER service, replace created mdf file with original one
>
> 3. Start MSSQLSERVER service, the database will be in Suspend mode
>
> 4. From Query Analyzer (QA) execute script
>
> use master
>
> go
>
> sp_configure 'allow updates', 1
>
> reconfigure with override
>
> go
>
> 5. From QA execute script
>
> update sysdatabases set status= 32768 where name = '<db_name>'
>
> 6. Restart MSSQLSERVER service, the database will be in Emergency mode
>
> 7. Rebuild Log. From QA execute script
>
> DBCC REBUILD_LOG('<db_name>', '<full name to new log file>'). You got a message - Warning: The log 
> for database '<db_name>' has been rebuilt.
>
>
> 8. From QA execute script
>
> Use master
>
> go
>
> sp_configure 'allow updates', 0
>
> Go
>
> 9. Clear from Enterprise Manager on database properties options tab Restrict access checkbox
>
> It works
>
> Igor A. Chechet
>
>

date: Tue, 14 Jun 2005 12:25:35 +0200   author:   Tibor Karaszi