Error 9003 : fail to attach a database

Hi,
I sucessful attached a database, but deleted it without detach. When I tried
to attach again got this error 9003: The LSN(12:32:1) passed to log scan in
database "Contacts" is invalid.
I tried to detach it, but I can't find the database in system, so it fails t
oo.
Please help, thanks in advance!
IreneIrene,
Do you have the .mdf and .ldf files for Contacts?
Did you use the Enterprise Manager or issue the sp_attach_db and sp_detach_d
b from the Query Analyzer?
...but deleted it without detach...
What does this mean? How was this accomplished? Explain...
Does Contacts show up when you run this...
SELECT * FROM master..sysdatabases
Norman|||Hi, Norman
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf.
After attached it, I found the new database "Contact" was readonly. I
made a mistake to del the database "Contact" directly in the Enterprise
Manager explorer.
When I tried to attach the file again in the Enterprise Manager
explorer, it shows the error 9003. Then I tried sp_detach_db "Contact",
it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record
in.
I guest it still has some reference files exist in database server, but
I don't know how to restore it.
Thanks again.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Hi, Norman
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf.
After attached it, I found the new database "Contact" was readonly. I made a
mistake to del the database "Contact" directly in the Enterprise Manager ex
plorer.
When I tried to attach the file again in the Enterprise Manager explorer, it
shows the error 9003. Then I tried sp_detach_db "Contact", it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record in.
I guest it still has some reference files exist in database server, but I do
n't know how to restore it.

Error 9003 : fail to attach a database

Hi
I sucessful attached a database, but deleted it without detach. When I tried to attach again got this error 9003: The LSN(12:32:1) passed to log scan in database "Contacts" is invalid
I tried to detach it, but I can't find the database in system, so it fails too
Please help, thanks in advance
IreneIrene
Do you have the .mdf and .ldf files for Contacts
Did you use the Enterprise Manager or issue the sp_attach_db and sp_detach_db from the Query Analyzer
...but deleted it without detach..
What does this mean? How was this accomplished? Explain..
Does Contacts show up when you run this..
SELECT * FROM master..sysdatabase
Norman|||Hi, Norma
I used the Enterprise Manager to attach the Contact.mdf and Contact.ldf
After attached it, I found the new database "Contact" was readonly. I made a mistake to del the database "Contact" directly in the Enterprise Manager explorer
When I tried to attach the file again in the Enterprise Manager explorer, it shows the error 9003. Then I tried sp_detach_db "Contact", it fails.
When I run "SELECT * FROM sysdatabases", no "Contact" database record in
I guest it still has some reference files exist in database server, but I don't know how to restore it.

Error 9003

Hi
I have been using SQL server with the web matrix project whilst I learn
ASP.net. (I am new to both). At some point this week the SQL server stopped
working (It may be linked to my computer crashing whilst another program was
running). It now will not run from the web matrix or the SQL service
manager. I have found the error logs and the last four lines read :-
2005-09-10 08:54:02.92 spid3 Starting up database 'master'.
2005-09-10 08:54:03.35 spid3 Error: 9003, Servrity: 20, State: 1.
2005-09-10 08:54:03.35 spid3 Cannot recover the master database.
Exiting.
I have found a description of error 9003
"The LSN %S_LSN passed to log scan in database '%.*Is' is invalid."
but this means nothing to me.
My guess is I have an inconsistancy because of the crash but to be honest I
am out of my depth.
Has anyone got some simple advice or do I just start again.
Thanks in advance
Mike
Hi,
Have a look into the below URL to correct the master database corruption.
This will work out provide you have the master database backup.
http://geekswithblogs.net/travis/arc.../27/48400.aspx
Thanks
Hari
SQL Server MVP
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:93CFAEEF-9171-4CD7-B712-58870BE12715@.microsoft.com...
> Hi
> I have been using SQL server with the web matrix project whilst I learn
> ASP.net. (I am new to both). At some point this week the SQL server
> stopped
> working (It may be linked to my computer crashing whilst another program
> was
> running). It now will not run from the web matrix or the SQL service
> manager. I have found the error logs and the last four lines read :-
> 2005-09-10 08:54:02.92 spid3 Starting up database 'master'.
> 2005-09-10 08:54:03.35 spid3 Error: 9003, Servrity: 20, State: 1.
> 2005-09-10 08:54:03.35 spid3 Cannot recover the master database.
> Exiting.
> I have found a description of error 9003
> "The LSN %S_LSN passed to log scan in database '%.*Is' is invalid."
> but this means nothing to me.
> My guess is I have an inconsistancy because of the crash but to be honest
> I
> am out of my depth.
> Has anyone got some simple advice or do I just start again.
> Thanks in advance
> Mike
|||Hi Prasad
Thanks for the advice. In fact I have been looking around the internet over
the last few hours and tried a few things including SP4. I also realised
that I had nothing backed up in the SQL Server (as I did not know how to).
Anyway, I installed a new Instance of the server on my computer and have
spent hours building the tables and stored procedures again. I have almost
finished! It's a little messy as I still have the old instance of the SQL
Server on the computer and cannot open it or remove it.
Anyway, I will back up my database this time!!
I will also have a look at your link just for interest sake - and I have
certainly learnt some important info about SQL Server today.
Thanks again
Mike
"Hari Prasad" wrote:

> Hi,
> Have a look into the below URL to correct the master database corruption.
> This will work out provide you have the master database backup.
> http://geekswithblogs.net/travis/arc.../27/48400.aspx
> Thanks
> Hari
> SQL Server MVP
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:93CFAEEF-9171-4CD7-B712-58870BE12715@.microsoft.com...
>
>
sql

Error 9003

Hi
I have been using SQL server with the web matrix project whilst I learn
ASP.net. (I am new to both). At some point this week the SQL server stopped
working (It may be linked to my computer crashing whilst another program was
running). It now will not run from the web matrix or the SQL service
manager. I have found the error logs and the last four lines read :-
2005-09-10 08:54:02.92 spid3 Starting up database 'master'.
2005-09-10 08:54:03.35 spid3 Error: 9003, Servrity: 20, State: 1.
2005-09-10 08:54:03.35 spid3 Cannot recover the master database.
Exiting.
I have found a description of error 9003
"The LSN %S_LSN passed to log scan in database '%.*Is' is invalid."
but this means nothing to me.
My guess is I have an inconsistancy because of the crash but to be honest I
am out of my depth.
Has anyone got some simple advice or do I just start again.
Thanks in advance
MikeHi,
Have a look into the below URL to correct the master database corruption.
This will work out provide you have the master database backup.
http://geekswithblogs.net/travis/ar...7/27/48400.aspx
Thanks
Hari
SQL Server MVP
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:93CFAEEF-9171-4CD7-B712-58870BE12715@.microsoft.com...
> Hi
> I have been using SQL server with the web matrix project whilst I learn
> ASP.net. (I am new to both). At some point this week the SQL server
> stopped
> working (It may be linked to my computer crashing whilst another program
> was
> running). It now will not run from the web matrix or the SQL service
> manager. I have found the error logs and the last four lines read :-
> 2005-09-10 08:54:02.92 spid3 Starting up database 'master'.
> 2005-09-10 08:54:03.35 spid3 Error: 9003, Servrity: 20, State: 1.
> 2005-09-10 08:54:03.35 spid3 Cannot recover the master database.
> Exiting.
> I have found a description of error 9003
> "The LSN %S_LSN passed to log scan in database '%.*Is' is invalid."
> but this means nothing to me.
> My guess is I have an inconsistancy because of the crash but to be honest
> I
> am out of my depth.
> Has anyone got some simple advice or do I just start again.
> Thanks in advance
> Mike|||Hi Prasad
Thanks for the advice. In fact I have been looking around the internet over
the last few hours and tried a few things including SP4. I also realised
that I had nothing backed up in the SQL Server (as I did not know how to).
Anyway, I installed a new Instance of the server on my computer and have
spent hours building the tables and stored procedures again. I have almost
finished! It's a little messy as I still have the old instance of the SQL
Server on the computer and cannot open it or remove it.
Anyway, I will back up my database this time!!
I will also have a look at your link just for interest sake - and I have
certainly learnt some important info about SQL Server today.
Thanks again
Mike
"Hari Prasad" wrote:

> Hi,
> Have a look into the below URL to correct the master database corruption.
> This will work out provide you have the master database backup.
> http://geekswithblogs.net/travis/ar...7/27/48400.aspx
> Thanks
> Hari
> SQL Server MVP
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:93CFAEEF-9171-4CD7-B712-58870BE12715@.microsoft.com...
>
>

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
DanDan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is ver
y
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:

> We have a reporting database that end users run ad-hoc queries against (SQ
L
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log fo
r
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she i
s
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of dis
k
> space, and have gotten this message with tempdb log set to unrestricted an
d
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because
it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this
?
> Thanks,
> Dan

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
Dan
Dan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is very
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:

> We have a reporting database that end users run ad-hoc queries against (SQL
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log for
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she is
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of disk
> space, and have gotten this message with tempdb log set to unrestricted and
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this?
> Thanks,
> Dan

Error 9002, tempdb log full

We have a reporting database that end users run ad-hoc queries against (SQL
Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
following error message:
Error: 9002, Severity: 17, State: 6
The log file for database 'tempdb' is full. Back up the transaction log for
the database to free up some log space.
When I track down the user associated with the Event Log message, he/she is
running a huge query that needs better selection criteria, but I don't
believe that the tempdb log is truely out of space. We have plenty of disk
space, and have gotten this message with tempdb log set to unrestricted and
with a limit of 15 GB.
Question: Is this a sql server bug or related to an i/o problem, because it
really isn't a true tempdb log full condition. Does this impact all users
using tempdb (I would think so) and any suggestions on how to prevent this?
Thanks,
DanDan,
This is not a bug. It is truly a tempdb log full alert. It does not matter
how much space you have because you are limiting the log to 15 GB. It is very
much possible for the log to be full on a reporting database. Remember, all
sorting, agregations and temp tables are created in the tempdb.
I don't think there is a right answer for the size, you will have to
increase it and watch it and increase it again as needed.
hth
DeeJay
"Dan H" wrote:
> We have a reporting database that end users run ad-hoc queries against (SQL
> Server 2000 SP 4 running on Windows 2000). Periodically, we'll get the
> following error message:
> Error: 9002, Severity: 17, State: 6
> The log file for database 'tempdb' is full. Back up the transaction log for
> the database to free up some log space.
> When I track down the user associated with the Event Log message, he/she is
> running a huge query that needs better selection criteria, but I don't
> believe that the tempdb log is truely out of space. We have plenty of disk
> space, and have gotten this message with tempdb log set to unrestricted and
> with a limit of 15 GB.
> Question: Is this a sql server bug or related to an i/o problem, because it
> really isn't a true tempdb log full condition. Does this impact all users
> using tempdb (I would think so) and any suggestions on how to prevent this?
> Thanks,
> Dan