| Author |
 Topic  |
|
|
GoodMorningSky
Junior Member
122 Posts |
 Posted - 06 October 2003 : 19:29:46
|
I often get the following error message on our company POS system using SQL server replication when replication error occurs.
I don't know why this error occurs often and how to approach this problem to stablize our system.
please give your any opinion on this problem.
Thank you..
The merge process could not perform retention-based meta data cleanup in database 'POS'.
(Source: Merge Replication Provider (Agent); Error number: -2147199467)
---------------------------------------------------------------------------------------------------------------
Could not find the index entry for RID '163af630200' in index page (1:11608), index ID 3, database 'POS'.
(Source: POS01 (Data source); Error number: 644)
--------------------------------------------------------------------------------------------------------------- |
Software Engineer.
MCSD.NET, SCWCD |
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 07 October 2003 : 04:16:07
|
| Have you done a repair and index rebuild on the databases |
 |
|
|
GoodMorningSky
Junior Member
122 Posts |
Posted - 07 October 2003 : 11:46:12
|
^^ I don't know what you mean..
When replication problem like this, I just drop the database and rebuild it with back up.. which is very un efficient way.. |
Software Engineer.
MCSD.NET, SCWCD |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 07 October 2003 : 12:39:58
|
which database do you drop and rebuild ?
does it fix the problem ? if so, setup some scheduled maintenance to rebuild the indexes before and after the replication occurs. |
|
|
|
GoodMorningSky
Junior Member
122 Posts |
Posted - 07 October 2003 : 17:58:37
|
Once index problem occurs I can't fix the problem.
That's why I just drop the database.
however, it's very inefficient way i guess.
Is there any way to fix the problem or prevent it?
And why this problem occurs almost in regular base? |
Software Engineer.
MCSD.NET, SCWCD |
Edited by - GoodMorningSky on 07 October 2003 18:00:44 |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 07 October 2003 : 18:21:01
|
| Ok, I will ask again, which database are we talking about the publisher or the subscriber ? |
|
|
|
GoodMorningSky
Junior Member
122 Posts |
Posted - 07 October 2003 : 21:20:59
|
Thank you for considering..
Publisher database has the problem not on the subscriber.
|
Software Engineer.
MCSD.NET, SCWCD |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 08 October 2003 : 05:27:57
|
quote:
Originally posted by GoodMorningSky
Thank you for considering..
Publisher database has the problem not on the subscriber.
Are there any other databases on the publishers server ? if so do they experience similar behaviour ?
Have you tried running a regular maintenance schedule on the publisher database ?
Also get the hardwars checked out on the publishing server (ram, drives etc) |
|
|
| |
Topic |
|
Topic Locked
