June 24, 2009 at 8:13 am
I will see this error and database becomes inaccessible to many people.
Process ID %d attempted to unlock a resource it does not own: %.*ls. Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator.
MSDN talks about database corruption. Any ideas what causes this, we have not changed anything. But it suddenly started happening in Dev and now in UAT. I am worried about production.
Please suggest on how to debug this.
June 24, 2009 at 8:20 am
June 24, 2009 at 8:59 am
This is stored in memory dump
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is PTLTD - 6040000
PhoenixBIOS 4.0 Release 6.0
Current time is 23:35:05 08/07/08.
2 Intel x86 level 15, 3394 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 95%
Total Physical = 3839 MB
Available Physical = 161 MB
Total Page File = 7780 MB
Available Page File = 4028 MB
Total Virtual = 2047 MB
Available Virtual = 262 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to H:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 08/07/08 23:35:45 spid 0
*
* Non-yielding IOCP Listener
*
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
June 24, 2009 at 5:48 pm
Have you tried running checkdb in that database?
Mj
June 24, 2009 at 7:20 pm
On 2 drives, file fragmentation is 99% and 95%. I just took over these servers few weeks back. I am trying to defragment it and it seems to be taking LONG time to complete it.
I am going to try this now.
I ran checkdb for few databases and they are fine. I am just suspecting CPU over head.
Thanks,
Sudhie.
June 24, 2009 at 8:40 pm
Sudiendra (6/24/2009)
MemoryMemoryLoad = 95%
Total Physical = 3839 MB
Available Physical = 161 MB
Total Page File = 7780 MB
Available Page File = 4028 MB
Total Virtual = 2047 MB
Available Virtual = 262 MB
I suspect this to be memory pressure as per the above statement.
only 161 MB free from 4GB of RAM and the load it shows at95%.
Let us more about your Hardware.
SQL Server edition/version Or version/edition.
Physical ram is 4GB/Disk configuration.
Database Size: and anything else you can think of.
Because we had a similar situation with our SQL 2005 standard SP2 with 4GB RAM on Dual Processor hyperthreaded+windows 2003 SP2 std edition.
We had SQL server engine/SSRS/SSAS/SSIS all services on the same Server. So we saw i diagnosed it down to Memeory pressure, becasue the SSAS was the culprit which used almost 1+GB during Cube Processing and at normal time it consumed 500MB and the SQL server was between 1.6 to 1.9 GB..and after other components used other parts of the memory... so nothing left for the OS..... Relating to which we had disconnection from web clients and other users... and were not able to connect to Server... we added 1GB of RAM. doing this the SSAS was comfortable in using more RAM and everything worked like a charm...
check to see if there is a familiar situation...at your end.
Maninder
www.dbanation.com
June 24, 2009 at 10:30 pm
It is OS memory and i have used 15 GB to SQL and 4 GB to OS. I will see if i leave more memory to OS to see if it works fine.
June 24, 2009 at 10:31 pm
3 Databases are corrupted. I am unable to fix it using DBCC CHECKDB repair allowing data loss..Any other ideas other than refreshing?
June 24, 2009 at 10:44 pm
Applied DBCC UPDATEUSAGE for 3 databases which resolved the issue. These databases are recently migrated from another box (2000 to 2005).
Any more maintenance to be performed now?
June 25, 2009 at 7:03 am
Sudiendra (6/24/2009)
It is OS memory and i have used 15 GB to SQL and 4 GB to OS. I will see if i leave more memory to OS to see if it works fine.
According to this you have 20GB of RAM, so are you running 64bit SQL or 32 bit windows ENT edition. and how about SQL.. is it Enterprise of Standard.
Did you migrate these databases?
did you run a full eror check like DBCC CHECKDB () with ALL_ERRORMSGS
Maninder
www.dbanation.com
June 25, 2009 at 2:09 pm
Did you run DBCC CHECKDB with DATA_PURITY command
after the upgrade?
http://www.mssqltips.com/tip.asp?tip=1119
MJ
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply