Bora.Choi

서버: 메시지 601, 수준, 12, 14 선 3상
데이터 이동으로 인해 NOLOCK 함께 스캔을 계속할 수 없습니다

Q:

2-3일전부터 서버가 죽어서요...

저는 NT4.0, Ms-SQL 7.0, IIS 을 사용하고 있습니다.

1. WEB

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBMSSOCN]General network error. Check your network documentation.

/dbopen.asp, line 12

2. Event Log

원본( SQLCTR70 )에서 이벤트 ID( 1001 )에 대한 설명을 찾지 못했습니다. 다음 삽입 문자열을 포함합니다: Shared memory segment already exists..

Error: 17826, Severity: 18, State: 1
2002-08-22 18:36:22.35 ods Could not set up ListenOn connection 'ACCOUNT'..
Operating system error 1899., 종료점 매퍼 데이터베이스를 만들 수 없습니다.

3. Ms-SQL
02-09-13 오후 12:18:13 - + [164] ODBC Message: 109, ConnectionTransact (GetOverLappedResult()). [SQLSTATE 01000]
02-09-13 오후 12:18:13 - ! [165] ODBC Error: 4, Connection broken. [SQLSTATE 08S01]
02-09-13 오후 12:18:13 - ! [298] SQLServer Error: 4, Connection broken. [SQLSTATE 08S01]
02-09-13 오후 12:18:13 - ! [298] SQLServer Error: 109, ConnectionRead (GetOverLappedResult()). [SQLSTATE 01000]
02-09-13 오후 12:18:13 - ! [382] Logon to server '(local)' failed (ConnCachePerfCounterValues)
02-09-13 오후 12:18:14 - + [360] SQLServerAgent initiating shutdown following MSSQLServer shutdown
02-09-13 오후 12:18:16 - ! [359] The local host server is not running
02-09-13 오후 12:18:17 - ? [098] SQLServerAgent terminated (normally)

A:

이전에 제대로 실행되던 웹 응용 프로그램에서 IIS가 갑자기 알 수 없는 80004005 오류를 보고하는 이유를 확인해 달라는 질문을 받았습니다.

즉, 다음과 같은 메시지가 나타납니다.

OLE DB 공급자 오류 ODBC 드라이버 오류...데이터 원본 이름을 찾을 수 없습니다...

먼저 저는 시스템 DSN이 제 위치에 있는지를 확인했습니다.

시스템 DSN이 제 위치에 있었으므로 레지스트리 권한 문제가 아닌가 생각되어 SysInternals의 NTRegMon( http://www.sysinternals.com/ntw2k/source/regmon.shtml )을 설치하고 웹 응용 프로그램을 시작하면서 레지스트리 호출을 추적했습니다.

아니나 다를까, 3개의 레지스트리 키에서 액세스 거부가 발견되었고 이를 수정하자 응용 프로그램이 제대로 시작되었습니다.

편집자 주 이 항목에 대한 자세한 내용은 KB 기사 Q238971 http://support.microsoft.com/support/kb/articles/Q238/9/71.ASP 를 참조하십시오.

출처: 야휴 지식인
http://kr.ks.yahoo.com/service/ques_reply/ques_view.html?dnum=J&qnum=1067220

2009-10-09 13:30:01.120 spid62 The database 'XXX' is marked RESTORING and is in a state that does not allow recovery to be run.
2009-10-09 13:30:25.530 spid20s Database mirroring is active with database 'XXX' as the mirror copy. This is an informational message only. No user action is required.
2009-10-09 17:19:14.180 spid20s Error: 3456, Severity: 21, State: 1.
2009-10-09 17:19:14.180 spid20s Could not redo log record (276495:119218:6),
for transaction ID (0:408286833), on page (20:508656), database 'XXX' (database ID 12).
Page: LSN = (276492:1649102:28), type = 1. Log: OpCode = 4, context 2,
 PrevPageLSN: (276495:66503:4). Restore from a backup of the database, or repair the database.
2009-10-09 17:19:14.190 spid20s Error: 1454, Severity: 16, State: 1.
2009-10-09 17:19:14.190 spid20s While acting as a mirroring partner for database 'XXX', server instance '장비명' encountered error 3456, status 1, severity 21. Database mirroring will be suspended.  Try to resolve the error and resume mirroring.
2009-10-09 17:19:14.700 spid20s Database mirroring is inactive for database 'XXX'. This is an informational message only. No user action is required.

2009-07-05 05:39:01.050spid1sA significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 263552, committed (KB): 528496, memory utilization: 49%.

2009-07-05 05:46:21.370spid1sA significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 265520, committed (KB): 527400, memory utilization: 50%.

2009-07-05 07:28:27.210spid27sError: 1204, Severity: 19, State: 4.

2009-07-05 07:28:27.210spid27sThe instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time.

Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

2009-07-05 07:28:27.320spid27sError: 1454, Severity: 16, State: 1.

2009-07-05 07:28:27.320spid27sWhile acting as a mirroring partner for database 'DB명', server instance '주서버명' encountered error 1204, status 4, severity 19. Database mirroring will be suspended.  Try to resolve the error and resume mirroring.

2009-07-05 07:28:27.820spid27sDatabase mirroring is inactive for database 'DB명'. This is an informational message only. No user action is required.

 

(주서버)

2009-07-05 07:28:27.920spid34sError: 1453, Severity: 16, State: 1.

2009-07-05 07:28:27.920spid34s'TCP://정보', the remote mirroring partner for database 'DB명', encountered error 1204, status 4, severity 19. Database mirroring has been suspended.  Resolve the error on the remote server and resume mirroring, or remove mirroring and re-establish the mirror server instance.

select request_session_id, count(*) num_locks from sys.dm_tran_locks  group by request_session_id order by count(*) desc