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...b;EN-US;828339
But does not seem to work..
Any Ideas ?!
-- Logu
Did 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/inf...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...b;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 : 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 : 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/defaul...kb;EN-US;828339
But does not seem to work..
Any Ideas ?!
-- LoguDid you run consistency checks on the database before detaching it? You migh
t just have a corrupt database,
and detach/attach won't clean such corruptions...
http://www.karaszi.com/sqlserver/in..._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 [url]http://support.microsoft.com/default.aspx?scid=kb;EN-US;828339[/ur
l]
> 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.sql

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 5173

I had to do a restore of my msdb. Before I did, I
detached all of my databases. The restore went fine, and
I was able to re-attach all of my databases, except for
one of them. When I try to attach it, I get an error that
says "Error 5173: Cannot associate files with different
databases." The ldf files are on a differend drive than
the mdf file, but they were like that before I detached
them. Nothing has changed on this database. How do I get
this DB attached?
Thanks.Hi
At a guess you have either got the wrong file names are missing files or
they are in the wrong order!
You may also want to check the permissions on the files and directories.
If that fails you may want to try sp_attach_single_file_db and only specify
the data file (make sure you keep a copy of the original files)
John
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
> I had to do a restore of my msdb. Before I did, I
> detached all of my databases. The restore went fine, and
> I was able to re-attach all of my databases, except for
> one of them. When I try to attach it, I get an error that
> says "Error 5173: Cannot associate files with different
> databases." The ldf files are on a differend drive than
> the mdf file, but they were like that before I detached
> them. Nothing has changed on this database. How do I get
> this DB attached?
> Thanks.|||I've double and triple checked the file names and they are
correct. All permissions look correct. It's only
one .mdf and one .ldf that need to attach.
If I run "sp_attach_single_file_db", will that create a
new log file? If so, is there a way for me to point the
log file somewhere else. I have to keep the log file on a
seperate drive due to disk space (60GB log file).
Thanks again.
>--Original Message--
>Hi
>At a guess you have either got the wrong file names are
missing files or
>they are in the wrong order!
>You may also want to check the permissions on the files
and directories.
>If that fails you may want to try
sp_attach_single_file_db and only specify
>the data file (make sure you keep a copy of the original
files)
>John
>"Ken" <anonymous@.discussions.microsoft.com> wrote in
message
>news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
>> I had to do a restore of my msdb. Before I did, I
>> detached all of my databases. The restore went fine,
and
>> I was able to re-attach all of my databases, except for
>> one of them. When I try to attach it, I get an error
that
>> says "Error 5173: Cannot associate files with different
>> databases." The ldf files are on a differend drive than
>> the mdf file, but they were like that before I detached
>> them. Nothing has changed on this database. How do I
get
>> this DB attached?
>> Thanks.
>
>.
>|||Hi
I would make sure that you keep safe copies of all the files!
I would then try to re-attach them in the original locations, if that works
then detach them again and move the files.
Alternatively if you backed up the database before trying this, you could
restore the backup using the MOVE option. See Books online about the RESTORE
command.
John
<anonymous@.discussions.microsoft.com> wrote in message
news:1f1a301c457b6$0dbf1ef0$a301280a@.phx.gbl...
> I've double and triple checked the file names and they are
> correct. All permissions look correct. It's only
> one .mdf and one .ldf that need to attach.
> If I run "sp_attach_single_file_db", will that create a
> new log file? If so, is there a way for me to point the
> log file somewhere else. I have to keep the log file on a
> seperate drive due to disk space (60GB log file).
> Thanks again.
>
> >--Original Message--
> >Hi
> >
> >At a guess you have either got the wrong file names are
> missing files or
> >they are in the wrong order!
> >You may also want to check the permissions on the files
> and directories.
> >
> >If that fails you may want to try
> sp_attach_single_file_db and only specify
> >the data file (make sure you keep a copy of the original
> files)
> >
> >John
> >
> >"Ken" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:1f03501c457ae$c2d08cf0$a601280a@.phx.gbl...
> >> I had to do a restore of my msdb. Before I did, I
> >> detached all of my databases. The restore went fine,
> and
> >> I was able to re-attach all of my databases, except for
> >> one of them. When I try to attach it, I get an error
> that
> >> says "Error 5173: Cannot associate files with different
> >> databases." The ldf files are on a differend drive than
> >> the mdf file, but they were like that before I detached
> >> them. Nothing has changed on this database. How do I
> get
> >> this DB attached?
> >>
> >> Thanks.
> >
> >
> >.
> >

Error 5123

I detached a database and moved it to another folder. I am trying to
re-attach the database and am getting 'Error 5123: CREATE FILE encountered
operating system error 32(The process cannot access the file because it is
being used by another process.) while attempting to open or create the
physical file...
Is there a file configuration setting I can change to eliminate this error
message? I've done this many times without problem and had no indication of
any process using this database when I detached it. Any helpful suggestions
to be able to attach this database will be appreciated. Thank you.
DanHi,
It can be our Backup process or Virus software accessing the file. Please
verify.
Thanks
Hari
SQL Server MVP
"Dan Slaby" <dls@.newsgroup.nospam> wrote in message
news:OKxEEK$jFHA.3960@.TK2MSFTNGP12.phx.gbl...
>I detached a database and moved it to another folder. I am trying to
>re-attach the database and am getting 'Error 5123: CREATE FILE encountered
>operating system error 32(The process cannot access the file because it is
>being used by another process.) while attempting to open or create the
>physical file...
> Is there a file configuration setting I can change to eliminate this error
> message? I've done this many times without problem and had no indication
> of any process using this database when I detached it. Any helpful
> suggestions to be able to attach this database will be appreciated. Thank
> you.
> Dan
>|||Dan,
I am having the exact same problem. I loaded a utility from
www.sysinternals.com that told me that it is indeed the SQL Server process
locking the .mdf file. I, however, have been unable to correct the problem.
I'm thinking about stopping the SQL Server, renaming the .mdf files,
restarting the server, then attaching the DBs.
I believe I locked the DB file accidentally before I detached by issuing a
DBCC OpenTran(<DBName> ). Now I can't reattach because of the file lock.
Leslie
"Dan Slaby" wrote:

> I detached a database and moved it to another folder. I am trying to
> re-attach the database and am getting 'Error 5123: CREATE FILE encountered
> operating system error 32(The process cannot access the file because it i
s
> being used by another process.) while attempting to open or create the
> physical file...
> Is there a file configuration setting I can change to eliminate this error
> message? I've done this many times without problem and had no indication o
f
> any process using this database when I detached it. Any helpful suggestion
s
> to be able to attach this database will be appreciated. Thank you.
> Dan
>
>

Error 5123

I detached a database and moved it to another folder. I am trying to
re-attach the database and am getting 'Error 5123: CREATE FILE encountered
operating system error 32(The process cannot access the file because it is
being used by another process.) while attempting to open or create the
physical file...
Is there a file configuration setting I can change to eliminate this error
message? I've done this many times without problem and had no indication of
any process using this database when I detached it. Any helpful suggestions
to be able to attach this database will be appreciated. Thank you.
Dan
Hi,
It can be our Backup process or Virus software accessing the file. Please
verify.
Thanks
Hari
SQL Server MVP
"Dan Slaby" <dls@.newsgroup.nospam> wrote in message
news:OKxEEK$jFHA.3960@.TK2MSFTNGP12.phx.gbl...
>I detached a database and moved it to another folder. I am trying to
>re-attach the database and am getting 'Error 5123: CREATE FILE encountered
>operating system error 32(The process cannot access the file because it is
>being used by another process.) while attempting to open or create the
>physical file...
> Is there a file configuration setting I can change to eliminate this error
> message? I've done this many times without problem and had no indication
> of any process using this database when I detached it. Any helpful
> suggestions to be able to attach this database will be appreciated. Thank
> you.
> Dan
>
|||Dan,
I am having the exact same problem. I loaded a utility from
www.sysinternals.com that told me that it is indeed the SQL Server process
locking the .mdf file. I, however, have been unable to correct the problem.
I'm thinking about stopping the SQL Server, renaming the .mdf files,
restarting the server, then attaching the DBs.
I believe I locked the DB file accidentally before I detached by issuing a
DBCC OpenTran(<DBName>). Now I can't reattach because of the file lock.
Leslie
"Dan Slaby" wrote:

> I detached a database and moved it to another folder. I am trying to
> re-attach the database and am getting 'Error 5123: CREATE FILE encountered
> operating system error 32(The process cannot access the file because it is
> being used by another process.) while attempting to open or create the
> physical file...
> Is there a file configuration setting I can change to eliminate this error
> message? I've done this many times without problem and had no indication of
> any process using this database when I detached it. Any helpful suggestions
> to be able to attach this database will be appreciated. Thank you.
> Dan
>
>