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 123»»»

log for database is not availabe Expand / Collapse
Author
Message
Posted Saturday, August 18, 2012 3:49 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, September 6, 2014 7:38 PM
Points: 202, Visits: 1,052
Hi,

I am getting the below error error message.

The log for database 'Commun' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

when i ran the dbcc check command it is giving the below error message.

Msg 1823, Level 16, State 2, Line 1
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Line 1
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
Msg 1823, Level 16, State 2, Line 1
A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Line 1
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
Msg 9001, Level 21, State 1, Line 1
The log for database 'Commun' is not available. Check the event log for related error messages. Resolve any errors and restart the database.

can anyone please help me

Thank You,
Post #1346889
Posted Saturday, August 18, 2012 3:56 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: Yesterday @ 3:43 PM
Points: 43,047, Visits: 36,206
Are there any earlier error messages?

Is the log file present where it should be? Is the drive online, etc? What's the state of the database?



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 #1346892
Posted Saturday, August 18, 2012 11:48 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, September 14, 2014 10:20 AM
Points: 92, Visits: 323
First and foremost if this is a production database look for a proper downtime window.

Also attempt a database backup before trying out anything, but that may fail again.

as a first step you can try this ;

execute the following command

use <databasename>
go

This will change the database context, then execute

sp_helpfile
go

Then note down the location of the log file from the sp_helpfile output

Then search if the file exists physically in the file system.

if the file exists than you can try detaching the database, you will still get an error during detach but the database will be detached.

to be on the safer side you can also backup the database files after they are detached.

and then you can attempt attachign the database files again.

Hope you do not have to go through the service restart to resolve the issue.

Good Luck.



Post #1346906
Posted Sunday, August 19, 2012 1:12 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 7:56 AM
Points: 7,010, Visits: 8,462
You've seen the message:
The log for database 'Commun' is not available. Check the event log for related error messages. Resolve any errors and restart the database.


it says ...check the eventlog...

I would take a look at the sqlserver errorlog file and search for messages related to that db.

Keep in mind you may need to search more than one copy of the errorlog.
(errorlog.1, errorlog.2,...)

Post your findings and we may be able to help out further.



Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #1346909
Posted Monday, August 20, 2012 9:38 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, September 6, 2014 7:38 PM
Points: 202, Visits: 1,052
Hi,

This is the error log message before that issue happened.

Transaction (Process ID 12) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Thank You,
Post #1347287
Posted Monday, August 20, 2012 9: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: Yesterday @ 3:43 PM
Points: 43,047, Visits: 36,206
That's not interesting (and shouldn't be in the SQL error log anyway)

Is the log file present where it should be? Is the drive online, etc? What's the state of the database?




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 #1347297
Posted Monday, August 20, 2012 9:49 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, September 6, 2014 7:38 PM
Points: 202, Visits: 1,052
Hi,

The log file for the database is present and the drive is online on the server.

Log files of other databases are present on the same drives and they run without any issues on the server

The status of the database is online and log_reuse_wait_desc is database_snapshot_creation

Thank You
Post #1347298
Posted Monday, August 20, 2012 9:53 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, September 6, 2014 7:38 PM
Points: 202, Visits: 1,052
Hi

The Log file of the database is present where it is supposed to be.The drive on which the log file is present is online.

Thank You,
Post #1347299
Posted Monday, August 20, 2012 9:54 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: Yesterday @ 3:43 PM
Points: 43,047, Visits: 36,206
Ok, so what's the problem? Was it just in running CheckDB?


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 #1347300
Posted Monday, August 20, 2012 9:56 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, September 6, 2014 7:38 PM
Points: 202, Visits: 1,052
Hi ,

The required information is present in the current SQL Server Error Log.

It is not present in the Archive #1 SQL Server Error Log.

Information related to this Log file is not found in the Error Logs.

Thank You,
Post #1347302
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse