LOCK on process

Last Post 08 Apr 2007 02:56 AM by TRACEYSQL. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
TRACEYSQL
New Member
New Member

--
07 Apr 2007 02:36 PM
This same problem sometimes work sometimes if fails and i have to fix the data

this time i tracked it down
252 0 0 0x0000 0 PAGEIOLATCH_SH 7:1:17617 7 0 720 55 165 2007-04-05 09:33:40.477 2007-04-05 09:33:41.967 0 1 sleeping 0x5C4754C07477D048A81BBBAB3BE5337700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ASRCFHCPSVR2 3348 AWAITING COMMAND 00123F0EFF70 TCP/IP DELTEK 0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0x0000000000000000000000000000000000000000 0 0

215 5904 252 0x0003 7651550 LCK_M_S KEY: 7:1328723786:1 (f80084220ddb) 7 5 20 0 15 2007-04-05 09:33:40.437 2007-04-05 09:33:41.977 0 1 sleeping 0x5C4754C07477D048A81BBBAB3BE5337700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ASRCFHCPSVR2 3348 SELECT 00123F0EFF70 TCP/IP DELTEK 0x0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 0x01000700440217013861D5A60000000000000000 32 -1



Trace

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

PAGE: (1:17617)
---------------

BUFFER:
-------

BUF @0x00000000058E6F00
-----------------------
bpage = 0x00000000AF1AC000 bhash = 0x0000000000000000
bpageno = (1:17617) bdbid = 7 breferences = 1
bstat = 0x9 bspin = 0 bnext = 0x0000000000000000

PAGE HEADER:
------------

Page @0x00000000AF1AC000
------------------------
m_pageId = (1:17617) m_headerVersion = 1 m_type = 1
m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x4002
m_objId = 6 m_indexId = 0 m_prevPage = (1:1069657)
m_nextPage = (1:1492481) pminlen = 14 m_slotCnt = 5
m_freeCnt = 5338 m_freeData = 2844 m_reservedCnt = 0
m_lsn = (369649:84300:11) m_xactReserved = 0 m_xdesId = (0:265626279)
m_ghostRecCnt = 0 m_tornBits = 0

Allocation Status
-----------------
GAM (1:2) = ALLOCATED SGAM (1:3) = NOT AL
TRACEYSQL
New Member
New Member

--
08 Apr 2007 02:56 AM
It was blocked i had no other choice but to kill it off.
I was trying to see why it did this from the page details..

It happens 3 of 5 times this process runs but then there are other connections going on.

My boss wants an explanation.

I said the PAGEIO_lATCH is memory issue.

Have you ever cleaned out the PROCEDURE and BUFFER CACHE on production server.
I was thinking may i do that

What you think...........
You are not authorized to post a reply.

Acceptable Use Policy