Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Database was in Emergency mode, single user mode - Need to bring database online Expand / Collapse
Author
Message
Posted Tuesday, November 13, 2012 1:43 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 5:19 AM
Points: 33, Visits: 63
Hello Everyone,

We are using one SQL Server 2000 version, and now one database is Emergency mode and in single user mode. The bad thing is we don't have any backups for that database but we have only the data files and log files. How can we bring that database to online??????

Please suggest on this issue.. Its need to be fixed ASAP.

Thanks In Advance....

Regards,
Post #1384282
Posted Tuesday, November 13, 2012 2:09 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:54 AM
Points: 42,466, Visits: 35,530
Why is the DB in emergency mode? How did it get there?
What errors are there for that DB in the error log?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1384295
Posted Tuesday, November 13, 2012 6:26 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 5:19 AM
Points: 33, Visits: 63
Hi,
This was the errorlog :

2012-11-13 16:52:48.20 spid10 Starting up database 'CMU'.
2012-11-13 16:52:48.24 spid11 Starting up database 'ESIDATADUMP'.
2012-11-13 16:52:48.24 spid11 udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device E:\SQLDATA\sqldatafiles\ESIDATADUMP_Data.MDF.
2012-11-13 16:52:48.23 spid9 udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device E:\DNCDatafiles\DNC.mdf.
2012-11-13 16:52:48.26 spid9 FCB::Open failed: Could not open device E:\DNCDatafiles\DNC.mdf for virtual device number (VDN) 1.
2012-11-13 16:52:48.26 spid12 Starting up database 'DBA'.
2012-11-13 16:52:48.26 spid12 udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device E:\SQLDATA\sqldatafiles\DBA_Data.mdf.
2012-11-13 16:52:48.26 spid12 FCB::Open failed: Could not open device E:\SQLDATA\sqldatafiles\DBA_Data.mdf for virtual device number (VDN) 1.
2012-11-13 16:52:48.26 spid13 Starting up database 'DNC_Table_BKUP'.
2012-11-13 16:52:48.26 spid14 Starting up database 'CanadaBT'.
2012-11-13 16:52:48.26 spid14 udopen: Operating system error 3(The system cannot find the path specified.) during the creation/opening of physical device E:\SQLDATA\sqldatafiles\CanadaBT_Data.MDF.
2012-11-13 16:52:48.26 spid14 FCB::Open failed: Could not open device E:\SQLDATA\sqldatafiles\CanadaBT_Data.MDF for virtual device number (VDN) 1.
2012-11-13 16:52:48.26 spid11 FCB::Open failed: Could not open device E:\SQLDATA\sqldatafiles\ESIDATADUMP_Data.MDF for virtual device number (VDN) 1.
2012-11-13 16:52:48.26 spid15 Starting up database 'distribution'.

Please check...

Regards,
Varalakshmi
Post #1384360
Posted Wednesday, November 14, 2012 12:02 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:54 AM
Points: 42,466, Visits: 35,530
The folder and/or files mentioned in those errors don't exist. Rectify that problem and restart SQL.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1384413
Posted Wednesday, November 14, 2012 5:22 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 5:19 AM
Points: 33, Visits: 63
Hi,

After restart of server also the database in emergency mode but those files we can able to see. We copied all the .mdf and .ldf files to some new location and created the required database in that new sql server by attaching these mdf and ldf files. Now we have atleast one source for current use.
It seems to be issue has been fixed.
Planning to do the same thing on the emergency mode database also.

Thanks
&
Regards,
Post #1384554
Posted Wednesday, November 14, 2012 5:47 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:54 AM
Points: 42,466, Visits: 35,530
Good, now set up a backup strategy.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1384572
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse