KNOWN ISSUE: Replication Data from a failed or hung job is not cleaned up automatically.
|Article:TECH141847|||||Created: 2010-10-13|||||Updated: 2013-09-25|||||Article URL http://www.symantec.com/docs/TECH141847|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Data is no longer replicating between servers. You may see one or more of the following symptoms:
- The database size is increasing dramatically, especially the ITEM table size.
- The Current Replication Activity report shows a job that is failed, or appears to be hung. For example, the percentage is not increasing or the Start Date is greater than 48 hours.
Job shows as in progress for more than 48hrs
Symantec Management Platform 7.0 SP5 and later
Symantec Management Platform 7.1 and later
When a failure occurs during a replication job, the normal cleanup measures are unable to be performed.
- Download and import the attached Task named ‘Replication Data Cleanup’ on each server participating in the replication process, source/destination, parent/child
- After importing, execute the Task (Note that this Task may time out depending on SQL Server speed and amount of data to be cleaned. If this happens, try re-running the Task several times if necessary as it should get farther with each pass)
- Once the Task finishes, run the NS.Daily task from the Windows Scheduled Tasks folder if you want to recover additional database space immediately
NOTE: The Task attached to this article should be disabled/deleted from your servers once this issue has been resolved in a released version of SMP.
Also, if the ITEM table in the database is too large then the cleanup Task may fail to run, because there are too many rows to deal with at one time. If the Task continually fails to run then edit the SQL in the task ‘Replication Data Cleanup’ and at the very top line put the following statement:
SET ROWCOUNT 5000
This will cause the Task to only take out 5,000 rows. This may also require that the Task be run multiple times before everything is cleaned up.
Article URL http://www.symantec.com/docs/TECH141847