July 26, 2010 at 8:06 am
The snapshot agen runs forever never completing...
Server 2008 was running merge replication between a publisher and a subscriber. The client wanted to add another subscriber. "No problem," thought I. Well, it's too late to make a long story short, so here's the end result:
The snapshot agent starts running, and never finishes. The replication monitor says "The snapshot is obsolete..." I've even tried the stored procedure to start the snapshot.
The gruesome details:
•MS SQL Server 2008 Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)
•Database Size 711MB
•Microsoft Windows Server 2003 R2
•Intel Xeon CPT 2.40GHz
•1.00 GB ram (seems a little small)
•136GB Drive, 116GB free
Somebody suggested I use sp_who to see what was locking things. Didn't looke to me like anybody was:
spid ecid status loginame hostname blk dbname cmd request_id
------ ------ ----------- -------------------------------------------- -------------------------------- -----------
1 0 background sa 0 NULL RESOURCE MONITOR 0
2 0 background sa 0 NULL XE TIMER 0
3 0 background sa 0 NULL XE DISPATCHER 0
4 0 background sa 0 NULL LAZY WRITER 0
5 0 background sa 0 NULL LOG WRITER 0
6 0 background sa 0 NULL LOCK MONITOR 0
7 0 background sa 0 master SIGNAL HANDLER 0
8 0 sleeping sa 0 master TASK MANAGER 0
9 0 background sa 0 master TRACE QUEUE TASK 0
10 0 background sa 0 master BRKR TASK 0
11 0 background sa 0 distribution CHECKPOINT 0
12 0 background sa 0 master TASK MANAGER 0
13 0 sleeping sa 0 master TASK MANAGER 0
14 0 background sa 0 master BRKR EVENT HNDLR 0
15 0 background sa 0 master BRKR TASK 0
16 0 background sa 0 master BRKR TASK 0
17 0 sleeping sa 0 master TASK MANAGER 0
18 0 sleeping sa 0 master TASK MANAGER 0
19 0 sleeping sa 0 master TASK MANAGER 0
20 0 sleeping sa 0 master TASK MANAGER 0
21 0 sleeping sa 0 master TASK MANAGER 0
22 0 sleeping sa 0 master TASK MANAGER 0
51 0 sleeping NT AUTHORITY\NETWORK SERVICE GOLFSQL 0 msdb AWAITING COMMAND 0
53 0 sleeping NT AUTHORITY\NETWORK SERVICE GOLFSQL 0 msdb AWAITING COMMAND 0
54 0 sleeping NT AUTHORITY\NETWORK SERVICE GOLFSQL 0 msdb AWAITING COMMAND 0
58 0 sleeping sa GOLFSQL 0 master AWAITING COMMAND 0
59 0 runnable sa GOLFSQL 0 CrescentAncient SELECT 0
66 0 sleeping NT AUTHORITY\NETWORK SERVICE GOLFSQL 0 msdb AWAITING COMMAND 0
(28 row(s) affected)
I made the mistake of asking on MSDN. There, if you have a question about a vague response, you get no response.
The client is rather understandably annoyed.
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font]
July 26, 2010 at 9:46 am
A 711 MB database hanging? That is just strange. Did you see any error in the SQL Server Error logs? There is one thing you can try. Try to set up replication using Back up method.
-Roy
July 26, 2010 at 10:55 am
Database keeps running. Snapshot agent doesn't. Always stays in active jobs and never finishes. Of course, now they've noticed that the data from the existing subscriber isn't merging.
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply