Log Reader Agent is getting stopped

I am getting in the logreader agent and it getting stopped Abruptly showing below error
"The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher,
and Distributor are still active."
When i start the agent it gets started but can i know why its getting stopped and how can i resolve this issue.
Thanks in advance.

I wish you have mentioned this was Oracle at the beginning:)
This is a known problem with Oracle Publishing. Microsoft is now recommending you use Attunity to track changes in Oracle and use SSIS to replicate the commands.
Open a support incident with Microsoft to help you to address the log reader problem and advise you on the best approach to this.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Similar Messages

  • Log Reader Agent Errors

    On a server with 4 merge publications I'm getting errors from a Log Reader Agent.
    From documentations it seems to me that Log Reader Agent must be present only if there are some transactional publication, so I think that errors depends on this.
    Probably the Log Reader Agent was created some time ago with a transactional publication that no longer exists.
    So my question is: can I remove the Log Reader Agent?
    To remove it can I simply remove the associated job?
    The error are all like this:
    The process could not execute 'sp_repldone/sp_replcounters' on 'GEREONTK'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
    Get help: http://help/MSSQL_REPL20011
    Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication. (Source: MSSQLServer, Error number: 18757)
    Get help: http://help/18757
    The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
    Get help: http://help/MSSQL_REPL22017
    Thanks,
    Roberto

    There's no more transactional replication on database but still exists two merge replications on some tables of the same db (publication Gereon and GereonPortfoliosAll).
    So I've no replication to drop but only a Log Reader Agent that seems to be a survivor from a previous transactional pubblication.
    In these day I've stopped the job related to the Log Reader Agent, and merge replication are working right. So I think I can remove this Agent from the server.
    In
    Log Reader Agent definition on MSDN I've found "The Replication Log Reader Agent is an executable that monitors the transaction log of each database
    configured for transactional replication and copies the transactions marked for replication from the transaction log into the distribution database." so it seems to me that is not related to merge replication and it safe to be removed.
    Thanks

  • The process could not execute 'sp_repldone/sp_replcounters' error for Log Reader Agent and SQL Server Assertion 17066 & 3624 errors in SQL Logs

    One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
    process could not execute 'sp_repldone/sp_replcounters' on XXXXX". 
    Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause. 
    ***********Error messages from SQL Logs******
    **Dump thread - spid = 0, EC = 0x0000000111534460
    Message
    A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
    Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
    Error: 3624, Severity: 20, State: 1.
    SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
    the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
    Error: 17066, Severity: 16, State: 1.
    External dump process return code 0x20000001.
    External dump process returned no errors.
    Thank you in advance.

    You need to determine if this error is a transient one or a show stopper one.
    It sounds like your log reader agent has crashed and can't continue.
    If so your best bet is to call Microsoft CSS and open a support incident.
    It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
    If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
    I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Log Reader Agent error "could not execute sp_replcmds' and causes stack dump

    Publisher/Subscriber db:  SQL 2008 R2, 2000 compatability mode
    Distributor database is on separate server.
    (note:  There is another database on this instance that is running replication without error, it is not in compatibility mode)
    After snapshot agent finishes, the log reader agent starts and fails immediately with this error in the Agent Job.
    Then I get a SEV20 error and stack dump in the error logs.
    Date  6/12/2014 3:12:26 PM
    Log  Job History (SERVER\INSTANCE-DBNAME-43)
    Step ID  2
    Server  ######RT02
    Job Name  SERVER\INSTANCE-DBNAME-43
    Step Name  Run agent.
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  0
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    2014-06-12 20:12:26.302 Copyright (c) 2008 Microsoft Corporation
    2014-06-12 20:12:26.302 Microsoft SQL Server Replication Agent: logread
    2014-06-12 20:12:26.302
    2014-06-12 20:12:26.302 The timestamps prepended to the output lines are expressed in terms of UTC time.
    2014-06-12 20:12:26.302 User-specified agent parameter values:
       -Publisher SERVER\INSTANCE
       -PublisherDB DBNAME
       -Distributor ######RT02
       -DistributorSecurityMode 1
       -Continuous
       -XJOBID 0x8958DF32810C6849B28A037A8FF8DD92
       -XJOBNAME SERVER\INSTANCE-DBNAME-43
       -XSTEPID 2
       -XSUBSYSTEM LogReader
       -XSERVER SERVER\INSTANCE
       -XCMDLINE 0
       -XCancelEventHandle 0000000000000F98
       -XParentProcessHandle 0000000000000F34
    2014-06-12 20:12:26.459 Parameter values obtained from agent profile:
       -pollinginterval 5000
       -historyverboselevel 1
       -logintimeout 15
       -querytimeout 1800
       -readbatchsize 500
       -readbatchsize 500000
    2014-06-12 20:12:26.493 Status: 4096, code: 20024, text: 'Initializing'.
    2014-06-12 20:12:26.493 The agent is running. Use Replication Monitor to view the details of this agent session.
    2014-06-12 20:12:27.885 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    2014-06-12 20:12:27.886 The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.
    2014-06-12 20:12:27.886 Status: 0, code: 21, text: 'Warning: Fatal error 3624 occurred at Jun 12 2014  3:12PM. Note the error and time, and contact your system administrator.'.
    2014-06-12 20:12:27.886 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
    I've tried removing replication and setting it back up again, restarting SQL, and restarting the server itself.
    Let me know if you need any more information to help troubleshoot.  Thanks.
    Please help, thanks. 

    Hi,
    Enable Verbose logging and check the results.
    Execute following commands: -Output C:\Temp\OUTPUTFILE.txt –Outputverboselevel 2.
    Please refer following KB article for your reference -
    http://support.microsoft.com/kb/q312292/
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Log Reader Agent is not able to read Transaction Log of Publisher database.

    Hi,
    There is no restore or change in recovery model or detach-attach action performed on my production database but still I am seeing below error message from Log Reader Agent-
    Error messages:
    The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
    Get help:
    An error occurred while processing the log for database 'MyDatabase'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. (Source: MSSQLServer, Error number: 9004)
    The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
    Get help: The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
    Note- CheckDB on production and distribution database executed successfully. Also, I need subscriber to be a true copy of publisher so I think sp_replrestart is not an option for me.
    My question is how to resolve this issue? I am thinking that reinitialization should resolve the problem but what if this is not going to resolve? Do I need to reconfigure the transaction replication? Please sugegst.

    Hi,
    Please check out this link on how to resolve “The process could not execute 'sp_repldone/sp_replcounters'” error.
    http://blogs.msdn.com/b/repltalk/archive/2010/02/19/the-process-could-not-execute-sp-repldone-sp-replcounters.aspx
    The possible cause could be:
    1.The last LSN in Transaction Log is less than what the LSN Log Reader is trying to find. An old backup may have been restored on top of Published Database. After the restore, the new Transaction Log doesn't contain the data now distributor & subscriber(s)
    have.
    2.Database corruption.
    Since you have not restored the published database, I suggest you run
    DBCC CHECKDB to confirm the consistency of the database. Refer to the How to fix in the above link.
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Log Reader Agent and Snapshot Agent wont start

    Hi There,
    I've two SQL 2012 servers with multiple instances installed.
    I've started replicating the databases in these instances using transactional replication and thus far they've worked without a hitch.
    One of my instances, annoyingly, has an issue where the Log Reader Agent and Snapshot Agent refuse to start, and I've followed exactly the same process as with the other instances\databases.
    The Agents are configured to make use of a domain user account with sysadmin permissions to the instances on both servers.
    I get the following two error when I View Log Reader Agent Status:
    The job failed. The Job was invoked by User sa. The last step to run was step 2 (Run agent.).
    I've asked the agent to run as my DOMAIN\sqlservice account, so I've no idea why it's moaning about sa?!!?
    I get the following error when I View Snapshot Agent Status:
    The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Di
    If I try to start either agent I'm told that the request to run job was refused because the job has been suspended, "Changed database context"??  Error 22022.
    Can anyone help?

    This is because your job owner is sa.  Right click on your job and notice the owner - but is should be sa.
    You likely have another issue. You may need to run the job and configure it for logging to see what the error is.
    http://support.microsoft.com/kb/312292/en-us
    looking for a book on SQL Server 2008 Administration?
    http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
    http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

  • Log reader agent

    may i know the process involved in log reader agent or definition.
    please suggest me about it.

    The following is an excerpt from here.
    Modifying Data and the Log Reader Agent
    The Log Reader Agent runs at the Distributor; it typically runs continuously, but can also run according to a schedule you establish. When executing, the Log Reader Agent first reads the publication transaction log (the same database log used for transaction
    tracking and recovery during regular SQL Server Database Engine operations) and identifies any INSERT, UPDATE, and DELETE statements, or other modifications made to the data in transactions that have been marked for replication. Next, the agent copies those
    transactions in batches to the distribution database at the Distributor. The Log Reader Agent uses the internal stored procedure sp_replcmds to get the next set of commands marked for replication from the log. The distribution database
    then becomes the store-and-forward queue from which changes are sent to Subscribers. Only committed transactions are sent to the distribution database.
    After the entire batch of transactions has been written successfully to the distribution database, it is committed. Following the commit of each batch of commands to the Distributor, the Log Reader Agent calls sp_repldone to mark
    where replication was last completed. Finally, the agent marks the rows in the transaction log that are ready to be purged. Rows still waiting to be replicated are not purged.
    Transaction commands are stored in the distribution database until they are propagated to all Subscribers or until the maximum distribution retention period has been reached. Subscribers receive transactions in the same order in which they were applied at the
    Publisher.
    Satish Kartan http://www.sqlfood.com/

  • Log Reader Agent: transaction log file scan and failure to construct a replicated command

    I encountered the following error message related to Log Reader job generated as part of transactional replication setup on publisher. As a result of this error, none of the transactions propagated from publisher to any of its subscribers.
    Error Message
    2008-02-12 13:06:57.765 Status: 4, code: 22043, text: 'The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately 24500000 log records have been scanned in pass # 1, 68847 of which were marked for replication, elapsed time 66018 (ms).'.
    2008-02-12 13:06:57.843 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on ServerName.'.
    2008-02-12 13:06:57.843 Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00065e22:0002e3d0:0006}. Back up the publication database and contact Customer Support Services.'.
    2008-02-12 13:06:57.843 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'ServerName'.'.
    Replication agent job kept trying after specified intervals and kept failing with that message.
    Investigation
    I could clearly see there were transactions waiting to be delilvered to subscribers from the followings:
    SELECT * FROM dbo.MSrepl_transactions -- 1162
    SELECT * FROM dbo.MSrepl_commands -- 821922
    The following steps were taken to further investigate the problem. They further confirmed how transactions were in queue waiting to be delivered to distribution database
    -- Returns the commands for transactions marked for replication
    EXEC sp_replcmds
    -- Returns a result set of all the transactions in the publication database transaction log that are marked for replication but have not been marked as distributed.
    EXEC sp_repltrans
    -- Returns the commands for transactions marked for replication in readable format
    EXEC sp_replshowcmds
    Resolution
    Taking a backup as suggested in message wouldn't resolve the issue. None of the commands retrieved from sp_browserreplcmds with mentioned LSN in message had no syntactic problems either.
    exec sp_browsereplcmds @xact_seqno_start = '0x00065e220002e3d00006'
    In a desperate attempt to resolve the problem, I decided to drop all subscriptions. To my surprise Log Reader kept failing with same error again. I thought having no subscription for publications log reader agent would have no reason to scan publisher's transaction log. But obviously I was wrong. Even adding new log reader using sp_addLogreader_agent after deleting the old one would not be any help. Restart of server couldn't do much good either.
    EXEC sp_addlogreader_agent
    @job_login = 'LoginName',
    @job_password = 'Password',
    @publisher_security_mode = 1;
    When nothing else worked for me, I decided to give it a try to the following procedures reserved for troubleshooting replication
    --Updates the record that identifies the last distributed transaction of the server
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
    -- Flushes the article cache
    EXEC sp_replflush
    Bingo !
    Log reader agent managed to start successfully this time. I wish if I could have used both commands before I decided to drop subscriptions. It would have saved me considerable effort and time spent re-doing subscriptions.
    Question
    Even though I managed to resolve the error and have replication funtioning again but I think there might have been some better solution and I would appreciate if you could provide me some feedback and propose your approach to resolve the problem.

    Hi Hilary,
    Will the below truncate the log file marked for replication, is there any data loss, when we execute this command, can you please help me understand, the internal working of this command.
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1

  • Does Log reader agent use sa in sp_replcmds?

    We have publisher, subscriber, and distributor on separate servers. Replication is Push Transactional with replication agents setup to run under SQL Agent account context. We are in the process of disabling sa from everywhere and I am monitoring sessions
    that use sa to make sure there is no impact.
    I see that log reader agent session sometimes uses sa as login name in its sessions on publisher. In sys.dm_exec_sessions, there are two columns for login: Login_Name and Original_Login_Name. The Login_Name shows sa. Most of the time the SPID of log reader
    agent on publisher shows the SQL agent service account as login name of the session. But sometimes the same SPID shows sa as login name. This always coincides with session running SP_REPLCMDS without any parameters and also messages like "The Log Reader
    Agent is scanning the transaction log for command to be replicated. Approximately...." in Replication Monitor. Normally, the session would run SP_REPLCMDS giving some parameters. When this happens, in sys.dm_exec_sessions, the log reader SPID keeps showing
    Original Login name as that of Distributor agent service account but login_name sa.
    Does sp_replcmds run as sa? If I disable sa on publisher, distributor, and subscriber, will it break replication?

    it all depends on what accounts you have set for log reader agent security, distribution agent security and snapshot agent security etc.. If you have not configured anything to use sa then you can disable and it should not have an issue.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • How to stop the auto-start of log reader agent (replication) right after my database is restored?

    I have the scenario where the SQL server is restored (after migration).
    This database has transactional replication set-up on one of the databases. When I do a manual delete and restore of the database, I see that the replication starts right after the publisher and subscriber are restored.
    Replication agents should not start and run before the integrity checks are completed. How to stop the replication from auto starting right after the migration?
    Thanks in advance - Jebah

    Thanks Pradyothana, I have disabled the logreader, distribution agents through sp_update_job in Tsql script. I have also verified that there are no pending transactions to be replicated to the subscriber, I see that the job is still being executed. Is there
    any other way to disable the jobs?
    Steps I followed
    Started with a Working publication and subscription
    Disabled the jobs (log reader and distribution agents)
    Backed up publisher, subscriber, distribution and msdb
    Deleted the publication, subscription, publisher and subscriber
    Restored the publisher, subscriber, distribution and msdb
    Enabled the jobs and executed sp_replrestart
    Observations/Issues
    Replication does not work
    Replication monitor does not show any error
    Jobs are shows as enabled but not started in job monitor
    Not able to start/stop the log reader and synchronization manually.
    I am not sure if I have missed something while restoring the db.
    Thanks in advance

  • Log Reader is getting Stopped in SQL replication

    Hi All,
    We are having a oracle Publisher and distributor and subscriber is SQL SERVER.
    My Log reader service is getting failed showing below error
    Error messages:
    The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor
    are still active.
    When i checked the MSrepl_errors table i found out the below errors
    Heterogeneous Logreader encountered an error in call to 'Initialize'.
    ORA-12541: TNS:no listener
    Heterogeneous Logreader encountered an error in call to LoadReplCmds when processing state 'POLLBEGIN'.
    ORA-03113: end-of-file on communication channel Process ID: 4852 Session ID: 539 Serial number: 14
    when i troubleshoot this i found out that My Oracle database was down for some time and when it was up the log reader service was not up automatically and so we are having around 1 Million transactions pending.
    I tried to reinitializing the subscriber but it stilled didn't work.I want to flush the pending transaction and take a new snapshot but when i am trying to do it using sp_repldone but its not wroking and showing below error
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
    Msg 18757, Level 16, State 1, Procedure sp_repldone, Line 1
    Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
    Is there any other way i can flush the load reader if the publisher the Oracle i think the sp_repldone command is not working for Oracle Publisher.Can anybody help me out my replication is stopped currently.
    Any help will be great for me.

    i disabled thePublishing and distribution and tried to recreate it again.the recreation was successful and the log reader is working fine now but the distribution agent is throwing below error.I assume the distribution agent should dop and create the table
    but its not able to so that.
    Error messages:
    The process could not bulk copy into table '"dbo"."MPI_COB_T_SHOP_ORDER_DETAIL"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)
    Get help: http://help/MSSQL_REPL20037
    Invalid object name 'dbo.MPI_COB_T_SHOP_ORDER_DETAIL'. (Source: MSSQLServer, Error number: 208)
    Get help: http://help/208
    To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.  Consult the BOL for more information on the bcp utility and its supported options. (Source: MSSQLServer,
    Error number: 20253)
    Get help: http://help/20253
    bcp "FlexNet"."dbo"."MPI_COB_T_SHOP_ORDER_DETAIL" in "G:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\ReplData\unc\MESD01_DISTRIBUTION_MPI_PUB\20150224062223\COB_T_SHOP_ORDER_DETAIL_71.bcp" -e "errorfile"
    -t"\n<x$3>\n" -r"\n<,@g>\n" -m10000 -SCIDCSWDMESMPD01 -T -w (Source: MSSQLServer, Error number: 20253)
    Get help: http://help/20253
    Can anyone help me on it please

  • Agent starting and stopping

    Having a problem with Agent starting, can't access database, OS is Windows XP Professional. Can anyone shed any light on this?

    It starts from last successfully delivered transaction. That means when you stop log reader agent in middle of its processing then it will start from the beginning of the last batch that was in process when it was stopped.
    Thanks, Mohan Kumar - Please mark the post as answered if it answers your question.

  • I am running Windows7 on my PVC. When I log in I'm getting two Apple error messages. One says, " The procedure entry point sqlite3_wal_checkpoint could not be located in the dynamic link library SQLite3.dll." The second says, "Apple Photostreams stop

    I am running Windows7 on my PVC. When I log in I'm getting two Apple error messages. One says, " The procedure entry point sqlite3_wal_checkpoint could not be located in the dynamic link library SQLite3.dll." The second says, "Apple Photostreams Uploader has stopped working".  Help!

    Entry point errors can often be fixed by deleting the offending dll, then repairing the component it is part of. If that doesn't help read on...
    For general advice see Troubleshooting issues with iTunes for Windows updates.
    The steps in the second box are a guide to removing everything related to iTunes and then rebuilding it which is often a good starting point unless the symptoms indicate a more specific approach. Review the other boxes and the list of support documents further down the page in case one of them applies.
    Your library should be unaffected by these steps but there is backup and recovery advice elsewhere in the user tip.
    If the advice above doesn't resolve things you could try this alternate version:
    iTunes 12.1.0.71 for Windows (64-bit - for older video cards) - itunes64setup.exe (2015-01-28)
    which is a 64-bit installer for the 32-bit version of the core application, similar to previous 64-bit releases.
    Or roll back to the previous build:
    iTunes 12.0.1.26 for Windows (32-bit) - iTunesSetup.exe (2014-10-16)
    iTunes 12.0.1.26 for Windows (64-bit) - iTunes64Setup.exe (2014-10-16)
    tt2

  • Replication Log Reader stopped unexpectedly

    This morning our websites stopped serving pages.  Whilst investigating I notice that the Replication Sql LogReader had stopped running and was reporting the error:
    "SubSystem Message - Job 'XXX582060-XXXXX-1' (0x6D6877EFE4F8EA4D930F8C967FE49BE5), step
    2 - A time out occurred while waiting for memory resources to execute the query. Rerun the query."
    I have restarted the LogReader and it seems to be working fine but I'd really like to get to the bottom of why it stopped in the first place so I can prevent happening in the future.
    Any help would be great.
    Thanks
    Mike

    Check this blog -
    http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
    Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
    Also make sure that you have configured your memory settings properly.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • After installing 4.7 the dispatcher is getting stopped

    hi gurus, i am installing 4.7 after installation i got the message like successfully complted , when iam trying to start the MMC but the dispatcher is getting stopped please check this log -
    trc file: "dev_disp", trc level: 1, release: "620"
    Tue Jan 08 14:21:04 2008
    systemid   560 (PC with Windows NT)
    relno      6200
    patchlevel 0
    patchno    251
    intno      20020600
    pid        300
    ***LOG Q00=> DpSapEnvInit, DPStart (00 300) [dpxxdisp.c   966]
         shared lib "dw_xml.dll" version 252 successfully loaded
         shared lib "dw_xtc.dll" version 252 successfully loaded
         shared lib "dw_stl.dll" version 252 successfully loaded
    Tue Jan 08 14:21:09 2008
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  3140]
    MtxInit: -2 0 0
    MBUF state OFF
    EmInit: MmSetImplementation( 2 ).
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation std
    <EsNT> Memory Reset enabled as NT default
    <EsNT> EsIUnamFileMapInit: Initialize the memory 916 MB
    <ES> 915 blocks reserved for free list.
    ES initialized.
    ***LOG Q0K=> DpMsAttach, mscon ( dev) [dpxxdisp.c   8832]
    CCMS: Initalizing shared memory of size 20000000 for monitoring segment.
    Tue Jan 08 14:21:10 2008
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 6200, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   940]
    DpMsgAdmin: Set patchno for this platform to 251
    Release check o.K.
    Tue Jan 08 14:22:09 2008
    ERROR => W0 (pid 892) died [dpxxdisp.c   11210]
    ERROR => W1 (pid 616) died [dpxxdisp.c   11210]
    Tue Jan 08 14:22:29 2008
    ERROR => W2 (pid 964) died [dpxxdisp.c   11210]
    ERROR => W3 (pid 1032) died [dpxxdisp.c   11210]
    ERROR => W4 (pid 1064) died [dpxxdisp.c   11210]
    ERROR => W5 (pid 736) died [dpxxdisp.c   11210]
    ERROR => W6 (pid 1128) died [dpxxdisp.c   11210]
    ERROR => W7 (pid 1184) died [dpxxdisp.c   11210]
    ERROR => W8 (pid 1152) died [dpxxdisp.c   11210]
    ERROR => W9 (pid 1360) died [dpxxdisp.c   11210]
    ERROR => W10 (pid 548) died [dpxxdisp.c   11210]
    ERROR => W11 (pid 1396) died [dpxxdisp.c   11210]
    ERROR => W12 (pid 1404) died [dpxxdisp.c   11210]
    ERROR => W13 (pid 1408) died [dpxxdisp.c   11210]
    ERROR => W14 (pid 1416) died [dpxxdisp.c   11210]
    ERROR => W15 (pid 1428) died [dpxxdisp.c   11210]
    my types changed after wp death/restart 0xbf --> 0x80
    DP_FATAL_ERROR => DpEnvCheck: no more work processes
    DISPATCHER EMERGENCY SHUTDOWN ***
    ERROR => DpMBufRead: state MBUF_PREPARED, opmode MBUF_USE [dpxxmbuf.c   503]
    ERROR => DpModState: DpMBufRead failed (-1) [dpxxdisp.c   13129]
    Tue Jan 08 14:22:36 2008
    ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   9058]
    MBUF state OFF
    MBUF component DOWN
    ***LOG Q05=> DpHalt, DPStop ( 300) [dpxxdisp.c   7637]
    cheers

    Hi kaushal ,
    here dis is the log file which u asked
    trc file: "dev_w0", trc level: 1, release: "620"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, M
    B 
    B Tue Jan 08 15:03:01 2008
    B  create_con (con_name=R/3)
    B  Loading DB library 'E:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' ...
    B  Library 'E:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' loaded
    B  Version of 'E:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' is "620.02", patchlevel (0.112)
    B  New connection 0 created
    M  systemid   560 (PC with Windows NT)
    M  relno      6200
    M  patchlevel 0
    M  patchno    251
    M  intno      20020600
    M  pid        396
    M 
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 396) [dpxxdisp.c   1016]
    I  MtxInit: -2 0 0
    X 
    X Tue Jan 08 15:03:02 2008
    X  EmInit: MmSetImplementation( 2 ).
    X 
    X Tue Jan 08 15:03:03 2008
    X  <ES> client 0 initializing ....
    X  Using implementation std
    M  <EsNT> Memory Reset enabled as NT default
    X  ES initialized.
    M 
    M Tue Jan 08 15:03:06 2008
    M  calling db_connect ...
    C  Got ORACLE_HOME=E:\oracle\ora81 from environment
    C  Client NLS settings: AMERICAN_AMERICA.WE8DEC
    C  Logon as OPS$-user to get SAPDEV's password
    C  Connecting as /@DEV on connection 0 ...
    C  Attaching to DB Server DEV (con_hdl=0,svchp=02F5EE78,svrhp=02F5EC84)
    C  Starting user session (con_hdl=0,svchp=02F5EE78,srvhp=02F5EC84,usrhp=0612CB2C)
    C 
    C Tue Jan 08 15:03:07 2008
    C  *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
    [dboci.c      3718]
    C  *** ERROR => CONNECT failed with sql error '1017'
    [dboci.c      9536]
    C  Try to connect with default password
    C  Connecting as SAPDEV/<pwd>@DEV on connection 0 ...
    C  Starting user session (con_hdl=0,svchp=02F5EE78,srvhp=02F5EC84,usrhp=0612CB2C)
    C  *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
    [dboci.c      3718]
    C  *** ERROR => CONNECT failed with sql error '1017'
    [dboci.c      9536]
    B  ***LOG BY2=> sql error 1017   performing CON [dbsh#2 @ 962] [dbsh    0962 ]
    B  ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dbsh#2 @ 962] [dbsh    0962 ]
    B  ***LOG BY2=> sql error 1017   performing CON [dblink#1 @ 419] [dblink  0419 ]
    B  ***LOG BY0=> ORA-01017: invalid username/password; logon denied [dblink#1 @ 419] [dblink  0419 ]
    M  ***LOG R19=> tskh_init, db_connect ( DB-Connect 000256) [thxxhead.c   1098]
    M  in_ThErrHandle: 1
    M  *** ERROR => tskh_init: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   8277]
    M 
    M  Info for wp 0
    M 
    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = -1
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    rfc_req = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M 
    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server dev_DEV_00 on host dev (wp 0)
    M  *  ERROR       tskh_init: db_connect
    M  *
    M  *  TIME        Tue Jan 08 15:03:07 2008
    M  *  RELEASE     620
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        8408
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************
    M 
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >SAP-Trace buffer write< for event BEFORE_DUMP
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   672]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  235]
    M  Entering ThSetStatError
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 396) [dpnttool.c   345]

Maybe you are looking for