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

"Database 'COMMON' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details." Expand / Collapse
Author
Message
Posted Tuesday, April 21, 2009 3:58 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 3, 2009 8:02 AM
Points: 7, Visits: 17

Dear Friends,
I am getting problem with my database(mentioned below), please give me the solution ASAP. because my production server has stoped. and I am not getting what to do. and in client side all are putting too much pressure on me.

This is Error messsage.

"Database 'COMMON' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details."


Thankis in Advance
Sharanu.
Post #701263
Posted Tuesday, April 21, 2009 4:57 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, July 25, 2014 4:40 AM
Points: 166, Visits: 267
- Check the disk space where the .mdf .ndf or ldf files are located.
- If the disk space is full due .ldf
detach the database and add new disk
move the files there and attach the database
- This is a offline operation


Sat


Cheer Satish
Post #701303
Posted Tuesday, April 21, 2009 5:04 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, August 5, 2013 7:41 AM
Points: 1,146, Visits: 230
seems this is a memory problem.
please provide some more detail like size of your mdf,ldf and location of both.
configuration available.
if space is not a problem check integrity of your database.

update if you are still facing problem.

Manoj



Post #701309
Posted Tuesday, April 21, 2009 5:19 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 @ 10:05 AM
Points: 42,829, Visits: 35,961
What does the SQL error log say? There will be a much more detailed error there. Please check the error log and post any errors relating to database Common.

This is not something that can be trivially fixed without knowing the cause.



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 #701317
Posted Tuesday, April 21, 2009 5:20 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 @ 10:05 AM
Points: 42,829, Visits: 35,961
TECHBABU (4/21/2009)
- Check the disk space where the .mdf .ndf or ldf files are located.
- If the disk space is full due .ldf
detach the database and add new disk
move the files there and attach the database
- This is a offline operation


I would strongly suggest not detaching the database immediately. Depending on what the root cause is, it may happen that you detach the database and it will not reattach again.



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 #701320
Posted Tuesday, April 21, 2009 6:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 3, 2009 8:02 AM
Points: 7, Visits: 17
Dear Friends,
Thanks for your valuable response,
here i am giving some more details,

my database is located at D drive and it is having 22GB space,
and mainly effected DB is common, its .mdf is 100MB and .ldf is 450MB, and

when i open the SQL server management studio and I suppose to query as
"Use common" then I am getting this problem "Database 'COMMON' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.", and my applications user name and password are stored in this DB so i am not able to access the application. and beside in Object explore I am not getting +sign to explode that database, its something locked.

please give me the solution so that my application works properly.

Thanks
Sharanu.
Post #701394
Posted Tuesday, April 21, 2009 7:08 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, September 6, 2011 7:51 AM
Points: 105, Visits: 581
Check the available space on your C drive, especially if the tempdb is stored on there.

Oh and if your mdf file is only 100Mb, you shouldn't have a log of 450Mb. Is the "Common" db in full mode?
Post #701407
Posted Tuesday, April 21, 2009 7:31 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 @ 10:05 AM
Points: 42,829, Visits: 35,961
sharanurampur (4/21/2009)
please give me the solution so that my application works properly.


Have a look through the SQL error log. There will be more details there regarding the cause of the problem. Find those errors and post them here.



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 #701434
Posted Tuesday, April 21, 2009 7:56 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 3, 2009 8:02 AM
Points: 7, Visits: 17

when I checked into the log files i got some message like..


2009-04-21 14:28:24.96 spid27s Starting up database 'DUMMY'.
2009-04-21 14:28:26.84 spid4s Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2009-04-21 14:28:37.32 spid9s Starting up database 'tempdb'.
2009-04-21 14:28:38.59 spid4s Recovery is complete. This is an informational message only. No user action is required.
2009-04-21 14:28:38.59 spid12s The Service Broker protocol transport is disabled or not configured.
2009-04-21 14:28:38.59 spid12s The Database Mirroring protocol transport is disabled or not configured.
2009-04-21 14:28:38.76 spid12s Service Broker manager has started.
2009-04-21 14:28:45.76 spid51 Using 'xpsqlbot.dll' version '2005.90.3042' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2009-04-21 14:28:45.98 spid51 Using 'xpstar90.dll' version '2005.90.3042' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2009-04-21 14:28:46.12 spid51 Using 'xplog70.dll' version '2005.90.3042' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2009-04-21 14:41:04.84 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1712, committed (KB): 74716, memory utilization: 2%.
2009-04-21 14:46:36.79 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 331 seconds. Working set (KB): 16892, committed (KB): 39140, memory utilization: 43%.
2009-04-21 14:51:08.57 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 603 seconds. Working set (KB): 15104, committed (KB): 36524, memory utilization: 41%.
2009-04-21 14:56:35.23 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 930 seconds. Working set (KB): 17212, committed (KB): 38988, memory utilization: 44%.
2009-04-21 15:01:07.17 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1202 seconds. Working set (KB): 15148, committed (KB): 36524, memory utilization: 41%.
2009-04-21 15:06:33.90 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1529 seconds. Working set (KB): 17200, committed (KB): 38708, memory utilization: 44%.
2009-04-21 15:11:05.84 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1801 seconds. Working set (KB): 15164, committed (KB): 36516, memory utilization: 41%.
2009-04-21 15:42:02.53 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 3657 seconds. Working set (KB): 17276, committed (KB): 38876, memory utilization: 44%.
2009-04-21 16:41:54.65 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 7249 seconds. Working set (KB): 8276, committed (KB): 38900, memory utilization: 21%.
2009-04-21 18:41:38.96 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 14434 seconds. Working set (KB): 10540, committed (KB): 38756, memory utilization: 27%.
Post #701469
Posted Tuesday, April 21, 2009 10:09 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Tuesday, August 26, 2014 4:16 PM
Points: 4,389, Visits: 9,526
Can you access the D drive on the server? Can you navigate to the folder where the mdf/ndf/ldf files exist and verify that they do in fact exist?

I have seen similar messages when there has been a network outage to the SAN. The outage was only for a second, but SQL Server lost the connection and could no longer access the drive. The only solution for this scenario was to reboot the server. I am not saying this is your problem - so don't just go and reboot the server to try and solve this problem (yet).

The errors you are getting refer to problems with memory. Are you running SQL Server 2005 Standard? Is it x64 or x86? What is the max memory setting for this instance? Are you running multiple instances on this system?


Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #701637
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse