Tuesday, March 27, 2012

DB attach error

Hi,
When we attach one of our databases, sql server shows this error:
Error 3624:
Location: recorvery.c:2440
Expression: seenCkptEnd
ProcessId: 1388
Is there any way to recovery this database. Unfortunately we have no backup

(I'm using sql server 2000 [service pack3 installed] and we have tried
attach a lot of pc/sql server)
Sp_attach_db might not work if the database wasn't cleanly detached using
sp_detach_db. Since you have no backup, I suggest you contact Microsoft PSS
to help you salvage data. You might be able to rebuild the log using
unsupported techniques (a Google search can find these) but data integrity
will be questionable without proper database recovery.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dolphin" <d@.d.com> wrote in message
news:uGNKHitJEHA.1132@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When we attach one of our databases, sql server shows this error:
> Error 3624:
> Location: recorvery.c:2440
> Expression: seenCkptEnd
> ProcessId: 1388
> Is there any way to recovery this database. Unfortunately we have no
backup
>
> (I'm using sql server 2000 [service pack3 installed] and we have tried
> attach a lot of pc/sql server)
>
|||Hi,
This is most likely to be due to a bug in SQL Server. You could need to open
a case with Microsoft to get it resolved.
Thanks
Hari
MCDBA
"Dolphin" <d@.d.com> wrote in message
news:uGNKHitJEHA.1132@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When we attach one of our databases, sql server shows this error:
> Error 3624:
> Location: recorvery.c:2440
> Expression: seenCkptEnd
> ProcessId: 1388
> Is there any way to recovery this database. Unfortunately we have no
backup
>
> (I'm using sql server 2000 [service pack3 installed] and we have tried
> attach a lot of pc/sql server)
>
|||You can create a new database with the same name and filenames and
locations as the one you want to attach. Then stop SQL Server and replace
the new files with the files from the detached database. Start SQL Server.
If the database comes up suspect, put it in emergency mode and run DBCC
Checkdb on it. Depending on what Checkdb returns you may be able to salvage
the data by BCPing it out.
Rand
This posting is provided "as is" with no warranties and confers no rights.

No comments:

Post a Comment