Master Slave Sync - Selected Record Not Found

[Former Member]

Hello All:

We have a simple master/slave repository set up and use a batch job with a CLIX command to sync our master and slave repostiories at 30-min intervals. However, lately our synchronizations have failed. The sync will begin, but then we receive the error "Selected Record Not Found". It is not a matter of the master or slave being connected, neither appear with black or white bands in the console. This error also occurs on a manual synchronization. Has anyone else encountered this error, know the reason and/or know of a solution other than to recreate the slave? This is starting to happen on a weekly basis.

Thanks, Don

[Former Member]

Hi,

Most of the times this prob comes when slave not able to find the master repository.

Just check your master repository is on the same server that when you create slave repository .

Just check master repository states also.

Please check at your ends and revert back with your findings.

Thanks,

sudhanshu

[Former Member]

Hi Sudhanshu,

Alas, this is not the case. Both the master and the slave are able to connect to the Oracle backend. Neither has the white/black bands that indicated a broken connections. If the connection is broken, it will give that error immediately upon requesting the sync. In this case, the synchronization process begins and progresses, but then will give the "selected record not found" error. This would lead me to believe that there is a certain material record (this is a materials repository) that is either locked or changed or hung up in some way that would not allow the sync to happen. We have tried returning to the sync at later times, but receive the same error each time.

Thanks, Don

[Former Member]

Hi,

I tried all the combination like checked out,deleting record from amster but i havenot got any such error.

please try verify and repair on both repository then try with slave syndication and also check whther any repositories is broken or not.

have you change any schema in master repo if yes then first sync both repo by unloading the repositories to sync the repo schema also.

kindly try these things at your end and get back with your findings

Thanks,

sudhanshu

[Former Member]

Hi, Thanks for your help.

We tried having a record open for editing while syncing and that did not cause the error. The slave repository can by verified, but not repaired. This is disabled. There has been no change in schema, either. As a matter of fact, we had an issue yesterday and only one record had been updated since the last successful sync 30 minutes prior. We are comparing those records.

Thanks, Don

[Former Member]

Hi,

when you verified the repository there aere any error or not.

If yes then unload repository and then repair it.

Thanks,

sudhanshu