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 823 : SQL Server

Hi
I'm getting an Error 823, when I tried to attach a detached SQL DB
[JPG file attached]
Tried this KB http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339
But does not seem to work..
Any Ideas ?!
-- LoguDid you run consistency checks on the database before detaching it? You might just have a corrupt database,
and detach/attach won't clean such corruptions...
http://www.karaszi.com/sqlserver/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Logu" <klogu@.scapevelocity.com> wrote in message news:uoN$ZBOMEHA.620@.TK2MSFTNGP10.phx.gbl...
> Hi
>
> I'm getting an Error 823, when I tried to attach a detached SQL DB
> [JPG file attached]
> Tried this KB http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339
> But does not seem to work..
>
> Any Ideas ?!
> -- Logu
>|||Hi Logu,
I wanted to post a quick note to see if you would like additional
assistance or information regarding this particular issue. We appreciate
your patience and look forward to hearing from you!
Sincerely yours,
Michael Cheng
Microsoft Online Support
***********************************************************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.

Error 823 (customer is down)

Ok, I know an 823 is a hardware error.
I detached the database, then I copied all *.*DF to another directory. I
then tried to attached the database from that new location and received:
Error 823: I/O error (bad page ID) deteced during read at offset
0x0000003e17x000 in file 'filename'
WHen I try to connect using the original directory, I receive the same
message.
I did get a message while I was detaching that it couldn't close the
database cleanly, and that the detach failed, but then the database
wasn't visible in EM, so I assumed it was really detached.
What are my options besides restoring the database?
Darin
*** Sent via Developersdex http://www.codecomments.com ***Hi Darin
This sounds like the files themselves may be corrupted, if you have a recent
backup you may have to go back to that.
Check out:
http://msdn.microsoft.com/library/d...serr_1_2a0j.asp
http://msdn2.microsoft.com/en-us/library/aa337267.aspx
If you are sure the hardware is ok and don't have a backup and the filename
is the log file, you may want to rename the log file and try attaching the
data file only see sp_attach_single_file_db kin books online, otherwise a
call to PSS may be the best and quickest option.
John
"Darin" wrote:

> Ok, I know an 823 is a hardware error.
> I detached the database, then I copied all *.*DF to another directory. I
> then tried to attached the database from that new location and received:
> Error 823: I/O error (bad page ID) deteced during read at offset
> 0x0000003e17x000 in file 'filename'
> WHen I try to connect using the original directory, I receive the same
> message.
> I did get a message while I was detaching that it couldn't close the
> database cleanly, and that the detach failed, but then the database
> wasn't visible in EM, so I assumed it was really detached.
> What are my options besides restoring the database?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>|||The local system doesn't have a backup. This is a subscriber in a
replication environment, so I can copy the data from the main server
(very time comsuming).
Also, the links you sent are to run dbcc checkdb, but I can't attache
the DB therefore I can't run checkdb.
Also, the file that is returning the error isn't the log, it is the main
MDF (1 mdf, 7 ndf, 1 ldf).
Darin
*** Sent via Developersdex http://www.codecomments.com ***|||The local system doesn't have a backup. This is a subscriber in a
replication environment, so I can copy the data from the main server
(very time comsuming).
Also, the links you sent are to run dbcc checkdb, but I can't attache
the DB therefore I can't run checkdb.
Darin
*** Sent via Developersdex http://www.codecomments.com ***|||If the error followed the files then the database itself is corrupt and
nothing is going to fix it other than starting over. Reinitializing
replication can take a long time but it beats waiting for a miracle healing
which isn't likely to happen.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Darin" <darin_nospam@.nospamever> wrote in message
news:OtztSrPBHHA.1196@.TK2MSFTNGP03.phx.gbl...
> The local system doesn't have a backup. This is a subscriber in a
> replication environment, so I can copy the data from the main server
> (very time comsuming).
> Also, the links you sent are to run dbcc checkdb, but I can't attache
> the DB therefore I can't run checkdb.
> Also, the file that is returning the error isn't the log, it is the main
> MDF (1 mdf, 7 ndf, 1 ldf).
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***|||Hi
Before in-initialising replication make sure you know what caused the
problem and that it is cured!
John
"Darin" wrote:

> The local system doesn't have a backup. This is a subscriber in a
> replication environment, so I can copy the data from the main server
> (very time comsuming).
> Also, the links you sent are to run dbcc checkdb, but I can't attache
> the DB therefore I can't run checkdb.
> Also, the file that is returning the error isn't the log, it is the main
> MDF (1 mdf, 7 ndf, 1 ldf).
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>|||Hi Darin
Before snap-shotting your subscriber, you might look into whether the 823
error has corrupted a page owned by a non-clustered index or a table
(clustered index or heap). If the page is owned by an non-clustered index,
you simply rebuild the index. If the page is owned up a table, you might
remove that table from the publication & re-snapshot the individual table in
its own publication..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Darin" <darin_nospam@.nospamever> wrote in message
news:umE28vOBHHA.2316@.TK2MSFTNGP04.phx.gbl...
> Ok, I know an 823 is a hardware error.
> I detached the database, then I copied all *.*DF to another directory. I
> then tried to attached the database from that new location and received:
> Error 823: I/O error (bad page ID) deteced during read at offset
> 0x0000003e17x000 in file 'filename'
> WHen I try to connect using the original directory, I receive the same
> message.
> I did get a message while I was detaching that it couldn't close the
> database cleanly, and that the detach failed, but then the database
> wasn't visible in EM, so I assumed it was really detached.
> What are my options besides restoring the database?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***

Error 823 (customer is down)

Ok, I know an 823 is a hardware error.
I detached the database, then I copied all *.*DF to another directory. I
then tried to attached the database from that new location and received:
Error 823: I/O error (bad page ID) deteced during read at offset
0x0000003e17x000 in file 'filename'
WHen I try to connect using the original directory, I receive the same
message.
I did get a message while I was detaching that it couldn't close the
database cleanly, and that the detach failed, but then the database
wasn't visible in EM, so I assumed it was really detached.
What are my options besides restoring the database?
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Hi Darin
This sounds like the files themselves may be corrupted, if you have a recent
backup you may have to go back to that.
Check out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_reslsyserr_1_2a0j.asp
http://msdn2.microsoft.com/en-us/library/aa337267.aspx
If you are sure the hardware is ok and don't have a backup and the filename
is the log file, you may want to rename the log file and try attaching the
data file only see sp_attach_single_file_db kin books online, otherwise a
call to PSS may be the best and quickest option.
John
"Darin" wrote:

> Ok, I know an 823 is a hardware error.
> I detached the database, then I copied all *.*DF to another directory. I
> then tried to attached the database from that new location and received:
> Error 823: I/O error (bad page ID) deteced during read at offset
> 0x0000003e17x000 in file 'filename'
> WHen I try to connect using the original directory, I receive the same
> message.
> I did get a message while I was detaching that it couldn't close the
> database cleanly, and that the detach failed, but then the database
> wasn't visible in EM, so I assumed it was really detached.
> What are my options besides restoring the database?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
|||The local system doesn't have a backup. This is a subscriber in a
replication environment, so I can copy the data from the main server
(very time comsuming).
Also, the links you sent are to run dbcc checkdb, but I can't attache
the DB therefore I can't run checkdb.
Also, the file that is returning the error isn't the log, it is the main
MDF (1 mdf, 7 ndf, 1 ldf).
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||The local system doesn't have a backup. This is a subscriber in a
replication environment, so I can copy the data from the main server
(very time comsuming).
Also, the links you sent are to run dbcc checkdb, but I can't attache
the DB therefore I can't run checkdb.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||If the error followed the files then the database itself is corrupt and
nothing is going to fix it other than starting over. Reinitializing
replication can take a long time but it beats waiting for a miracle healing
which isn't likely to happen.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Darin" <darin_nospam@.nospamever> wrote in message
news:OtztSrPBHHA.1196@.TK2MSFTNGP03.phx.gbl...
> The local system doesn't have a backup. This is a subscriber in a
> replication environment, so I can copy the data from the main server
> (very time comsuming).
> Also, the links you sent are to run dbcc checkdb, but I can't attache
> the DB therefore I can't run checkdb.
> Also, the file that is returning the error isn't the log, it is the main
> MDF (1 mdf, 7 ndf, 1 ldf).
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi
Before in-initialising replication make sure you know what caused the
problem and that it is cured!
John
"Darin" wrote:

> The local system doesn't have a backup. This is a subscriber in a
> replication environment, so I can copy the data from the main server
> (very time comsuming).
> Also, the links you sent are to run dbcc checkdb, but I can't attache
> the DB therefore I can't run checkdb.
> Also, the file that is returning the error isn't the log, it is the main
> MDF (1 mdf, 7 ndf, 1 ldf).
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>

Error 823 (customer is down)

Ok, I know an 823 is a hardware error.
I detached the database, then I copied all *.*DF to another directory. I
then tried to attached the database from that new location and received:
Error 823: I/O error (bad page ID) deteced during read at offset
0x0000003e17x000 in file 'filename'
WHen I try to connect using the original directory, I receive the same
message.
I did get a message while I was detaching that it couldn't close the
database cleanly, and that the detach failed, but then the database
wasn't visible in EM, so I assumed it was really detached.
What are my options besides restoring the database?
Darin
*** Sent via Developersdex http://www.developersdex.com ***Hi Darin
This sounds like the files themselves may be corrupted, if you have a recent
backup you may have to go back to that.
Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_reslsyserr_1_2a0j.asp
http://msdn2.microsoft.com/en-us/library/aa337267.aspx
If you are sure the hardware is ok and don't have a backup and the filename
is the log file, you may want to rename the log file and try attaching the
data file only see sp_attach_single_file_db kin books online, otherwise a
call to PSS may be the best and quickest option.
John
"Darin" wrote:
> Ok, I know an 823 is a hardware error.
> I detached the database, then I copied all *.*DF to another directory. I
> then tried to attached the database from that new location and received:
> Error 823: I/O error (bad page ID) deteced during read at offset
> 0x0000003e17x000 in file 'filename'
> WHen I try to connect using the original directory, I receive the same
> message.
> I did get a message while I was detaching that it couldn't close the
> database cleanly, and that the detach failed, but then the database
> wasn't visible in EM, so I assumed it was really detached.
> What are my options besides restoring the database?
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***
>|||Hi
Before in-initialising replication make sure you know what caused the
problem and that it is cured!
John
"Darin" wrote:
> The local system doesn't have a backup. This is a subscriber in a
> replication environment, so I can copy the data from the main server
> (very time comsuming).
> Also, the links you sent are to run dbcc checkdb, but I can't attache
> the DB therefore I can't run checkdb.
> Also, the file that is returning the error isn't the log, it is the main
> MDF (1 mdf, 7 ndf, 1 ldf).
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***
>|||Hi Darin
Before snap-shotting your subscriber, you might look into whether the 823
error has corrupted a page owned by a non-clustered index or a table
(clustered index or heap). If the page is owned by an non-clustered index,
you simply rebuild the index. If the page is owned up a table, you might
remove that table from the publication & re-snapshot the individual table in
its own publication..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Darin" <darin_nospam@.nospamever> wrote in message
news:umE28vOBHHA.2316@.TK2MSFTNGP04.phx.gbl...
> Ok, I know an 823 is a hardware error.
> I detached the database, then I copied all *.*DF to another directory. I
> then tried to attached the database from that new location and received:
> Error 823: I/O error (bad page ID) deteced during read at offset
> 0x0000003e17x000 in file 'filename'
> WHen I try to connect using the original directory, I receive the same
> message.
> I did get a message while I was detaching that it couldn't close the
> database cleanly, and that the detach failed, but then the database
> wasn't visible in EM, so I assumed it was really detached.
> What are my options besides restoring the database?
> Darin
> *** Sent via Developersdex http://www.developersdex.com ***

Error 8115 in Enterprise Manager when I want to shrink my attached Database

Hallo everbody,
I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
numeric ..." when I want to shrink my database after attaching to sql server
2000.
No error occurs when I shrink my database with the query analyzer.
No error is reported when I try DBCC DBCHECK on the database.
So, whats the problem for the Enterprise Manager?
It's not only on my PC ... it occurs on other PCs too after attaching the
database to sql server 2000.
Any ideas?
Thanks und Greetings
MartinMy guess is a programming mistake in either EM or DMO. Does this happen when you open the shrink
dialog or when you press "OK"?
Is it a large database? Does it have many database files?
My guess is that EM or DMO executes some SQL statement that causes an overflow in the SQL code,
quite simply. Perhaps there's a KB article on this. Did you check? I ran profiler when opening the
dialog, and I can possibly see why an overflow can occur if you have strange figures in sysfiles, or
if you have many or large database...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Martin Schmeller" <martin.schmeller@.mcs-ag.com> wrote in message
news:exSk8soDFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hallo everbody,
> I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
> numeric ..." when I want to shrink my database after attaching to sql server
> 2000.
> No error occurs when I shrink my database with the query analyzer.
> No error is reported when I try DBCC DBCHECK on the database.
> So, whats the problem for the Enterprise Manager?
> It's not only on my PC ... it occurs on other PCs too after attaching the
> database to sql server 2000.
> Any ideas?
> Thanks und Greetings
> Martin
>

Error 8115 in Enterprise Manager when I want to shrink my attached Database

Hallo everbody,
I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
numeric ..." when I want to shrink my database after attaching to sql server
2000.
No error occurs when I shrink my database with the query analyzer.
No error is reported when I try DBCC DBCHECK on the database.
So, whats the problem for the Enterprise Manager?
It's not only on my PC ... it occurs on other PCs too after attaching the
database to sql server 2000.
Any ideas?
Thanks und Greetings
Martin
My guess is a programming mistake in either EM or DMO. Does this happen when you open the shrink
dialog or when you press "OK"?
Is it a large database? Does it have many database files?
My guess is that EM or DMO executes some SQL statement that causes an overflow in the SQL code,
quite simply. Perhaps there's a KB article on this. Did you check? I ran profiler when opening the
dialog, and I can possibly see why an overflow can occur if you have strange figures in sysfiles, or
if you have many or large database...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Martin Schmeller" <martin.schmeller@.mcs-ag.com> wrote in message
news:exSk8soDFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hallo everbody,
> I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
> numeric ..." when I want to shrink my database after attaching to sql server
> 2000.
> No error occurs when I shrink my database with the query analyzer.
> No error is reported when I try DBCC DBCHECK on the database.
> So, whats the problem for the Enterprise Manager?
> It's not only on my PC ... it occurs on other PCs too after attaching the
> database to sql server 2000.
> Any ideas?
> Thanks und Greetings
> Martin
>

Error 8115 in Enterprise Manager when I want to shrink my attached Database

Hallo everbody,
I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
numeric ..." when I want to shrink my database after attaching to sql server
2000.
No error occurs when I shrink my database with the query analyzer.
No error is reported when I try DBCC DBCHECK on the database.
So, whats the problem for the Enterprise Manager?
It's not only on my PC ... it occurs on other PCs too after attaching the
database to sql server 2000.
Any ideas?
Thanks und Greetings
MartinMy guess is a programming mistake in either EM or DMO. Does this happen when
you open the shrink
dialog or when you press "OK"?
Is it a large database? Does it have many database files?
My guess is that EM or DMO executes some SQL statement that causes an overfl
ow in the SQL code,
quite simply. Perhaps there's a KB article on this. Did you check? I ran pro
filer when opening the
dialog, and I can possibly see why an overflow can occur if you have strange
figures in sysfiles, or
if you have many or large database...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Martin Schmeller" <martin.schmeller@.mcs-ag.com> wrote in message
news:exSk8soDFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hallo everbody,
> I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
> numeric ..." when I want to shrink my database after attaching to sql serv
er
> 2000.
> No error occurs when I shrink my database with the query analyzer.
> No error is reported when I try DBCC DBCHECK on the database.
> So, whats the problem for the Enterprise Manager?
> It's not only on my PC ... it occurs on other PCs too after attaching the
> database to sql server 2000.
> Any ideas?
> Thanks und Greetings
> Martin
>

Error 7201: Permissions problem?

Hi there

I am new to this forum and I was wondering if someone could help out.

I am marked as "dbo" on a SQL Server database. Attached to this DB is a
publication. When I right click > properties SQL Server gives me Error 7201

Any ideas as to how I can get over this? Is it permissions related?

ThanksRandall McMurphy via SQLMonster.com (forum@.nospam.SQLMonster.com) writes:
> I am new to this forum and I was wondering if someone could help out.
> I am marked as "dbo" on a SQL Server database. Attached to this DB is a
> publication. When I right click > properties SQL Server gives me Error
> 7201

That is: "Could not execute procedure on remote server '%.*ls' because SQL
Server is not configured for remote access. Ask your system administrator to
reconfigure SQL Server to allow remote access."

> Any ideas as to how I can get over this? Is it permissions related?

No, it's a configuraiton issue. I have not seen the message before, and
the message is a little strange. Which server needs to be configured? The
local server or the remote server? But since I cannot think of any
configuration on the local side, it's probably the definition of the remote
server that is wacko.

Do sp_helpserver on the linked server, and make sure that all of these
are enabled: rpc, rpc out and data access. If they are not, use
sp_serveroption to set these on.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp