Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Data Warehousing / June 2005

Tip: Looking for answers? Try searching our database.

URGENT: SQL Error 9003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Igor A. Chechet - 14 Jun 2005 07:31 GMT
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
Tibor Karaszi - 14 Jun 2005 10:22 GMT
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.

Signature

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

> Greetings!
>
[quoted text clipped - 5 lines]
> Thank you
> Igor A. Chechet
Igor A. Chechet - 14 Jun 2005 11:13 GMT
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
Tibor Karaszi - 14 Jun 2005 11:25 GMT
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.

Signature

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

> Solution:
>
[quoted text clipped - 42 lines]
>
> Igor A. Chechet
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.