Problems Resetting and Restarting the System

Learn about issues that may occur when resetting and restarting the system.

Problems with transactions replaying upon a restart of an ESP project or an "Unknown streamName" error within the ESP Server Console.	Indicates a replay of transactions for a stream that is no longer available. A non-persistent rs_lastcommit always replays transactions. A persistent rs_lastcommit minimizes transaction replay. Persist the rs_lastcommit using a log store and verify that the Transactional Stream Operations is set to True.
Problems with transactions replaying upon a restart of an ESP project or an error within the ESP Server Console.	Purge the Replication Server Adapter queue (queue number) prior to a project restart by logging into the Replication Server and executing sysadmin hibernate_on - go - sysadmin sqm_purge_queue, 107,0 - go - sysadmin hibernate_off - go. Note: The queue number (107) should correspond with the queue number of your ESP Replication Server Adapter connection on the Replication Server. Execute an "admin who"to determine the queue number.
Modifying the ESP Adapter for Replication Server parameters requires a restart of projects, thus all non-persistent streams are cleared. Re-materialize source data, if desired, by dropping and recreating subscriptions. Suspend the Replication Server connection to the Replication Server Adapter prior to stopping the project. This forces an update to the persistent rs_lastcommit, which improves startup time for Replication Server connecting to the ESP Adapter for Replication Server.