Database crashed its very urgent

Hi All,
one of my database is suddenly crashed with power fluctuation and when i
started the server it is showing "not able to connect database". I have take
n
backup and i was trying to attach database in other system. It has given me
the following error.
Microsoft SQL-DMO (ODBC SQLState: HY000)
--
Error 9003: The LSN (375:9588:1) passed to log scan in database
'QVLMSCASPARES' is invalid.
--
OK
--
Please any one can help me out.
With Regards,
AHARIHari
>I have taken
> backup and i was trying to attach database in other system. It has given m
e
> the following error.
You can recover the data wont attach it. You will attach only if you
have.mdf files with you.
When did you take back up.waht kind of back up( full,differential,log) what
is your recovery model.when did you take master back up.
above information is needed to suggest you right one.
Regards
R.D
--
Regards
R.D
--Knowledge gets doubled when shared
"Srihari" wrote:

> Hi All,
> one of my database is suddenly crashed with power fluctuation and when i
> started the server it is showing "not able to connect database". I have ta
ken
> backup and i was trying to attach database in other system. It has given m
e
> the following error.
> --
> Microsoft SQL-DMO (ODBC SQLState: HY000)
> --
> Error 9003: The LSN (375:9588:1) passed to log scan in database
> 'QVLMSCASPARES' is invalid.
> --
> OK
> --
>
> Please any one can help me out.
> With Regards,
> AHARI|||once the database has crashed i have stopped sqlserver and took the copy of
the microsoft sqlserver directory under program files and kept it in other
location.
I think i am having master back up also.
How can i retrieve the data.
With Regards,
AHARI
"R.D" wrote:
> Hari
> You can recover the data wont attach it. You will attach only if you
> have.mdf files with you.
> When did you take back up.waht kind of back up( full,differential,log) wha
t
> is your recovery model.when did you take master back up.
> above information is needed to suggest you right one.
> Regards
> R.D
> --
> Regards
> R.D
> --Knowledge gets doubled when shared
>
> "Srihari" wrote:
>|||Only God should save you . Back up is different from taking copy of file
after crash.
what kind of crash did you observe.
In the folder you wil find .mdf files
go to enterprise manager, and try to attach it, If you are lucky then you
should get your data.
At least hereafter, take back up in appropriate times. do read BOL
--
Regards
R.D
--Knowledge gets doubled when shared
"Srihari" wrote:
> once the database has crashed i have stopped sqlserver and took the copy o
f
> the microsoft sqlserver directory under program files and kept it in other
> location.
> I think i am having master back up also.
> How can i retrieve the data.
> With Regards,
> AHARI
> "R.D" wrote:
>|||Hi R D
God Helped me!... I had backup of one days prior and i have re entered the
data for one day. some how system is up but in these situations is there an
y
other way to resolve instead of re entering.
With Regards,
AHARI
"R.D" wrote:
> Only God should save you . Back up is different from taking copy of file
> after crash.
> what kind of crash did you observe.
> In the folder you wil find .mdf files
> go to enterprise manager, and try to attach it, If you are lucky then you
> should get your data.
> At least hereafter, take back up in appropriate times. do read BOL
> --
> Regards
> R.D
> --Knowledge gets doubled when shared
>
> "Srihari" wrote:
>|||Yes, that's what transaction log backups are for. Do you have log
backups? If not, then consider implementing them for next time. Read
about transaction log backups in Books Online.
Also, invest in a UPS if you haven't already done so. A database server
needs to be protected from power fluctuations.
David Portas
SQL Server MVP
--|||thanks for you suggestion. I am trying to get the procedure to retrieve data
from crashed database. No one is helping me in that way. Actually this
incident had happend at one of our client place.
At least now can any one tell me how to retrieve data from crashed database.
I tried in google i got some article which is not so clear. if i get the
master also along with crashed database that is LDF and MDF how to retrieve
the data tell me the procedure in detail.
Clients are using UPS too. The database is running from past 4 years.
I felt that News group MVPs will respond quickly and take the matter
serious. Hear i am seeing they are taking it lite and making fun of me.
with Regards,
AHARI
"David Portas" wrote:

> Yes, that's what transaction log backups are for. Do you have log
> backups? If not, then consider implementing them for next time. Read
> about transaction log backups in Books Online.
> Also, invest in a UPS if you haven't already done so. A database server
> needs to be protected from power fluctuations.
> --
> David Portas
> SQL Server MVP
> --
>|||I am not making fun of you. You said in a previous post that you had
already recovered the database so I understood that you didn't need
more help on that. I was answering your specific question about how to
recover additional data by asking for more information on whether you
have a log backup. You didn't answer that question unfortunately.
As I understand it you have restored an old database backup to another
server but you still have a copy of the latest MDF and LDF files
available. It isn't possible to apply the transaction log to a database
that is online and in a recovered state. To apply the transaction log
you first have to restore from a full database backup with the
NORECOVERY option. Only then can you start to restore transaction log
backups, assuming you have them.
To restore the master database you have to first put the database into
single user mode. Only attempt to restore master on either the server
that the backup was originally taken from or on a clean install of SQL
Server.
Have you tried re-attaching the MDF and LDF files as suggested by RD?
That should be your first course of action. There is an example of how
to re-attach under the sp_attach_db topic in Books Online. If you can
attach the database successfully then you are in luck. Take a backup
immediately, run DBCC CHECKDB and then you are back in business
hopefully.
If you re-attach your database but it is marked as "suspect" then
things are bit less rosy to say the least. I recommend you contact
Microsoft support directly as there are no documented solutions and the
possible fixes are not without their own risks. I don't want to suggest
anything that may make things worse.
Relevant articles in Books Online:
"sp_attach_db"
"Restoring the master Database"
"How to restore to the point of failure"
Hope this helps.
David Portas
SQL Server MVP
--|||Hello David portas,
Thanks you for your quick response.
If you see my first posting I have clearly mentioned that, i am attaching
database in other system and mentioned the error message too.
Ok. According to your reply if i get this error i cant retrieve data back.
"David Portas" wrote:

> I am not making fun of you. You said in a previous post that you had
> already recovered the database so I understood that you didn't need
> more help on that. I was answering your specific question about how to
> recover additional data by asking for more information on whether you
> have a log backup. You didn't answer that question unfortunately.
> As I understand it you have restored an old database backup to another
> server but you still have a copy of the latest MDF and LDF files
> available. It isn't possible to apply the transaction log to a database
> that is online and in a recovered state. To apply the transaction log
> you first have to restore from a full database backup with the
> NORECOVERY option. Only then can you start to restore transaction log
> backups, assuming you have them.
> To restore the master database you have to first put the database into
> single user mode. Only attempt to restore master on either the server
> that the backup was originally taken from or on a clean install of SQL
> Server.
> Have you tried re-attaching the MDF and LDF files as suggested by RD?
> That should be your first course of action. There is an example of how
> to re-attach under the sp_attach_db topic in Books Online. If you can
> attach the database successfully then you are in luck. Take a backup
> immediately, run DBCC CHECKDB and then you are back in business
> hopefully.
> If you re-attach your database but it is marked as "suspect" then
> things are bit less rosy to say the least. I recommend you contact
> Microsoft support directly as there are no documented solutions and the
> possible fixes are not without their own risks. I don't want to suggest
> anything that may make things worse.
> Relevant articles in Books Online:
> "sp_attach_db"
> "Restoring the master Database"
> "How to restore to the point of failure"
> Hope this helps.
> --
> David Portas
> SQL Server MVP
> --
>